SysManager 1.127.3下載

[1.127.3] - 2026-10-09
Cancelling a tab's PowerShell work no longer freezes SysManager when the PowerShell behind it has died, and a
PowerShell that stopped working is reported by the tab that was using it (#2608).
Fixed
- Pressing Cancel while a script runs returns at once. Cancelling waited for PowerShell to confirm the stop, on the
thread that draws the window. When the powershell.exe running the script had ended, closed from Task Manager for
example, that confirmation took about a minute to fail, and SysManager stopped responding for all of it. The stop
is now asked for in the background, and nothing it throws can come out of Cancel. Cancel has waited for the stop
since the first release; it could take that long whenever the script ran in a separate powershell.exe, which
every session has done since 1.114.4.
- A PowerShell session that stopped working is reported by the tab, not by the error window. PowerShell raises
two kinds of error for a session that can no longer run anything, and neither was one the tabs' own handling
catches, so on Preinstalled Apps, Defender Tweaks, Edge/OneDrive Remover, Scheduled Maintenance, Restore Points,
System Fixes and Task Scheduler it reached the app-wide error handler. Both now arrive as the failure each of those
tabs already reports for a script that failed.
- The next script after a powershell.exe that ended starts a fresh one straight away. SysManager keeps one
powershell.exe for a short burst of scripts. If it had ended in between, the next script still went to it, waited
about a minute and failed. It is now replaced before the script starts, without waiting for the old one to be
cleaned up. It had been reused that way since SysManager first kept it, in 1.78.7.
Verify the download
Get-FileHash .\SysManager-v1.127.3.exe -Algorithm SHA256
Expected SHA256: 3B725A627A329F3C6745E6812F866A2249200CA8BC4041AB218376D04EA2E538
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.127.3.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.127.3.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.