Shkarko SysManager 1.136.15

[1.136.15] - 2026-10-30
Install and Go back no longer close SysManager for good when it runs from Program Files,
and Go back offers the version you had before the last update and nothing else.
Fixed
- Install and Go back closed SysManager, and nothing reopened, when it ran from Program Files
or another folder Windows protects. The part that replaces SysManager refuses such a folder,
but it decides only after SysManager has closed, so its refusal reached the log and nothing
else. SysManager now asks the same question before it asks you anything, and says why it
can't update itself there; Install offers Manual download in its place. A folder SysManager
cannot write a new file to is refused the same way. Present since 1.64.2.
- An update that failed once SysManager had closed still replaced the kept previous version
with the one running, so Go back offered the version already in use. The outgoing version is
now kept under a separate name until the update has landed, and dropped if it does not.
Present since Go back arrived in 1.61.0.
- After going back, Go back stayed offered, for the version just restored. Going back now keeps
nothing in the kept copy's place and takes Go back away once it has landed. An update that
could not keep the version it replaced also takes it away, rather than offering an earlier
update's copy as the version before the last update. Present since 1.61.0.
Verify the download
Get-FileHash .\SysManager-v1.136.15.exe -Algorithm SHA256
Expected SHA256: B0B4E599C89D56B8D2D55A2A71B740F348FC6CD0E39BD7D32741D9DC7401A5A0
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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.136.15.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.136.15.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.