Pakua SysManager 1.130.18

[1.130.18] - 2026-10-20
CPU Core Affinity says when Windows will not show a process's cores, instead of showing the last process's, and
Display Profiles lists a monitor connected after the tab was first opened.
Fixed
- CPU Core Affinity showed the previous process's cores for a process it could not read. Picking a process whose
cores Windows does not let SysManager read, such as Defender's engine or another account's program, left the grid
ticked as it was for the process picked before, so those ticks read as this one's, and Apply stayed on for a change
Windows then refused. The grid now shows no cores, Apply is off, and the status line says why. A process that closed
after the list was read is taken off the list, as it already was after an Apply. Since CPU Core Affinity was added
(1.38.0).
- Display Profiles never saw a screen connected after the tab was first opened. The displays were read once, and
SysManager keeps running in the notification area, so a monitor or TV plugged in later, or a laptop put on its dock,
never appeared and could not be set until SysManager was closed and started again. The tab reads the displays again
when Windows reports a display change, and on a new Refresh button and F5, keeping the display you picked while it
is still connected. Nothing is read while a change waits for Keep; a change reported then is read once it is kept
or reverted. Since Display Profiles was added (1.37.0).
Verify the download
Get-FileHash .\SysManager-v1.130.18.exe -Algorithm SHA256
Expected SHA256: 08380BEC6B63EFEB0ABF628968A30ADFF528AE8DA6A52CA9E14661E22F0F0C77
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.18.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.18.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.