Pakua SysManager 1.136.93

[1.136.93] - 2026-11-02
A maximized window comes back maximized from the notification area, and an unrecognized close setting asks again.
Fixed
- Bringing SysManager back from the notification area, from the tray icon, its menu or by starting it a second time,
set the window to its normal size every time, so a maximized window came back un-maximized, and a click on the
tray icon un-maximized a window that was already open. Now only a minimized window is restored, to the size it had
before, and any other comes back as it was left. This was there since the tray came in 0.38.0.
- A close setting saved as a number or a list, such as "3", made the X button do nothing, with no message, until the
setting's file was deleted. It is now read as not chosen, so closing asks again. This was there since the setting
came in 1.56.9.
Verify the download
Get-FileHash .\SysManager-v1.136.93.exe -Algorithm SHA256
Expected SHA256: E02DF73ECAEBD3D7FDE24A45C50EEE0146B6436397F740331D4B54DFB18EB1F8
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.93.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.93.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.