Aquesta és una versió anterior. La versió actual és la 1.131.0. SysManager 1.131.0 · Data de publicació:
Fitxers d’instal·lació 1.130.74
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
[1.130.74] - 2026-10-22
The Dashboard no longer freezes over a drive that is slow to answer, one drive it cannot read no longer empties its
storage card, and the health score judges free space by what the drive really has.
Fixed
- The Dashboard could stop responding as it opened and on every Scan system. Its storage card asked each drive
letter whether it was ready, on the window's own thread, before checking whether it was a local drive at all, so
a mapped network drive whose server could not be reached, or a disc drive spinning up, held the window until
Windows gave up on it. It now asks only local drives, and away from the window. Since 1.17.0.
- One drive that could not be read emptied the storage card, and one that refused to be read stopped the
Dashboard from starting. Each drive is now read on its own: one that fails is left out and the others are
listed. Since 1.17.0. The drive list in About's copied environment info had the same flaw and stopped at such a
drive, losing the ones after it. Since 0.14.0.
- The health score rounded free space to whole gigabytes before comparing it with its limits. 9.7 GB free
counted as 10 and escaped the limit under 10 GB, and 19.7 GB counted as 20, which on a drive whose percentage
looked fine left out the advice to free up space. The score, and "Why is it slow?", which judges the drive the
same way, now compare the space as Windows reports it. Since 1.78.0.
Verify the download
Get-FileHash .\SysManager-v1.130.74.exe -Algorithm SHA256
Expected SHA256: 965AAC509F872C5A758B586ED1A8E79A400C7C554F2B2EFA94F9964C1605FF63
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.130.74.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.130.74.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.130.74
