Baixar SysManager 1.130.45 per a Windows

[1.130.45] - 2026-10-21
System Fixes reads SFC's progress and result whatever language Windows is in, DISM no longer says no repairs were
needed after a repair, and Reinstall WinGet picks your own App Installer.
Fixed
- SFC's progress and result were never read. SFC writes its output as UTF-16, and System Fixes read it in the
console's code page, which put a NUL between every letter. The progress bar never showed a percentage or a time left,
and the verdict was always the exit code's: a green "Scan completed successfully." even when SFC found files it could
not repair. The output is read as UTF-16 now, and the verdict is matched against SFC's own messages, which the tab
takes from Windows in its display language, so it no longer depends on Windows being in English. SFC's other endings,
such as a repair waiting for a restart or another repair already running, say what to do next, and an ending the tab
does not recognise points to the console instead of being called a success. Since 0.14.0 for the verdict and 1.16.1
for the percentage.
- DISM said no repairs were needed after a repair. DISM ends with the same sentence whether it repaired Windows'
repair source or found nothing to repair, and the tab read it as "no repairs needed". It says the repair source is
healthy now and to run SFC next. Since 0.14.0.
- Reinstall WinGet could pick an older App Installer. On a PC with more than one account it registered whichever
copy Windows listed first, which can be an older one registered for another account, and Windows refuses that. It
registers your own App Installer now, or the newest one on the PC if you have none. Since 1.26.0.
Verify the download
Get-FileHash .\SysManager-v1.130.45.exe -Algorithm SHA256
Expected SHA256: 370F5C93C7C43605DE06030662578B59AEB5227444B224EDFA8737C810372FFE
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.45.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.45.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.