SysManager 1.114.42

[1.114.42] - 2026-09-29

The Standby List Cleaner, the Dark Mode Scheduler and the appearance popup no longer replace your saved
settings with the defaults when SysManager cannot read them. A change made after such a read wrote the
defaults over everything else you had saved there.

Fixed

• Standby List Cleaner, Dark Mode Scheduler and appearance: saved settings are never written over after a
  read that failed. Each reads its settings once, when SysManager starts, and saves everything on screen
  whenever one setting changes. When the read failed, the screen showed the defaults, and the first change
  wrote them over the file: the auto-purge switch and threshold, the dark and light times, or a custom
  theme.
  • After a read that failed, a change still takes effect, but nothing is saved over the file, and the next
    start reads your saved settings again. The Standby List Cleaner and the Dark Mode Scheduler say so on
    their status line.
  • A settings file that is damaged is kept as <name>.unreadable before a new one is written. If it cannot
    be moved aside, nothing is saved.
  • The Dark Mode Scheduler now switches the theme before it saves the schedule, so "Schedule applied" no
    longer covers a schedule that could not be saved.
    Present since each setting was first saved: v1.13.0 for the theme, v1.41.0 for the dark-mode schedule and
    v1.56.12 for auto-purge.

---

Verify the download

Get-FileHash .\SysManager-v1.114.42.exe -Algorithm SHA256

Expected SHA256: 268F9605AAD127BE5D37BCF2D1F2495FF4AE3FBE9AB2B10F3407B9CB96F26F2D

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.42.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.42.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.