Lataa SysManager 1.102.0

[1.102.0] - 2026-09-15
You can now switch off the add-ons that make right-click slow. Context Menu already listed them — the
extras that archivers, cloud-sync clients and antivirus add to your right-click menu — but their switch was
disabled, so the tab showed you the problem and could not do anything about it. Now it can. Windows keeps a
list of add-ons it refuses to load, and switching a row off puts it on that list: nothing the program
installed is deleted, and switching the row back on takes it off again. Because the list applies to the
whole PC it needs administrator rights, and because Explorer decides which add-ons to load when it starts,
there is a Restart Explorer button so the change actually shows up.
Added
- Add-on rows in Context Menu can be switched off and back on, using the blocked-extensions list Windows
checks before it loads a shell add-on. The row's tooltip explains that this needs administrator rights
and applies once Explorer restarts, before you click rather than after.
- A Restart Explorer button in the Context Menu toolbar, which confirms first and explains that open
File Explorer windows will close. Without it a blocked add-on stays in the menu until the next sign-in,
which reads as the switch not working.
- Add-ons that were already blocked — here, or by another tool such as Autoruns — now show as switched off
instead of active, so the list matches what Windows is really doing and the block can be undone here.
Changed
- Add-ons implemented from inside the Windows folder are treated as system entries: hidden until you tick
"Show system entries", and never changed by a preset. They are part of the shell rather than something a
program added.
- The Win10 and Win11 presets only ever change plain menu entries, never add-ons. Applying one used to be a
menu-style change; with add-ons now switchable, one click would otherwise have blocked every third-party
add-on on the PC — including cloud-sync menus and antivirus scan items — which is far more than the button
says it does.
Verify the download
Get-FileHash .\SysManager-v1.102.0.exe -Algorithm SHA256
Expected SHA256: 452AEC140BEB22CDACF0563C7B425B1A66435A3810CB9BECBBACB05157CE57F4
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.102.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.102.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.