Skip to content

SysManager 1.75.22

Choose a tag to compare

@github-actions github-actions released this 01 Sep 11:39
· 54 commits to main since this release
b269faa

[1.75.22] - 2026-09-01

Pressing "Run as administrator" could ask you whether to keep SysManager running in the notification area, and
then not restart with administrator rights at all. The same thing could happen when quitting from the
notification-area icon.

Fixed

  • "Run as administrator" now actually restarts SysManager with administrator rights. Every tab that needs
    administrator rights offers that button, and it works by starting a new copy of SysManager and closing the
    current one. Closing it went through the same path as pressing the X button — so if you had never told
    SysManager what X should do, it stopped to ask whether to keep running in the notification area. That
    question is the right one when you press X and completely wrong here, and while it sat on screen the new
    copy was waiting for the old one to finish letting go. It gave up after a few seconds. The result was a
    confusing question followed by nothing happening. The question is now only asked when you press X, which is
    the only time it makes sense.
  • Quitting from the notification-area icon no longer asks whether to keep running in the notification area.
    The same cause, and the same nonsensical question — you had just told it to quit.

Verify the download

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

Expected SHA256: DC9147BB899D6E17A07B95E2AA560DB22E9C3450CFF794C61C14CC7E89F9F115

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