Descarcă SysManager 1.130.14 pentru Windows

[1.130.14] - 2026-10-20
Nothing one of SysManager's PowerShell steps leaves behind reaches the next one, and a step cancelled as it
starts is reported as cancelled and never starts.
Fixed
- A PowerShell step could see what an earlier one had left behind. SysManager keeps a PowerShell session open
between the steps a tab runs, so that a burst of them starts faster, and every step ran in that session's shared
scope. A setting one step changed, such as whether an error stops it, carried into the next step on the same
session, and a value a step failed to set kept whatever an earlier step had left in it. That is how Scheduled
Maintenance's save could go on with an action an earlier step had left, which 1.130.13 fixed for that tab. Each
step now runs in a scope of its own. Since PowerShell sessions began to be kept between steps (1.78.7).
- Cancelling a step as it began could show an error, or let it start anyway. A tab's first PowerShell step takes
a few hundred milliseconds to open its session, and a Cancel pressed in that time asked a step that had not started
to stop. Starting it was then refused with an error the tab's cancel handling did not expect, so an error showed
where "Cancelled" should have, or, once the stop had gone through, the step started anyway and was stopped again a
moment later, so a change you had cancelled could begin. A step cancelled before it starts now never starts, and
is reported as cancelled. The error since 1.127.3; the late start before that too.
Verify the download
Get-FileHash .\SysManager-v1.130.14.exe -Algorithm SHA256
Expected SHA256: E8E732510F5C6F5FE86A5C212D832908A74A814FCCA2A185BCC692DB720C001B
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.14.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.14.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.