Baixar SysManager 1.113.1 per a Windows

[1.113.1] - 2026-09-23
If you keep two Firefox profiles, Browser Cleaner showed you two identical rows. Both were called
plainly "Firefox" with the same description, so there was no way to tell which profile you were about to
clean — and because the tab remembers your ticks by the row's name, a tick you put on one profile was
applied to the other after a rescan. Firefox profiles are now named individually, the way Chrome and Edge
profiles already were.
Fixed
- Each Firefox profile is its own named row. Firefox stores profiles in folders with a random prefix
(8f3k2p9q.dev-edition), so the rows use the readable half: your everyday profile stays simply "Firefox"
and a second one reads "Firefox — dev-edition", with the profile named in the description too ("Cookies in
dev-edition — clearing these signs you out of websites"). If two profiles happen to share that readable
half, both keep their full folder name so they still read apart.
- A tick can no longer drift to the wrong profile. The tab remembers your selection across a rescan by
the row's browser and category, so two rows that were both called "Firefox / Cookies" were the same row as
far as that memory was concerned: unticking cookies on one profile silently unticked them on the other.
Distinct names make every row's identity unique, which is what that memory needs to be correct.
- Cleaning one Firefox profile leaves the others alone, and is now covered by a test that says so — the
same guarantee that already held between Chrome profiles and between Opera channels.
- A profile is named once, not once per folder. Firefox splits a single profile across two locations
(its cache under Local AppData, its cookies and sessions under Roaming), so the profiles are collected
from both before any naming happens. Otherwise the same profile could have appeared under two different
names depending on which category a row came from.
Verify the download
Get-FileHash .\SysManager-v1.113.1.exe -Algorithm SHA256
Expected SHA256: F7A105138BA502D345036574F1ABF2ED542C10C6623229B98C483D440DA0D9D3
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.1.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.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.