Lataa SysManager 1.74.0

[1.74.0] - 2026-08-25
The CPU Core Affinity process list is now filterable, and shows which processes are already pinned.
Finding one game in a dropdown of 300 svchost entries was a dead end; now there's a name/ID filter
like the other list tabs, and a process running on a subset of cores says so right in the list.
Added
- A filter box on the CPU Core Affinity process picker. Type part of a name or the process ID to
narrow the list — the same affordance the Services, Task Scheduler and Windows Features tabs already
have. The selection is kept across a Refresh, even if the process's affinity changed in between.
- A "pinned" marker in the list. A process running on a subset of cores shows it — e.g.
"chrome (1234) — 4 of 16 cores" — so you can see what you've already tuned instead of selecting each
one to infer it from the core checkboxes. The tab already read this and discarded it. The wording is
neutral (it reports the state, it doesn't claim SysManager set it), and a process on all cores or one
whose mask can't be read shows no marker.
Verify the download
Get-FileHash .\SysManager-v1.74.0.exe -Algorithm SHA256
Expected SHA256: 904478641F41EDEBDC9A717DCD16734BDA591DEDAD4A6A0648E666EF0BC255ED
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.74.0.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.74.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.