Λήψη SysManager 1.113.10

[1.113.10] - 2026-09-24
Timer Resolution, Gaming Profile and OneDrive now report what actually happened. Turning the fast timer
off no longer claims the timer is back to normal while another program is still holding it. Game mode no
longer counts a timer request Windows refused, and no longer switches off a fast timer you had turned on
yourself. Reinstalling OneDrive no longer says "restored" when its setup failed.
Fixed
- Timer Resolution: turning it off says what the timer actually did. Windows runs the timer at the
fastest rate any program asks for, so after SysManager lets go, a game, a browser playing video or a chat
app can still keep it fast. The tab said "back to the Windows default" regardless, while its own reading
showed otherwise. It now says when another program is keeping the timer fast, and names the value. The
status line shown when the tab opens had the same flaw for a timer held somewhere in between — 1 ms, for
example — which it called "the Windows default". Present since the tab was added in v1.35.0.
- Gaming Profile: the timer step no longer claims a success it did not have, or undoes your own
setting. The "Finest timer resolution" step counted as applied whether or not Windows accepted the
request. And because Windows keeps a single timer request per program, stopping game mode switched off
the fast timer when it was already on from the Timer Resolution tab. The step now counts only a request
Windows accepted, changes nothing when the fast timer is already on, and releases only a request it made
itself. Present since the step was written in v1.52.38.
- Edge/OneDrive Remover: restoring OneDrive reports failure when its setup fails. The setup's result was
thrown away, so a failed reinstall said "OneDrive restored." and put back a File Explorer entry for a
client that was not there. It now checks the result, as removal already did, and puts the entry back only
after the setup succeeds. Present since the tab was added in v1.53.0.
Verify the download
Get-FileHash .\SysManager-v1.113.10.exe -Algorithm SHA256
Expected SHA256: B324A16736B236B9A6A89A0E39CBD558C43C2AEE6FA79E790DB7B6E2715794E9
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.10.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.10.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.