Lataa SysManager 1.78.8

[1.78.8] - 2026-09-08
App Blocker's Unblock button asked you to confirm even when it could not do the job. Without
administrator rights it would show the confirmation, quietly fail every change, and report "Unblocked 0
applications" without saying why — while the Block button on the same tab had always refused up front and
explained itself. Unblock now does the same. It also says how many it could not change, instead of
reporting the number that worked as if it were all of them.
Fixed
- App Blocker — Unblock now refuses without administrator rights instead of failing silently.
Unblocking writes the same protected Windows setting that blocking does, so without admin every change
fails. The command checked nothing: it showed a confirmation promising the applications "will be allowed
to run again", tried anyway, and reported a count of zero with nothing connecting it to permissions. It
now checks before the confirmation, so it never asks permission for something it cannot do, and says
"Unblocking requires administrator privileges." The check sits ahead of the dialog on purpose — behind
it, the wording would have been right while the user had still been asked.
Changed
- App Blocker — a partly successful unblock says so. Even with administrator rights an individual
change can fail, and "Unblocked 2 applications" after selecting three read as complete success. It now
reports "Unblocked 2 of 3" and how many could not be changed.
Verify the download
Get-FileHash .\SysManager-v1.78.8.exe -Algorithm SHA256
Expected SHA256: 9978B9DA4FC1D6001C7F7752A6274AB3B1C6D7CF18CE61C37E8CB9B8142EF038
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.78.8.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.78.8.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.