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.80.0
| 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.80.0] - 2026-09-09
Startup Manager now shows where each entry actually lives: a registry Run key and which hive it is in, a
Startup folder, or Task Scheduler. The app had worked this out for every entry since the tab shipped and
then kept it to itself. It matters because entries are not equal. Turning off an all-users entry needs
administrator rights, and one placed by a system policy cannot be turned off from this tab at all, yet all
three looked identical in the list.
Added
- Startup Manager — a Location column. Every scan filled Location in for all three sources, the tests
asserted it was never blank, and no column bound it, so the work was thrown away on every refresh
(#1587). The column sits after Publisher with the same styling, ellipsizes from the end so the hive stays
readable, and puts the full path on hover.
Changed
- A field the startup scan fills in must now be shown or declared logic-only. The build fails on a third
option, which is what Location had been for as long as the tab existed. Source, RegistryKey,
ValueName and TaskPath are named as steering the toggle and the Open button rather than being
displayed; anything else added later fails until someone decides which it is. The check also runs per
construction site rather than over their union, because a field dropped from one of the three would leave
that one source blank while the other two looked correct — the hardest kind of gap to notice.
Verify the download
Get-FileHash .\SysManager-v1.80.0.exe -Algorithm SHA256
Expected SHA256: AA8931D0866B89F5079FEDBC75F9112121C54A612ADB29E1D9E2F1BB334ACD0E
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.80.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.80.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.80.0