SysManager 1.130.12 አውርድ

[1.130.12] - 2026-10-20
App Blocker recognises the blocks older versions wrote on a PC where Windows is not in C:\Windows, and a program
name too long for Windows is refused with the tab's own message instead of an error box.
Fixed
- App Blocker could neither show nor lift a block an older version wrote, where Windows is not in C:\Windows.
Versions before 1.33.11 stored a block as C:\Windows\System32\SysManager_Blocked.exe, and later versions
recognised a block only by the path to their own system folder. Where Windows is installed elsewhere, such a block
still kept the program from starting, but the tab did not list it, so it had no Unblock button, the Dashboard's
warning about a block that cannot be lifted could not see it, and blocking the program again was refused as
another program's debugger. A block is recognised by that file name now, wherever the path points. Since 1.33.11.
- A very long program name made Block fail with an error box. Windows limits a registry key name to 255
characters, and a pasted name longer than that reached the registry and failed there with an error SysManager did
not catch, so the generic error box appeared instead of the tab's own message. Such a name is refused as not a
valid program name now, and the box takes at most 255 characters. Since App Blocker was added (0.34.0).
Verify the download
Get-FileHash .\SysManager-v1.130.12.exe -Algorithm SHA256
Expected SHA256: D090313FF732E865D4B1A8B13F97BCC8FFE1DD5781F5D946935C05020A22DE7D
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.130.12.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.130.12.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.