Lataa SysManager 1.64.13

[1.64.13] - 2026-08-13
Pressing Enter on a confirmation prompt no longer approves it. Every "are you sure?" now starts on
the safe answer, so an accidental keypress cancels instead of going ahead.
Fixed
- A stray Enter could approve a confirmation you hadn't read. Every prompt that asks you to confirm something — shredding files, ending a process, removing built-in apps, uninstalling, applying a preset — opened with Yes already selected. So pressing Enter, or pressing it a second time after the key that opened the prompt, went straight ahead with the action. All 76 of those prompts now open with No selected: Enter cancels, and choosing Yes still takes a single click or keypress. The same applies to the prompt you get when closing the window, which now starts on Cancel — its behaviour finally matches what it already promised, since Esc and the window's X have always meant "leave things alone".
Verify the download
Get-FileHash .\SysManager-v1.64.13.exe -Algorithm SHA256
Expected SHA256: 89E5EA224AFD93926C812F109B8FBA2E52214F9C8FFC5FB93C5053DD3E3621E2
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.13.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.13.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.