SysManager 1.130.9

[1.130.9] - 2026-10-20

When installing an update stops short, the About tab now says so as a problem, and Scheduled Maintenance no longer
hides two errors.

Fixed

• A refused or failed update install was shown as a finished download. When Install stopped, for example because
  the download did not match its published SHA256 hash, the reason took the place of the text in the green "Download
  complete" line, on one line cut off at the card's edge, with Install still offered beside it. It is shown in an
  amber line that wraps now. A download that fails its hash check, or whose signature cannot be read, is deleted, and
  Download and Manual download come back in place of Install. When the hash could not be fetched, the running copy
  could not be found or the new version would not start, the file is kept and Install is offered again, and the
  message for a hash that could not be fetched now says to check the connection instead of calling the file
  corrupted. Since 0.28.22.
• Downloading again after a refused install brought back the same file. The update cache keeps the hash of each
  download beside it and reuses the file while the two match, which they do for a damaged download too, so Download
  returned the refused file at once and Install refused it again. A refused file is deleted with its stored hash now,
  so the next download fetches it again. Since 0.48.24.
• Scheduled Maintenance could show "Not run yet" for a schedule that had run, and leave nothing in the log when
  Remove failed. Two of its PowerShell calls still let an error pass without a word. When Windows could not report
  the task's last run, the page showed Last result "Not run yet"; it says now that the schedule could not be read.
  When Windows refused to remove the task, the page said "Could not remove the task. Check the log." and the log held
  no reason; the reason is written there now. Since Scheduled Maintenance was added (1.50.0).

---

Verify the download

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

Expected SHA256: 4CB37A03E41B3AF1E542789DF76993ECB696A19FDE891302B38AACC79B823232

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