SysManager 1.130.76

[1.130.76] - 2026-10-22

An empty entry in a saved history or preset file no longer breaks the tab that reads it: the entry is skipped and
the rest still load.

Fixed

• Disk Analyzer ended every analysis in an error. An empty entry among its saved scans, or one without its
  folder, is valid in the file, which a hand edit, a sync tool or a damaged write can leave, and the comparison with
  the last scan threw on it. Since 1.73.0.
• Speed Test failed to save every result. An empty entry in its history threw each time the history was read
  or written. Since 0.41.0.
• Volume Control's presets could not be saved, deleted or applied. An empty preset, one without its name or
  its list of apps, or an empty app in one, threw. Since 1.55.0.
• Recent Changes could not load. An empty entry in the activity history was in every list it read, and it was
  written back with each new entry. Since 1.125.0.
• Gaming Profile would not open. Settings saved or imported as nothing at all reached the tab, which threw as
  it was built, on every start. An imported profile like that is now skipped, and saved settings like that load
  the defaults. A record of a game mode session missing part of what it needs is reported as one that cannot be
  used, rather than breaking the offer to undo it. Since 1.52.38.

---

Verify the download

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

Expected SHA256: 8D844305175920B604359E806644013690F921D08D9BED29DC35ED3C8549BA60

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