Skip to content

SysManager 1.130.39

Choose a tag to compare

@github-actions github-actions released this 21 Oct 12:10
· 64 commits to main since this release
5f8d0be

[1.130.39] - 2026-10-21

Filter chips, menu items, buttons and tooltips built around a number or a name show all their words, and
Settings Watchdog's reasons have their tooltip.

Fixed

  • Services' filter chips showed only their counts. "Safe to disable" and "Keep enabled" read as two identical green
    pills with a number in each, and Running, Stopped, Not rated and Advanced as identical grey ones. Each chip now names
    what it filters beside its count, as in "Safe (12)". Since 1.10.0.
  • The right-click menus named only the row, on every item. On Services and Process Manager each item read just the
    service's or the program's name, "Kill" included, and a screen reader announced them the same way. Disk Analyzer's
    block menu read only the folder's name. Each item now says what it does, as in "Kill notepad.exe" or "Show AppData in
    Explorer". Since 1.104.0, and 1.119.0 on Disk Analyzer.
  • Three buttons showed only a number or a name. "Clear marks" on Services and System Logs read a bare count, and
    now reads "Clear 2 marks", or "Clear 1 mark". Bulk Installer's button for the chosen category read only the
    category, and now reads "Select Browsers". Since 1.61.6.
  • Settings Watchdog's reasons had no tooltip. The column trims a long reason, and the tooltip meant to show all of
    it, with the registry value the setting is read from, never appeared. It does now. Since 1.61.7.
  • System Logs' "SysManager's own logs" button had a tooltip of only a folder path. It now says that it opens
    SysManager's own diagnostic logs, and where they are. Since 1.56.10.

Verify the download

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

Expected SHA256: 9888A35B3DF09ECB7E84A8DD18F030D87B7FC37DA3D550665269E1A08317C589

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