Pakua SysManager 1.127.9

[1.127.9] - 2026-10-09
System Logs now shows Information or Verbose events when you tick them, instead of only after the next Refresh, and
a Refresh keeps your marks (#2601).
Changed
- System Logs: a load keeps your marks and the event you have open. A Refresh builds the list anew, and it dropped
every mark and closed the event open on the right. An event the load lists again now keeps its mark and stays open;
one it does not list, such as an event from another log, takes its mark with it. This matters more now that ticking
a severity loads the list too (below). Refresh had dropped the marks since marking arrived in 1.61.6.
Fixed
- System Logs: ticking a severity the list was loaded without now loads it. The severity switches decide what a
load asks Windows for, and then filter what it listed. Information and Verbose start off, so ticking either after a
load filtered a list that held none of them, and nothing appeared until Refresh. Ticking one now loads the list
again with it, also when it is ticked while a load is still running. Unticking one still filters straight away. The
switches had worked this way since System Logs arrived in 0.3.0.
Verify the download
Get-FileHash .\SysManager-v1.127.9.exe -Algorithm SHA256
Expected SHA256: CB502594C35213E5637A2559539B61308C91CAAEFBD8329CDEF6810167396811
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.9.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.9.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.