Sækja SysManager 1.130.35

[1.130.35] - 2026-10-21
The Edge/OneDrive Remover says whether OneDrive is really installed, reaches Edge's update tasks, and leaves things
as they were when a change fails.
Fixed
- The OneDrive card said "OneDrive is installed." right after a removal that worked. It looked for OneDrive's
setup, which Windows keeps after an uninstall so OneDrive can be put back, so on a standard Windows the card never
said "not installed" and Remove stayed on offer. It now looks for OneDrive itself, installed for your account or
for every account, and reads "Checking OneDrive…" until it has looked, where it said "not installed". When
OneDrive is installed but nothing to uninstall it with is found, Remove now says it could not remove it, not that
OneDrive is not installed. Since 1.53.0.
- Disabling Edge never reached its automatic-update tasks, and said it had. Edge Update adds an ID to the name of
each of its two tasks, and the tab asked Windows for the names without one, so it found no task, changed none and
reported success; Restore did the same. The tasks are now found by the start of their names, and a change that
finds none or cannot change one is reported as failed, with any task it had changed put back. Since 1.53.0.
- A failed Disable Edge left Edge's background mode and startup boost switched off. The two policies are written
first, and when the update tasks then failed, the change was reported as failed with both left in place. They now
go back to what they were before, a value set by whoever manages the PC included. Since 1.56.2.
- A failed Remove OneDrive took OneDrive out of File Explorer's sidebar anyway. The entry was hidden whatever the
uninstaller answered, so a removal that failed left an installed OneDrive missing from the sidebar. It now goes
only with a removal that worked. The removal closes OneDrive first, and when it fails it now says so and that
OneDrive can be opened again from the Start menu. Since 1.53.0.
Verify the download
Get-FileHash .\SysManager-v1.130.35.exe -Algorithm SHA256
Expected SHA256: 60C5F8698F7EFC4B2B1EEF6F544C38A06938AC867EB34FEBCEA596C759069DB5
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.130.35.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.130.35.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.