Last ned SysManager 1.114.18

[1.114.18] - 2026-09-28
File Lock Detector now checks folders, and says when a path does not exist or a check could not be completed.
All three used to read "No process is currently using that path."
Fixed
- File Lock Detector: a folder is checked through the files inside it. The tab asks Windows' Restart Manager,
which tracks files and refuses a folder outright, even for an administrator. So every folder was reported as
unused, including one with a file held open inside it, though the tab invites you to enter a folder.
- The tab now checks the files in the folder and its subfolders, up to 1,000, and lists every process holding
any of them.
- When a folder holds more, the result says that only the first 1,000 were checked.
- A folder with no file to check says so, rather than that nothing is using it.
- Links and junctions inside the folder are not followed out of it.
- A path that does not exist says so. A mistyped path got the same answer as a file nothing was using. It now
reads "No file or folder exists at that path."
- A check that could not be completed says so. Any Restart Manager failure also read as "no process". It now
says the check could not be completed and to try again.
Present since the tab was added in v1.36.0.
Verify the download
Get-FileHash .\SysManager-v1.114.18.exe -Algorithm SHA256
Expected SHA256: 005FA0370C62CE1B6F535D816039342FAAF69788DD0A53AB0979DCB8C32F61FB
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.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.114.18.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.