Shkarko SysManager 1.136.79

[1.136.79] - 2026-11-02
On Dark Mode Scheduler, a switch you make holds until the schedule's next change, and a time it cannot read is refused instead of quietly replaced.
Fixed
- With the schedule on, Dark or Light on Dark Mode Scheduler was undone within a minute: the schedule's check compared
the theme it wanted with the one SysManager had last set, so it switched straight back, while the same change made
in Windows Settings held. A switch made here now holds until the schedule's next change, and the status line says
when the schedule takes over. Changing the schedule ends it. This was there since the tab was added in 1.41.0.
- The schedule's two time boxes took any text and saved it as typed, and the schedule read what it could not, "1900",
"19h" or "19;00", as 19:00 or 07:00 without a word, while the box went on showing the text. A time it cannot read is
refused now: the box goes back to the time the schedule runs on, the status line says how to write one, and nothing
is saved. A time it reads is saved the way it reads it, "7:30" as "07:30". This was there since 1.41.0 too.
Verify the download
Get-FileHash .\SysManager-v1.136.79.exe -Algorithm SHA256
Expected SHA256: 93A109CEB7DCCD7AC6435766569B01BD7880EF30BC1EEE85B61CB3BEAC59A08C
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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.136.79.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.136.79.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.