SysManager 1.116.0

[1.116.0] - 2026-10-05

The System Report now starts with what is wrong. Before the list of hardware it shows the same health score
and "what to do" list as the Dashboard, and the recent problems Windows logged, so whoever you send the report to
can read the verdict in seconds.

Added

• A health section at the top of every System Report: on screen, and in the text, HTML and JSON exports
  (#1508). The report listed the hardware and said nothing about how the PC was doing, and the score and its
  advice were only on the Dashboard, a screen the person helping you never sees.
  • The overall score and its label, each part of the score (disk health, free space, memory, uptime, and battery
    on a laptop), and the Dashboard's "what to do" list. A part Windows gave nothing for says "could not be read"
    instead of showing the in-between score used for it.
  • Up to five recent problems from the Windows System log: critical and error events from the last 7 days,
    grouped by source and event ID with how many times each was logged, critical first, then newest. Where
    SysManager has a plain-English explanation and advice for the event, they are included; otherwise the source
    and ID are listed, which is what to search for.
  • An event's own message is never included. It can name files, user names and computers, which the report
    keeps out, and the HTML footer now says so.
  • When the System log cannot be read the report says that, rather than reporting no problems. The read stops
    after 15 seconds, and the report is then built without the list.
  • Long explanations are wrapped, so the on-screen preview needs no scrolling sideways.

Changed

• The System Report shares the Dashboard's scoring instead of computing anything of its own, using the
  readings it already takes for its other sections, so the two can never disagree.

---

Verify the download

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

Expected SHA256: 78A9ED67016B3A056F19084286057DAE62577F7BF790E643F045E7748DE55EF7

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