Preuzmi SysManager 1.136.95 za Windows

[1.136.95] - 2026-11-03
Restore backup on Environment Variables says what it will change and counts what it did, and Apply names what blocks a backup.
Fixed
- Restore backup asked only whether to restore "the original environment", though a backup kept since your first
Apply also takes out the folders installers have added to PATH since, and removes their variables. It now lists
each variable it would change, as Undo Changes does, and says when there is nothing to restore. It rewrote every
variable in the backup and counted each, so a restore that changed one could say it restored dozens; it now
changes and counts only what differs.
- After a restore, a variable with a space in its name, which Windows allows, was counted as one that "needs
administrator rights", even running as administrator, and without administrator so was every machine-wide variable
in the backup, changed or not. Such a name is now left as it is and named, and "administrator" is said only for a
machine-wide change while SysManager is not running as one. This was there since 1.56.3.
- A value among your variables that is not text, such as a number an installer stored there, stopped every Apply
with "The existing safety backup is invalid", with no backup there and nothing on the tab to change it. Apply now
says which variable stops the backup and why. This was there since 1.56.3.
Verify the download
Get-FileHash .\SysManager-v1.136.95.exe -Algorithm SHA256
Expected SHA256: AB27D20F8542C74783315FFDD0FACECB6B6001ED92C1B7B1C5970A8886DBB6A7
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.95.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.95.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.