SysManager 1.111.2 yüklə

[1.111.2] - 2026-09-18
If App Blocker ever blocked something it should not have, it now says so instead of leaving you to find
out. Version 1.111.0 and later refuse to block the processes Windows needs, the permission prompt, and
SysManager itself — but that only stopped new mistakes. A machine where an older version already blocked one
was left listing it as an ordinary entry, next to an Unblock button that could not work, with nothing
explaining why. Such an entry is now marked, raised on the Dashboard, and the warning carries the recovery
step. Nothing is removed automatically: it tells you and hands you the undo.
Fixed
- A block the app cannot lift is now identified instead of hidden in the list. consent.exe is the
Windows permission prompt, and unblocking writes a protected setting that needs the permission prompt to
approve it — so a block on it removes its own undo. Versions before 1.111.0 could write one. The blocked
list marks such an entry, and the tab shows what was lost and how to get it back.
- The recovery step is the right one for the state the PC is in. Running as administrator, the banner
points at the Unblock button. Not running as administrator — the case where no prompt can appear at all —
it names the exact registry value and location to delete, so the answer does not have to be found
somewhere else.
- The Dashboard reports it too. The damage is invisible until the first time something asks for
administrator rights, which makes the App Blocker tab the last place anyone would think to look. It is now
a red alert on the landing page that opens the right tab.
- One rule decides which targets are dangerous. The list of executables the app refuses to block, and the
check that recognises a block an older version already wrote, now read the same definition rather than two
copies that could drift apart about which entries matter.
Changed
- The block confirmation says what a block looks like. It reported only that the program would be
prevented from launching. What you actually see is a Windows error saying it cannot find
SysManager_Blocked.exe — a file that deliberately does not exist, because a path that does not resolve
is how the block works. That read as SysManager having broken something; the dialog now sets the
expectation, and repeats that nothing is deleted.
Verify the download
Get-FileHash .\SysManager-v1.111.2.exe -Algorithm SHA256
Expected SHA256: 5B321BEB1B6943D69E5226A18335BD63D5A57E08B6BEE1272B1EFCF80A32732C
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.111.2.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.111.2.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.