Sækja SysManager 1.111.1

[1.111.1] - 2026-09-18
Thirty buttons were too small to hit reliably, and one of them deletes something. Buttons that sit inside
a table row or a toolbar trim themselves to fit, and nothing stopped them getting too small. Every button in
the app that sets its own padding was rendered and measured: 30 came out under the accessible minimum, across
16 screens, and the worst was the X that removes an entry from your hosts file at 20 by 19 pixels. Every
button is now at least 28 by 28 however short its label, so a cramped label makes a button narrow to look at
rather than narrow to click.
Fixed
- Every button has a minimum clickable size of 28 by 28 pixels. 110 buttons set their own padding to fit a
compact row; measured with their real style, padding, font size and label, 30 fell under the 24 by 24 that
WCAG 2.5.8 asks for — 26 of them on height, 4 on both height and width. That matters most for anyone whose
pointing is not precise, and the smallest of the thirty was one of the few that removes something.
- 28 rather than the 24 WCAG 2.5.8 asks for. A floor set exactly at the threshold leaves nothing for a
fractional display scale, and 28 by 28 is already the size of the small round buttons at the bottom of the
sidebar, so this makes the rest consistent with a decision the app had already taken.
- The sidebar search box makes room for its clear button. That button asked to be 20 by 20 and the new
floor overrules it, so without widening the space reserved for it, it would have sat on top of what you
typed.
Changed
- Rows and toolbars holding those buttons are slightly taller. That is the cost of the larger targets, and
it is the intended trade — the buttons that grew are the ones that were too small to aim at.
Verify the download
Get-FileHash .\SysManager-v1.111.1.exe -Algorithm SHA256
Expected SHA256: F776D633A9192B88449E33930F6FC9BB2DB0D5E4CEE4860051E73B11558E7119
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.111.1.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.111.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.