Skip to content

SysManager 1.68.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Aug 07:15
· 513 commits to main since this release
v1.68.0
4f98cfd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[1.68.0] - 2026-08-25

The automatic restore point now covers the tab where you would most want it. Turning a privacy switch
off through Tweaks Hub took a Windows restore point first; making the identical change from another tab,
or removing OneDrive, took none. Same risk, different answer depending on which page you happened to
open — and the unpredictable version of a safety net is the worst kind.

Added

  • Edge/OneDrive Remover now takes a restore point before its first change, like Tweaks Hub already
    did. It is attempted before the change rather than after, because a snapshot taken afterwards records
    the state you are trying to get back from. The Restore buttons count too — putting Edge back is a
    system change like any other.
  • One restore point per session, not one per tab. Windows allows roughly one a day, so two features
    each making their own meant the first one used up the allowance and the second reported "no restore
    point" while a perfectly good one existed. Tweaks Hub and Gaming Profile each had their own private
    copy of that logic; there is now a single shared one, and a test refuses a second.

Changed

  • The restore point is still only ever mentioned when one was actually created. System Restore is
    switched off on many PCs and needs administrator, so a silent "no" is normal — and claiming
    protection that did not happen would be worse than not offering it.

Verify the download

Get-FileHash .\SysManager-v1.68.0.exe -Algorithm SHA256

Expected SHA256: 91085DB7A2F95FE717CD85D1D50BFB4D11023CB04A76F1A42A5F81C0F6C702C0

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.68.0.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.68.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.

Assets 5
Loading