Lataa SysManager 1.130.71

[1.130.71] - 2026-10-22
SysManager opens for each Windows account, even while another account's copy is running, and starting it again
keeps bringing its window back.
Fixed
- SysManager did not open while a copy was running for another Windows account. One single-instance check
served the whole PC, so with a copy left in the notification area by another account, under fast user switching,
or by the account "Run as administrator" switches to, a new start was refused by that copy's lock or by its
activation pipe, and ended before it wrote anything to its log: no window and no log line. Each account now has
its own check in each session, and a refusal no longer ends the start. Since 0.13.2.
- Starting SysManager again could stop bringing its window back. The copy that listens for a second start
stopped for good on the first pipe error it met while running, which a second start causes when it leaves before
the wait begins. From then on, starting SysManager again while it sat in the notification area did nothing. A
start that leaves early now counts as one, and after any other error the copy logs it and listens again a second
later. Since 1.52.15.
Verify the download
Get-FileHash .\SysManager-v1.130.71.exe -Algorithm SHA256
Expected SHA256: 256BF96864F31740C0ADF7379B5386BC23FC758E80661D9831180B535007DBD1
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.71.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.71.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.