SysManager 1.75.2

[1.75.2] - 2026-08-26

Timer Resolution had the two ends of its range the wrong way round, so "Enable" asked Windows for the
slowest timer instead of the fastest one. The tab reported a 15.6 ms best case and a 0.5 ms worst
case — exactly backwards — and Gaming Profile's "Finest timer resolution" switch had the same
problem, promising 0.5 ms while requesting the 15.6 ms default.

Fixed

• Timer Resolution now really requests the fastest timer your hardware supports. The Windows call
  that reports the achievable range returns the slowest value first and the fastest second; its
  parameter names say the opposite ("Minimum" means minimum precision, i.e. the longest interval), and
  SysManager had trusted the names. Measured on real hardware the call returns 15.625 ms, then
  0.5 ms, then the value in effect. The two are now read in the order the call actually uses, so the
  tab shows the right numbers, Enable asks for the fast end, and the Gaming Profile switch does what
  its label says. If you had used either one for lower input latency, it was not doing anything —
  it now does.

---

Verify the download

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

Expected SHA256: E0F8A1D14EDDBD3D8740B0A522B37B7A7501E2688F6F7CFCB7D56491041F22EF

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