Baixar SysManager 1.114.52 per a Windows

[1.114.52] - 2026-09-30
File Lock Detector and CPU Core Affinity now act only on the process you picked. If it has closed and
Windows has given its process ID to another program, End process, Apply and Restore leave that program alone
and say the process had already closed.
Fixed
- File Lock Detector's End process ended whichever program had the listed process ID when you confirmed.
The list can be minutes old, and Windows gives a closed process's ID to the next one started, so a locker
that had closed could have been replaced, and the replacement was ended behind a prompt that warned about
the locker's unsaved work. End process now passes the start time Restart Manager reported with the ID, and
ends the process through the same call Process Manager uses (#2498), which leaves a process that started at
another time alone. The tab then says "X had already closed, so nothing was ended." and checks the file
again. Present since v1.36.0, when File Lock Detector was added.
- CPU Core Affinity's Apply and Restore changed whichever program had the listed process ID. Each process
in the list now carries its start time, and reading or changing its affinity checks it. A change aimed at a
process that has closed leaves the new owner of its ID alone, says "X had already closed, so nothing was
changed.", and refreshes the list, and a refresh no longer keeps the selection on a new process with the old
one's ID. The original affinity Restore puts back is remembered per process, start time included, so a
restarted program that gets the same name and ID is restored to its own. Present since v1.38.0, when CPU
Core Affinity was added. Gaming Profile picks its game from the same list and is tracked in #2559.
Changed
- File Lock Detector keeps the outcome of End process on the status line. "Ended X." now stays in front
of the result of the check that follows it, which used to replace "Ended X. Re-scanning…" the moment it
began. A refusal reads "Couldn't end X — it may need administrator rights.", without the old "or it already
exited", which is its own outcome now.
Verify the download
Get-FileHash .\SysManager-v1.114.52.exe -Algorithm SHA256
Expected SHA256: C6EBE669816BE7E790DF3E7BD75BCAFC92DA49B992DEA7AA20E9C1E6315189A9
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.114.52.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.114.52.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.