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.113.13
| 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.113.13] - 2026-09-24
Five more places now say what actually happened. Windows Features no longer reports "Found 0 features"
when Windows refused to list them. Settings Watchdog no longer says a baseline was saved when it was not.
Profile import says how many sections it could not apply. The hosts editor says a change waits for
Save, and Browser Cleaner no longer says it cleaned when nothing was removed.
Fixed
- Windows Features: Scan explains that listing needs administrator rights. Windows shows the list of
optional features only to an administrator. From a normal launch the query failed silently, and the tab
reported "Found 0 features (0 enabled)" under a "scan complete" toast. A refused scan now says Windows
shows the list only to an administrator and points to Run as administrator. An elevated scan that fails
is reported as a failure. The banner now says listing needs administrator rights too. Present since the
tab was added in v0.46.0.
- Settings Watchdog: "Baseline saved" only when it was. A baseline that could not be written — a full
disk, a folder that cannot be written — was caught and dropped, and the tab still said it was saved and
recorded the save in Recent Activity. The tab now says the baseline could not be saved, and why. Present
since the tab was added in v1.48.0.
- Profile Export / Import: an import says what it could not apply. Sections the import skips — one
from a newer SysManager, one that fails the import check, one that cannot be written — were only logged,
and the tab reported the applied count under a "Profile imported" toast even when nothing was applied.
It now says "Imported 2 of 3 sections — 1 could not be applied", and reports an import that applied
nothing as nothing imported, without the toast. Present since the tab was added in v1.28.0.
- DNS & Hosts: add and remove say the change waits for Save. "Added …" and "Removed …" read as done,
but only Save writes the hosts file. Leaving the tab after removing a blocking entry kept the entry in the
file. Both messages now say to press Save. Present since the hosts editor was added in v1.6.0.
- Browser Cleaner: no "Browser data cleaned" when nothing was removed. An open browser can hold every
file, and the toast — often the only result left once the rescan replaces the status — still said the
data was cleaned. It now says nothing was removed and suggests closing the browser and cleaning again.
Present since the tab was added in v1.31.0.
Verify the download
Get-FileHash .\SysManager-v1.113.13.exe -Algorithm SHA256
Expected SHA256: 50804B13CEA6A0180261CB03F237A3F231BA15CE9AA926946F39DDAE59E49B3B
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.113.13.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.113.13.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.113.13