SysManager 1.136.94

[1.136.94] - 2026-11-03

The diagnostics bundle says exactly what is in it, and About's report buttons cope when Windows' management service fails.

Fixed

• About's diagnostics bundle named and counted its three newest logs before reading them, so one that could not be
  read was still listed in the README inside the zip and counted in "Saved … and 3 log files", though the zip did
  not have it. The README and the message now count and name the logs that are in the zip, and say which could not
  be read. The README also describes environment.txt line by line, from the lines in it; it left out the build, the
  .NET runtime, the graphics cards, the drives and the display. Both were there since the bundle came in 1.111.0.
• "Copy environment info" and "Save diagnostics bundle" raised the app's error dialog when Windows' management
  service failed in a way it reports as a COM error, such as the service being turned off, instead of leaving out
  what it could not read. They now leave it out, as the system report does; this was there since the environment
  info was read this way in 0.48.5. System Health's scan and disk check, Battery Health, the drive list, the
  Dashboard's health score, the command line's health check and the resource history's temperatures handle the same
  failure now too.

---

Verify the download

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

Expected SHA256: 718CE221202CFC1F1F58A43555CB40F2E40E80AF3E182C050062B7A278C4B701

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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.136.94.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.136.94.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.