Λήψη SysManager 1.122.0

[1.122.0] - 2026-10-06
Browser Cleaner now shows the extensions each browser has, what they can do, and which ones another program put
there. "Since last week my searches go to some other site" is usually an extension, and until now SysManager could
clear the cache but not show it. Nothing in a browser is changed: "Manage in …" opens the browser's own page.
Added
- Extensions in Browser Cleaner (#1526). A second view in the tab, switched with the same pills as Privacy &
Telemetry's "Show". "Look for extensions" lists every extension in every browser and profile the tab already
cleans — Chrome, Edge, Brave, Vivaldi, every Opera channel and Firefox — one group per profile.
- Each extension shows its own icon, name and version, when it was installed and where it came from (a store, a
file, the browser itself, or a folder on the PC), and in plain words what it can do: "Changes your search
engine", "Replaces your new tab page", "Can read and change everything on every website", "Can see your open
tabs". Those that change what you see, reach every website or can control the browser are amber. A permission
the list does not know is shown by its own name rather than left out.
- Marks say which ones another program put there, which ones your organisation manages (only it can remove
those), and which ones are turned off. Those added by another program come first, then those that can read every
website.
- The toolbar counts them: "12 extensions in 3 browsers · 1 was put there by another program". A profile whose list
could not be read says so and asks you to close that browser and look again, instead of showing as empty.
- Nothing is left out for being hard to read. An extension whose files cannot be read, or sit behind a link, is
listed as "An extension whose name could not be read" with what the browser recorded about it, and a profile kept
behind a link (a common way to move it to another drive) is shown as one that could not be read, and says why. A
link where a profile, an extension or one of its folders should be is never followed, and a browser's files cannot
send SysManager to a network share outside the profile it is reading. One odd value in those files costs only
itself, and a file that is not JSON at all costs only that file — never the list.
- Read-only. "Manage in …" opens the browser on its own extensions page, where it asks you itself, and puts the
page's address on the clipboard in case the browser opens somewhere else. While SysManager runs as administrator
it opens no browser — one opened from it would run as administrator too — and says to open the browser and paste
the address yourself. Each profile is opened as itself, and where a browser has more than one, the status says
which profile to open.
- Searching the sidebar for "extensions", "add-ons", "search changed" or "browser ads" opens Browser Cleaner on this
view, and F5 refreshes whichever view is shown.
Verify the download
Get-FileHash .\SysManager-v1.122.0.exe -Algorithm SHA256
Expected SHA256: D75C644BF52E26BA7F443EF5F08F286B1BC14B5B928263421D3F1081FBA6430C
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.122.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.122.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.