SysManager 1.75.14

[1.75.14] - 2026-09-01

App Blocker refuses to block one more Windows file. Blocking it was possible, and it would have stopped
Windows ever asking you for permission again — including the permission needed to undo it.

Fixed

• App Blocker will no longer block the Windows permission prompt. App Blocker stops a chosen program
  from starting, and it already refuses the handful of Windows files that the computer needs in order to
  start at all. Missing from that list was the small Windows program that draws the "Do you want to allow
  this app to make changes?" box. Nothing stopped you picking it — the file browser accepts it like any
  other program — and blocking it would have meant Windows could never ask for permission again. Undoing
  the block needs permission, so there would have been no way back from inside SysManager, or from anywhere
  else on the running computer. It is now refused like the others.
• The refusal message says what is actually true. That message read "is required for Windows to start …
  could leave the computer unable to boot", which was right for the files already on the list and wrong for
  this one: Windows starts perfectly well without the permission prompt, and the damage only shows up the
  first time something needs it. The message now covers both cases without claiming the wrong one.

---

Verify the download

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

Expected SHA256: 7505FF978EEC9EB1DD5D028CAEFE8F79B2B5EF6EEFB1AF8042FCC40F889F4C0E

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.75.14.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.75.14.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.