Pakua SysManager 1.136.156

[1.136.156] - 2026-11-09
A page too tall for the window scrolls instead of cutting off its bottom, and its lists, consoles and charts keep
the height they need.
Fixed
- Every page was fixed rows over one stretching row, a list, a console or a chart, that took what the page had
left, with no scrolling, so once the fixed rows filled the page that row got nothing and whatever was under it was
cut off with no way to reach it. At the default window System Fixes' console had no room at all and 186 px of the
page were past its bottom, Scheduled Maintenance ran past its bottom too and Windows Update's list had 5 px, and at
the smallest window seven pages ran past their bottom and fifteen left a list, a console or a chart under 160 px.
Each stretching row now has a floor, 160 px or what its content needs, such as Ping's chart card, and a page the
window is too short for keeps that height and scrolls as a whole. A page that fits fills the window as before, and
its lists keep their own scrolling.
- Because nothing is cut any more, eight pages that hold more than the default window shows scroll at that size:
System Fixes, Scheduled Maintenance and Windows Update, which ran off the page before, and Quick Cleanup, Resource
History, Bandwidth Monitor, Ping and Settings Watchdog, whose console, chart or empty list was cut short.
- App Updates' console was 7 px too short for its "No output yet", and is now as tall as that needs.
- Tests pin the floor and the height a page asks for, the shell filling, scrolling and bringing a control into view,
every page that stretches a row being one that does this, and every page laid out at both windows cutting nothing.
Verify the download
Get-FileHash .\SysManager-v1.136.156.exe -Algorithm SHA256
Expected SHA256: 64B9696FCC99EC3BA06A8E5740A9649F5246CEF2D2531463C05D2539159E6FF8
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.156.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.156.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.