Sækja SysManager 1.78.2

[1.78.2] - 2026-09-08
Running SysManager as administrator left a hidden powershell.exe behind every time a feature used one. They
were invisible, they never went away on their own, and each one held a few threads open inside SysManager. A
long session with a lot of Windows Update or disk-health checks accumulated them.
Fixed
- The helper SysManager starts for administrator tasks is now actually stopped when the task ends. It was
being let go of rather than closed — the difference being that letting go of something does not end it. Each
leftover kept its output pipes open, which kept threads inside SysManager waiting on them for nothing. In a
test run that used PowerShell hundreds of times, this left roughly 276 of them alive at once and over a
thousand stuck threads, until the run could no longer make progress.
Added
- A test that starts a real background process and proves the cleanup stops it. Written the awkward way on
purpose: the first two versions passed against code that did no cleanup at all, once because the stand-in
process was dying for an unrelated reason and once because the test never went through the real code path.
Verify the download
Get-FileHash .\SysManager-v1.78.2.exe -Algorithm SHA256
Expected SHA256: 3AEBF515C5E2159E21D016BB7F2D8E603B23E7F78214D00398E108D0BED02031
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.2.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.2.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.