Lataa SysManager 1.78.0

[1.78.0] - 2026-09-07
The health score now counts how much room is left on your Windows drive, and that will change the number you
see. A PC with a nearly-full drive could score "Excellent" before — the worst thing a health score can do,
because a full drive is the commonest reason a computer feels slow and it is what stops Windows installing its
own updates.
Fixed
- A PC that is out of room can no longer score "Excellent", or even "Good". As long as the drive's SMART
status was fine, memory was under 60% and it had been restarted recently, the score said everything was well
while the actual problem sat there unmentioned.
Added
- The score says how many GB are left, and where to get more. "Only 4 GB free on C: — Deep Cleanup can
reclaim space" now appears first among the recommendations, because it is the only one of them you can act on
today, in this app. A worn battery and an ageing disk are real and SysManager cannot fix either.
- Big drives are not scolded for being big. 400 GB free on a 4 TB disk is only 10% and nothing whatever is
wrong, so a comfortable amount of space in gigabytes outweighs an unimpressive percentage. It works the other
way too: 9 GB free on a small laptop drive is 22% and still not enough for Windows to update itself, so the
percentage does not get to call that healthy.
- Only the Windows drive counts. A deliberately packed archive drive does not slow your PC down, and being
told your machine is unhealthy for a disk you filled on purpose is noise.
- --health --json reports the free-space component, so a script can see why a score is low.
Changed
- Your score may read lower than before with nothing changed on your PC. That is the new component being
counted, not a fault appearing. If it dropped, the recommendation on the Dashboard says why.
Verify the download
Get-FileHash .\SysManager-v1.78.0.exe -Algorithm SHA256
Expected SHA256: 445D993B725CC8D700E9CBA37FBEC827FDB65295CBC46DDC1553B2A83CD92B5B
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.78.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.78.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.