SysManager 1.84.0下載

[1.84.0] - 2026-09-09
Scheduled maintenance now actually runs on a laptop that is not plugged in. Windows refuses to start a
scheduled task on battery unless it is told otherwise, and SysManager had never told it — so on any laptop
used unplugged, the Scheduled Maintenance tab showed a confident "Next run" time and then quietly did
nothing, sometimes for weeks. The tab now also lets you ask for the opposite, waiting until you are away
from the PC, tells you in words what the settings you picked will do, and shows Windows' own count of runs
that never happened.
Fixed
- Maintenance on battery. The scheduled task is now created with permission to start on battery, and to
keep running if you unplug mid-way. This is the whole bug: the tab promised "no need to remember it
yourself" while the run it promised was being skipped, and Windows reports a skipped run as nothing at
all — no error, no result code, just a Last run that never moves.
Added
- "Only run when I'm not using the PC". Off by default, deliberately: waiting for an idle machine
brings back the same "never ran" problem on a PC that is always in use, so it is a choice you make rather
than a default you have to discover.
- A plain sentence describing the schedule you are about to save, conditions included — "Every day at
03:00, only while plugged in" — updated as you change the settings, so the consequence of a tick is
visible before you commit to it.
- A warning when Windows has skipped runs. It shows the count Windows recorded and the likely reasons
(the PC was off, asleep, or blocked by one of the conditions). This is the only signal Windows gives for
a run that was skipped, and it stays hidden when there is nothing to report rather than announcing a
reassuring zero.
- A one-hour cap on a maintenance run, so a wedged background run cannot sit in the scheduler forever.
Verify the download
Get-FileHash .\SysManager-v1.84.0.exe -Algorithm SHA256
Expected SHA256: 23FC05C95915E820E6C030C7E1305CFF2259C7BBE5A282A5E42BBC1FA92C59C3
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.84.0.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.84.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.