SysManager 1.130.51: prenos za Windows

[1.130.51] - 2026-10-21
Windows Features says why Windows refused a change, shows each feature the way Windows reports it afterwards, and
Escape or Cancel no longer stop a change half-way.
Fixed
- Every failed change said "Check permissions". The tab offers a change only when SysManager runs as
administrator, and the script threw DISM's own reason away. A failure now gives Windows' reason and its error code,
and plain words for four codes with a known way out: files the feature needs that Windows could not download
(0x800F0906) or find (0x800F081F), a policy that forbids downloading them (0x800F0907), and a service it needs that
is turned off (0x80070422). Since 0.46.0.
- After a change, the row showed what was asked for rather than what happened. It flipped the row when Windows
said yes and left it alone when Windows said no, so a change that failed part-way, or one waiting for a restart,
showed the wrong state. The tab now reads the feature back from Windows after every change. A feature waiting for a
restart to turn on read as off, in a scan too; it now shows the state it will have, with "Reboot required", and the
reboot notice appears. Since 0.46.0.
- A switch could show the opposite of the feature's state. Declining the confirmation, or a change that could not
start or failed, left the switch turned over while the State column said otherwise, and the next click asked the
wrong question: turning the switch back off asked whether to enable the feature. The switch now turns back. Since
1.9.0.
- Escape and Cancel stopped a change half-way. Both ended PowerShell and DISM while Windows was applying the
change, and nothing checked what was left. They now stop only a scan, and the Cancel button shows only while one
runs. Since 0.46.0 for Cancel and 1.76.0 for Escape.
- Four safety hints were wrong. "Remote Differential Compression API Support" was described as a Remote Desktop
client, Windows Media Player Legacy as a codec pack, and Media Features as Windows Media Player itself. Windows
Sandbox's rating was filed under a name that is not Sandbox's, so its row showed as not rated. Since 1.10.0.
Verify the download
Get-FileHash .\SysManager-v1.130.51.exe -Algorithm SHA256
Expected SHA256: 48525DFB96E9715E5E5E584C2429EBB1D86C6920858D0BBB1D4BF4B2595FF862
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.51.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.51.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.