SysManager 1.136.33

[1.136.33] - 2026-10-31

The memory check counts memory errors only, and a memory test that passed no longer reads as a
warning.

Fixed

• The Dashboard and System Health counted PCI Express, processor and AMD northbridge errors as RAM
  errors, and not the errors Windows files under memory. Laptops often log PCI Express errors from
  power-saving ports, and such a laptop was told "test your RAM", by a test that could not find the
  cause. The check now counts the errors that Windows' own event definitions give to memory. This
  was there from the first version.
• A Windows Memory Diagnostic run that found no errors read "Memory diagnostic ran 1 time — check
  results" in yellow, and one that found errors left the tile green with "No memory errors (30
  days)". A test that found errors now reads "The memory test found errors — your RAM may be
  faulty" in red, and one that passed reads as no errors. This was there since 1.20.40, and before
  that every result counted.
• System Logs explained a memory test that passed as "Windows Memory Diagnostic detected memory
  errors" with "Your RAM is likely faulty", under a message saying the test detected none. It now
  says the test found no errors, and the results that found errors, which had no explanation, say
  the RAM is likely faulty. The memory check and System Logs read the same list of results now.

---

Verify the download

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

Expected SHA256: 1047468F1AD6128940B7EAB1121100214AF0DF1A5313348F705D8097A83C33E5

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