Troubleshooting

This is usually intentional. The report records the specific reason. The common causes:

• Low or tied match confidence — the tool cannot prove which product it is, so it refuses to act.
• Protected software — it matched an RMM, VPN, backup, encryption, driver, or firmware guard. These are checked before your blocklist, so a wildcard cannot reach them.
• No supported backend — services, scheduled tasks, and registry artifacts are audit-only until a dedicated tested handler exists.
• Gate not enabled — endpoint protection and remote tools each need their own explicit authorization on top of uninstall mode.
• Command validation failed — the vendor uninstall string was not safely executable.

If you believe the classification is wrong, open a catalog request.

By design, and there is no setting that changes it. Both are classified as approved management software and stay preserved even with remote-tool authorization enabled and an aggressive wildcard blocklist in policy. Remove them through your RMM tooling instead.

The published artifacts are not code-signed. Verify the download against the release SHA256SUMS.txt before running it:

Get-FileHash .\OEM-Endpoint-Cleanup-2.2.1-win-x64.msi -Algorithm SHA256

For production distribution, re-sign the artifacts with an organization-controlled certificate.

1603 is a vendor-side installation failure, not a tool failure. The report preserves the uninstaller's own output so you can see the vendor or Windows deployment error rather than just a code.

A timeout is reported as a distinct outcome. Uninstallers are bounded by processTimeoutSeconds (default 900, clamped to 30–3600). Vendor uninstallers that are password-protected, self-protected, or interactive will hit this — those need manual intervention or the vendor's own cleanup tool.

Check, in order: is Uninstall mode enabled? Is the process elevated? Does the row's decision say Remove rather than manual-review? Is dryRun set to true in your deployed policy.json? Dry-run never starts a process, and it is the default.

You cannot undo it from the tool. Vendor uninstallers are not transactional, and the tool deliberately does not create restore points or attempt file and registry reconstruction. Reinstall from the OEM support portal, the Microsoft Store, or your approved package source — the report records item-specific reinstall guidance.

Yes. Deploy the MSI with standard Windows Installer properties and push a policy.json alongside it. See unattended deployment. Ring-test each OEM model in dry-run first — product names and silent flags vary by model and release.