Lataa SysManager 1.113.8

[1.113.8] - 2026-09-24
SysManager no longer says it made a restore point when Windows declined to make one. Windows allows
one restore point a day, and a second request within 24 hours was reported as "Restore point created" —
on the Restore Points tab and on every tab that takes one automatically before its first change — while
no new point existed.
Fixed
- A restore point is reported only when Windows really made it. Windows allows one restore point every
24 hours. When asked again within that time — after Windows Update or a driver install has made one, a
second click, or SysManager's own automatic point from earlier the same day — Windows PowerShell
answers with a warning rather than an error. SysManager only stopped on errors, so it carried on and
reported "Restore point created". Every tab that relies on the automatic point did the same: Defender,
Edge & OneDrive, Privacy, Windows Features, Tweaks Hub, Gaming Profile, Debloater and Performance. It now
stops on that warning too, so those tabs say nothing about a restore point, and the Restore Points tab
shows its existing message: Windows allows only one every 24 hours. Present since the Restore Points tab
was added in v1.23.0.
- Restoring to a point is reported only when Windows accepted the request. A restore that failed —
the point was gone, or System Restore was off — was reported as "Restore initiated — the system will
restart." with no restart coming. It now says the restore could not be started.
Verify the download
Get-FileHash .\SysManager-v1.113.8.exe -Algorithm SHA256
Expected SHA256: C0554114B980AAFD125B74722097A5E10BEAC7D0A2713B4C0B1AC37E5F20830D
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.113.8.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.113.8.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.