SysManager 1.136.117のダウンロード

[1.136.117] - 2026-11-05
Process Manager and Startup Manager call Windows 11's own Notepad, Paint, Terminal and Widgets part of Windows again, and Why is it slow? no longer calls a copy of a Windows program part of Windows.
Fixed
- Windows 11 installs Notepad, Paint, the Snipping Tool, Terminal and Widgets as Microsoft Store packages, outside
the System folder, and Process Manager and Startup Manager labelled each of them "Not recognised — named like a
Windows component, but running from …". So did Windows Media Player, which runs from Program Files, and Defender
whenever its path could be read. A program named like a part of Windows is now trusted where Windows keeps its
programs: the System folder, Microsoft's own packages, Windows' folders under Program Files and Defender's under
ProgramData. Anywhere else it is still "Not recognised". Since 1.131.11.
- Why is it slow? on the Dashboard decided whether the busiest program was part of Windows by its name alone, and
added a copy running from another folder to Windows' own processes of that name. A copy of svchost.exe in a
profile folder was called "Windows service host" and "part of Windows". It is now counted on its own, goes by its
process name, and the check says which folder it runs from. Since Why is it slow? first shipped, in 1.127.0.
Verify the download
Get-FileHash .\SysManager-v1.136.117.exe -Algorithm SHA256
Expected SHA256: 6DDFDB2C3835794FBB4E3B746F25088F45DB785BBA987017AECCAF4D6C68982D
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.117.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.117.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.