SysManager 1.114.34: prenos za Windows

[1.114.34] - 2026-09-29
Volume Control no longer replaces your saved presets when it cannot read them, and says when a preset was
not saved. One failed read could leave only the preset just saved, and deleting one could remove them all.
Fixed
- Volume Control: saved presets are never written over when they could not be read. A presets file that
could not be read was taken as empty. Saving a preset then left it as the only one, and deleting a preset
left none.
- Save and Delete now change nothing when the presets cannot be read, and say so.
- A presets file that is damaged is kept as volume-presets.json.unreadable before a new one is written.
- Volume Control: a preset that could not be written no longer reads as saved. The tab said "Saved
preset" and showed it in the list even when writing the file failed, and it was gone at the next start. It
now says the preset was not saved, and the same for Delete.
Both present since presets were added in v1.55.0.
Verify the download
Get-FileHash .\SysManager-v1.114.34.exe -Algorithm SHA256
Expected SHA256: 43E0BB57FC2E73282CB07250899799B9654B9DE909789B4C5CB0924BA03891A9
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.34.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.34.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.