SysManager 1.101.1

[1.101.1] - 2026-09-14

A scheduled cleanup now shows up in the app's history. Scheduled Maintenance exists to run while you
are not watching — and that was the problem: it ran, deleted temporary files, and SysManager's own recent
activity had nothing to say it had ever happened. The same cleanup started from the button had always been
recorded. Both actions a schedule can run now appear in the history, marked as having come from the
command line, so "did my weekly cleanup actually run, and did it find anything?" is answerable by opening
the app.

Fixed

• Temp cleanup and standby-memory purge run from the command line — which is how Scheduled Maintenance
  runs them — are recorded in the activity history, with how much was freed. They previously left no
  trace, while the same two operations started from their buttons were both recorded.
• The history entry uses the same name as the button version, so the list still reads by what was done
  rather than splitting one operation into two kinds of entry; where it came from is in the detail line.
• The read-only health score deliberately records nothing. It changes nothing, and a script polling it
  would push all 60 entries out of a history whose whole purpose is to be the record of what the app
  changed.

---

Verify the download

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

Expected SHA256: C2B0C2948E9595A40AC50663C01076CAA0E50BF75C779564E670D4726FA90E1E

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