Descargar SysManager 1.136.137 para Windows

[1.136.137] - 2026-11-06
On Windows Features the note about administrator rights comes before Scan now, and App Blocker, File Shredder and
Shortcut Cleaner show their lists in a card like the other list tabs.
Fixed
- On Windows Features the Scan and Search toolbar sat between the heading and the banner that says why the tab needs
administrator rights, so someone without them met Scan first, on screen and with Tab, and read why the list stays
empty only after it (since 1.7.7). The banner comes straight after the heading now, as on the 31 other tabs that
carry it. On Shortcut Cleaner the banner sat 16 px under the heading, where the other tabs laid out the same way
leave 12 (since 1.43.0). Two checks fail the build: one when a control comes between a tab's heading and its
banner, one when a banner on that layout leaves the 12 px gap.
- App Blocker (since 0.34.0), File Shredder (since 1.4.0) and Shortcut Cleaner (since 0.32.0) drew their list straight
on the page, where Startup Manager, Uninstaller, Services and the other list tabs put theirs in a card with an edge
and rounded corners. The difference showed most on the light themes. Each list and its empty message sit in a card
now. On File Shredder and Shortcut Cleaner that card sits 16 px under the toolbar, as on Quick Cleanup, instead of
12. App Blocker's two rows of buttons are wrapping card toolbars like Uninstaller's, and the faint divider
between Refresh and Select All, the only one on a toolbar in the app, is gone, so the two buttons sit 16 px apart
where they were 49. A check fails the build when a list sits outside a card.
Verify the download
Get-FileHash .\SysManager-v1.136.137.exe -Algorithm SHA256
Expected SHA256: E98D271FFC10C95275E9522C607FB6EBFBEF8E4EA0D2900F1FE2FECE5431BE29
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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.136.137.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.136.137.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.