SysManager 1.114.37: prenos za Windows

[1.114.37] - 2026-09-29
Recent Activity on the Dashboard no longer loses its history when SysManager cannot read it. A read that
failed when SysManager started could leave the next action as the only one listed.
Fixed
- Recent Activity: the history is never written over when it could not be read. When the activity file
could not be read, the next action was added to what SysManager held in memory and written over the file.
After a read that failed at startup, that was nothing, so the whole history went, including actions that
a command-line or scheduled run had recorded.
- An action logged while the file cannot be read now waits, is listed on the Dashboard meanwhile, and is
written with the next action once the file can be read.
- An activity file that is damaged is kept as activity.json.unreadable before a new one is written.
Present since Recent Activity was added in v1.17.0.
Verify the download
Get-FileHash .\SysManager-v1.114.37.exe -Algorithm SHA256
Expected SHA256: 7AECA9970A3BE370BAAB754865D9B6C58DF31344BC72944AB42184EC72A982C2
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.37.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.37.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.