SysManager 1.131.1

[1.131.1] - 2026-10-27

Store apps and many installed programs can now actually be uninstalled — they used to be listed, tickable,
and then refused with "Invalid package ID".

Fixed

• Most Store apps, and many ordinary programs, could be ticked for removal and then never removed. Windows
  gives some apps no public identifier, so winget lists them under a local one instead — MSIX\… for a Store
  or packaged app, ARP\… for a program known only by its registry entry. SysManager checks every identifier
  before it goes anywhere near a command line, and that check had no room for the backslash those use, so the
  Uninstaller let them be ticked, asked for confirmation with "This cannot be undone", and then failed each one
  with "Error: Invalid package ID. (Parameter 'packageId')". On the machine this was traced on, 103 of 182
  installed apps had an identifier of that kind. Those identifiers are now recognised, with their own rule
  rather than by loosening the check that protects everything else, and winget removes them the same way it
  removes anything else.
• An app SysManager genuinely cannot remove now says what to do instead. It used to show the raw
  programmer's error text; it now says the app has to be removed from Windows' own Settings > Apps page.

---

Verify the download

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

Expected SHA256: C57A998C86654EC6781136D340D0356AF38041B2B338A671CCC4E10C572BA7C2

This build is not code-signed, so Windows will warn on first launch. That is
expected for a small independent app: see what the warning says and what to
click.
Code signing is planned through the SignPath Foundation,
which provides free certificates to open-source projects, with signing performed by
SignPath.io. Until then, the SHA256 above and the build
attestation below are what establish that a download is the genuine build.

Code signing policy

This release is not code-signed. The team roles, release-approval process and
privacy policy required by the SignPath Foundation programme
are documented in advance under Code signing
policy. That
documentation is a prerequisite for applying, not evidence of a certificate. The
attribution line naming SignPath as the signing provider will appear here once a
certificate is actually issued.

This program will not transfer any information to other networked systems unless
specifically requested by the user or the person installing or operating it. Full
privacy policy.

Verify where this binary came from

This exe was built by GitHub Actions from this public source, and the build is
recorded in the Sigstore public transparency log. With the
GitHub CLI:

gh attestation verify .\SysManager-v1.131.1.exe --repo laurentiu021/SystemManager

That proves which commit and workflow produced this exact binary, something the
SHA256 file cannot show, since it is published alongside the exe it describes.
Each release also ships SysManager-v1.131.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.