Sækja SysManager 1.109.3

[1.109.3] - 2026-09-17
A tab that failed to load could say nothing at all. Every tab starts loading in the background the
moment you open it, and that background work was wrapped in a net that only caught six kinds of failure.
Anything else vanished: no message, no log line, no crash — the tab simply sat there half-filled, and there
was no way to tell it apart from a tab that had nothing to show. One of those invisible failures had been
happening on Preinstalled Apps at every launch. The net now catches everything and records it.
Fixed
- A view model's background load no longer loses an unexpected failure. The boundary that wraps every
tab's start-up work caught six exception types and let the rest through, where they were not merely
unlogged but unobservable: nothing awaits that work, so the failure stayed on a task that is kept alive by
the tab itself and therefore never reaches the process-wide unobserved-task handler, which only runs when
such a task is finalised. It is now logged at Fatal with the tab's name and the failure's type, and
recorded on the view model so a test — or, later, the tab itself — can see it.
- A NullReferenceException thrown on every launch by Preinstalled Apps' package parser was one of
those. It was found only because an unrelated test was changed to wait for the load, which is exactly the
shape of the problem: the sole way to notice was to wait for something the application never waits for.
Changed
- A failure nobody predicted is rethrown when a debugger is attached, so it is loud while someone is
working on the code and quiet in a released build. Gated on the debugger rather than on a debug build,
because every build this project produces is Release — a #if DEBUG branch here would compile into
nothing that ever runs and could not be tested.
Verify the download
Get-FileHash .\SysManager-v1.109.3.exe -Algorithm SHA256
Expected SHA256: EE951E767E26C35BBA83B53012EFF00A0575927A4B5DCBFACFE4BB8FF0A744E7
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.109.3.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.109.3.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.