SysManager 1.136.66 yüklə

[1.136.66] - 2026-11-02
System Health reads no errors as 0, no longer calls a drive Healthy when nothing could be read from it, and colours a drive's temperature the way its verdict reads it.
Fixed
- A drive whose error counters were read showed "—", which means not reported, for read and write errors when
there had been none: a reported 0 was turned into "not reported". It reads 0. This was there since 1.127.7.
- A drive Windows gave no health status for, with nothing read from it, as without administrator rights, was
called "Healthy." in green, or "Healthy — N h on" from its power-on hours alone. It says Windows could not
report this drive's health, in grey. This was there since 0.3.0.
- A drive Windows reports as failing showed its health gauge in amber under the red "Drive is failing": its score
is capped at 20, which is where the amber band starts. The gauge is red. This was there since 1.57.6.
- System Health coloured a drive's temperature amber from 41 °C and red above 60 °C while its verdict warns only
from 70 °C, so a drive at 62 °C read red beside a green "Healthy — 62 °C", and the Dashboard showed the same
reading in blue. Both now use one scale: green to 50 °C, blue while warm, and amber from 70 °C, where the
verdict says the drive runs hot. System Health's scale was there since 0.16.0.
Verify the download
Get-FileHash .\SysManager-v1.136.66.exe -Algorithm SHA256
Expected SHA256: 44C38526463CB6D0901C8A6C83FE3393A93D79BF5E673549EC662669F7C6F441
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.66.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.66.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.