Shkarko SysManager 1.114.38

[1.114.38] - 2026-09-29
Resource History no longer deletes older samples when SysManager cannot read how many days to keep. A
setting that could not be read counted as 7 days, so a 14- or 30-day history lost everything past the first
week.
Fixed
- Resource History: a retention setting that cannot be read no longer shortens the history. The number of
days to keep was taken as 7 whenever its file could not be read or did not hold one of the offered choices,
and the prune that runs when SysManager starts then deleted every sample older than a week.
- While the setting cannot be read, a prune keeps what the longest choice, 30 days, would keep.
- Choosing a retention on the tab replaces the unreadable setting, and that choice is the one used,
including 7 days, which is what the tab shows meanwhile. The file holds only that one number, so it is
replaced rather than kept aside.
Present since Resource History was added in v1.47.0.
Verify the download
Get-FileHash .\SysManager-v1.114.38.exe -Algorithm SHA256
Expected SHA256: 938301BC3DA7A0E2C68D1328FBC7B27B928A6C5288A869451A079DC9259E5001
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.114.38.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.114.38.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.