[1.112.2] - 2026-09-21
Context Menu Manager was quietly filling a folder you were never told about. Before each change it saves a
copy of the affected registry key, which is sensible — but it kept every copy forever, nothing in the app ever
read them, and nothing mentioned they existed. It now keeps the three most recent per entry and says so on the
tab.
Fixed
- Only the three most recent registry copies per entry are kept. One file was written per toggle and never
removed, so the folder grew for the life of the install. Three matches what the diagnostics bundle already
keeps for log files, rather than being a second number to remember.
- Pruning one entry can no longer delete another's copies. A shorter entry name can be the start of a
longer one, and both produce files that begin the same way — so cleaning up after one could have swept away
the history of the other. The file names are matched on their exact date-and-time shape instead.
- The tab now says the copies exist, and where. They are not needed to undo anything — the on/off switch
does that, and always did — but a file you can restore by hand is only useful if you know it is there.
Verify the download
Get-FileHash .\SysManager-v1.112.2.exe -Algorithm SHA256
Expected SHA256: 845C00C8F55C24B1B5C406612063761613C67CA5D1649572BF034BD4D9918151
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.112.2.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.112.2.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.
