SysManager 1.114.20: prenos za Windows

[1.114.20] - 2026-09-28
Drivers now says when a scan failed, instead of reporting "0 drivers found". When Windows reports an error
part-way through a scan, the drivers it did list are shown with a note that some may be missing.
Fixed
- Drivers: a failed scan is not "0 drivers found". The scan ignored the exit code, so a query that failed
outright reported "0 drivers found", "Done" and a "Driver scan complete" notification.
- It now says the drivers could not be read, and keeps the list from the previous scan.
- When Windows reports an error part-way through, the drivers it did list are shown, with a note that some
may be missing.
- Output that cannot be read counts as a failed scan. Its message used to be replaced by "Done" at once.
Present since the tab was added in v0.3.0; the replaced message since v0.27.0.
Verify the download
Get-FileHash .\SysManager-v1.114.20.exe -Algorithm SHA256
Expected SHA256: C6756325FD9E3D396E39767709C05876AAF350F5F2AAA0708270569A06BB336C
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.114.20.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.114.20.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.