Skip to content

[Add Package]: Microsoft.MaliciousSoftwareRemovalTool #80

@DandelionSprout

Description

@DandelionSprout

Reasons to potentially add it

The tool is used in the system background by tens (if not hundreds) of millions, primarily because most of the monthly Windows updates include it. As such, even the standalone, manually-run-only version of the tool could be considered high-profile; and as it gets circa 10 updates a year (I've handled 5 or 6 manifest version updates for it previously), I'm hoping automation (e.g. the bot) can take care of it.

Potential obstacles

At the time of writing, updates can be looked for by first checking for a hash mismatch; and if there is a mismatch, add 1 to the last number of the URL, so that for instance -V5.137.exe is replaced by -V5.138.exe. However, that pattern is not very consistent, even less so for the x64 InstallerUrl-s.

The x64 and x86 versions have different PackageUrl-s, and thus 2 different places where updates would need to be checked for:

Side notes

Of the current locale files, only the (...).nb.yaml one could be safely removed; all 23 others should remain pretty much as-is (or expanded upon), including their tags.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions