SysManager 1.56.1

What's new for you

SysManager 1.56.1 makes app removal safer and more predictable. The Uninstaller now runs actions only from a normal session, lets each package request Windows approval when needed, and reports cancellations, failures, and restart-required removals accurately.

[1.56.1] - 2026-07-28

Security

• Prevented the Uninstaller from acting as a privileged execution broker. Scan remains available in an administrator session, but uninstall actions are disabled until SysManager is reopened normally. This applies to both direct registry commands and the WinGet route, so user-controlled package metadata can no longer inherit SysManager's elevated token.
• Hardened registry-command validation. Trusted shared-data paths now come from the canonical Windows known folder instead of the mutable ProgramData environment variable. Local commands must identify the canonical absolute executable that is actually launched, bare rundll32 payloads resolve only from System32, and Windows Installer product-code commands must match the complete supported argument grammar; appended packages, transforms, and other payloads are rejected.

Fixed

• Let each local uninstaller own its UAC request. In an unelevated SysManager session, validated registry uninstallers now launch through the Windows shell. An uninstaller whose manifest requires administrator rights can therefore show its own Windows UAC prompt without requiring SysManager itself to remain elevated.
• Made cancellation and batch outcomes truthful. Cancelling while WinGet or a local uninstaller is queued now prevents an unobserved process start, completed processes win a late cancellation race, cancelled or failed batches retain partial progress, and successful removals that require a restart are reported as success with restart guidance.

---

Verify the download

Get-FileHash .\SysManager-v1.56.1.exe -Algorithm SHA256

Expected SHA256: B680BB77E84C273EC1CB59BA68C9A32B1C6849A9A3955955C4AC44952475F4A3