Sækja SysManager 1.64.17

[1.64.17] - 2026-08-13
If the PC loses power or crashes while SysManager is saving, your settings and history survive
instead of coming back empty.
Fixed
- A crash or power cut while saving could silently wipe your history and presets. Seventeen places wrote your data by emptying the file first and then filling it back in. Interrupt that — a power cut, a crash, a full disk — and the file on disk is neither the old version nor the new one. Worse, the app treated a file it could not read as "no data", quietly starting from scratch: you would open the app and find your activity history, speed-test history, volume presets, gaming profiles or saved settings simply gone, with nothing explaining why. Saves now write to a second file and swap it in as one step, so an interrupted save leaves the previous version completely intact. Affects the Activity log, Speed Test history, Volume presets, Gaming profiles, theme and appearance settings, the close-behaviour preference, the standby and update preferences, the Settings Watchdog baseline, the service-startup ledger, the performance snapshot used to undo tweaks, restored configuration backups, and the app-icon cache.
Verify the download
Get-FileHash .\SysManager-v1.64.17.exe -Algorithm SHA256
Expected SHA256: EFC2A8117F74DD19C056BED7946F8390E6D76EBACFC64F3A0FF6A2845E3777B4
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.64.17.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.64.17.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.