SysManager 1.127.14

[1.127.14] - 2026-10-09

After a list refreshes, keyboard focus goes back to the row you were on, instead of jumping to the top of the
window (#2609).

Fixed

• Keyboard focus comes back to the same row after a list is rebuilt. A list that refreshes replaces every row at
  once, and the focused button or cell went with its old row. Focus then fell back to the window, so someone using
  the keyboard or a screen reader had to Tab back in from the sidebar after F5 on Services, after putting a change
  back on Undo Changes, and whenever another list reloaded. Focus now returns to the same control in the same row
  when that row is still there, to the row now in its place when it is not, and to the list, or the control after
  it, when no row is left. It does so only when the keyboard was the last thing used and focus had not been moved
  somewhere else, so a list that refreshes on a timer never scrolls back under the mouse. Every table has it, and
  so do the 21 other lists rebuilt this way whose rows can take focus. Lists have lost focus this way since they
  were first refreshed in place.
• A test now fails when a list that is rebuilt this way, and whose rows can take focus, does not keep it.

---

Verify the download

Get-FileHash .\SysManager-v1.127.14.exe -Algorithm SHA256

Expected SHA256: 017AF56087BBB258B8D6CD3E656658255A9D3096581CA58CAEF371F0B85083FA

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.127.14.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.127.14.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.