ดาวน์โหลด SysManager 1.136.41

[1.136.41] - 2026-10-31
Ending a process, or changing one in CPU Core Affinity or Gaming Profile, no longer reaches
another program that was given its ID, and a new program at a reused ID gets its details.
Fixed
- Process Manager ended a process whose start time Windows would not give by its ID alone. Without
administrator rights that is most of the system's and other users' processes. If such a process
closed while the confirmation was open and Windows gave its ID to another program, Yes ended that
program, and the status line named the first one. A row is now ended only while it is still the
same process, by its start time and its name. File Lock Detector ends a locker through the same
check, and CPU Core Affinity and Gaming Profile change and watch a process the same way. The
start-time checks these tabs gained from 1.114.14 to 1.114.53 each left such a process out.
- A program that started at the ID of one that had just closed stayed bare in Process Manager for
as long as it ran: no icon, no description, no category or safety, no signature and no way to
open its file location. A Windows component in that position got the ordinary kill prompt rather
than its own warning. It now gets its details like any new program. This was there since
1.20.63.
Verify the download
Get-FileHash .\SysManager-v1.136.41.exe -Algorithm SHA256
Expected SHA256: 77F731AF9C80462EAF80AE4B2C27A73C8E1B7DB37E5C294A7A285E140A8BF5AA
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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.136.41.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.136.41.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.