Aquesta és una versió anterior. La versió actual és la 1.130.86. SysManager 1.130.86 · Data de publicació:
Fitxers d’instal·lació 1.76.25
| 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.76.25] - 2026-09-07
Six tabs told you a list was empty with one small grey sentence floating in a large blank card, while thirty
others gave you an icon, a headline and a plain-English next step. They now all look the same, and three of
them explain the thing that actually confuses people: the list is empty because a search or filter is hiding
everything, not because the feature is broken.
Fixed
- Services, Startup, Task Manager, Windows Features, DNS & Hosts and Speed Test use the same empty state as
every other tab. These six drew their own one-line message instead of the shared control, so they had no
icon and no headline — and two of them were not even centred, reading as a stray caption rather than an
empty state. Seven places in total; the shared control is now used everywhere.
- Three of them now say why the list is empty. "No processes to show" on its own is alarming. Where the
list is empty because a search term or a filter matches nothing, it now says so and tells you to clear it —
Task Manager, Windows Features and Services.
- DNS & Hosts explains what an empty hosts file means instead of just noting there is nothing to show.
Added
- A check that no tab can hand-roll its own empty state again. The six were not an oversight of taste:
none of them declared the namespace the shared control lives in, so it was simply unreachable when they
were written. The check now catches that, and it is scoped so the "No battery detected" and "No NVIDIA GPU
detected" notices — which are facts about your hardware inside a working card, not empty lists — are
correctly left alone.
Verify the download
Get-FileHash .\SysManager-v1.76.25.exe -Algorithm SHA256
Expected SHA256: 87916D1EB777F0CAE9C81088B76DC0C867B07045A17C947163D30CAD2B89F698
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.76.25.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.76.25.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.76.25