Lataa SysManager 1.101.5

[1.101.5] - 2026-09-14
App Updates and Profile Export stop putting back the ticks you removed. Both listed everything already
ticked, so unticking was how you said "not this one" — and refreshing put every tick back. In App Updates
that meant the next Upgrade installed a package you had excluded; in Profile Export it meant a section you
had left out went into the file anyway. This completes the sweep started two releases ago: every list in the
app that can act on a tick now keeps yours.
Fixed
- Unticking a package in App Updates survives a rescan, including when the rescan finds a newer version on
offer — "don't upgrade this one" does not stop being true because the version changed.
- Unticking a section in Profile Export survives a refresh, so an excluded section cannot reappear in the
exported file or in what an import applies.
- In both, unticking everything survives too, rather than being read as "nothing chosen yet" and reset.
- A package or section that appears only after the refresh is ticked as normal, since there was no earlier
choice about it to keep.
Verify the download
Get-FileHash .\SysManager-v1.101.5.exe -Algorithm SHA256
Expected SHA256: 33BBF5772BD2FE28DBD78D9EACC4ACD29AF2CBD7F95EF61780242CBC149C3EDC
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.101.5.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.101.5.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.