Lataa SysManager 1.114.14

[1.114.14] - 2026-09-28
Ending a program in Process Manager now ends that program only. It also ended every program the chosen one
had started. After SysManager's own "Run as administrator" restart, that meant ending Explorer closed every
open program.
Fixed
- Process Manager: Kill ends the process you chose, and nothing else. It ended the whole process tree: the
program, every program it had started, and theirs in turn, behind a confirmation that named one program.
- Every program opened from the taskbar or the Start menu is started by Explorer. So after SysManager's own
administrator restart, ending explorer.exe closed all of them, with anything unsaved.
- When SysManager itself had been started from Explorer, it was inside that tree, and .NET refuses to end a
tree that contains the program asking. Nothing was ended, and the tab blamed administrator rights.
It now ends the one process, as Task Manager's End task and File Lock Detector already did. Present since the
tab was added in v0.9.0.
- Process Manager: "Could not kill" now means the process is still running. The same message covered a
process that had already closed, and a tree kill that ended the program but not one of its children. A
process that has closed now loses its row and says so.
- The kill also checks when the process started. If the program closed while the confirmation was open and
Windows gave its ID to another program, that program is left alone.
- SysManager's own row is refused before the confirmation, because ending it would stop SysManager
mid-step. It used to be refused only by accident.
- Process Manager: the once-a-second refresh no longer rewrites the status line. It wrote "Refreshing process
list…" and then "Loaded N processes." every second.
- Any result, including "cannot be ended" for a system-critical process, was replaced within a second.
- A screen reader was given two announcements a second.
- The progress bar and the tab's busy mark in the sidebar flashed on every refresh.
The background refresh is now silent, and the Refresh button still reports what it loaded. Present since the
automatic refresh was added in v1.10.2.
Verify the download
Get-FileHash .\SysManager-v1.114.14.exe -Algorithm SHA256
Expected SHA256: B26EE961998916C2A1DE1BE58550C9EB3AA4FD578FF5B9669235B62AF3972141
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.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.114.14.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.