Sækja SysManager 1.66.1

[1.66.1] - 2026-08-24
Two tabs list the same scheduled tasks, and now each one says so. Startup Manager deliberately leaves out
Windows' own tasks to keep its list short and safe to touch, which is the right call — but it never told
you, so a task you could not find looked like a task that was not there.
Fixed
- Startup Manager and Task Scheduler now explain how they overlap. Startup Manager says that it lists
scheduled tasks belonging to programs you installed and that Windows' own are left out, and points at
Task Scheduler for the complete list. Task Scheduler says the reverse: a third-party task also appears
in Startup Manager, it is the same task in both places, and switching it in one tab shows up in the
other once that tab refreshes. Neither claims the two lists stay in step live, because they do not.
- Corrected a documented claim that was never true. The README said Startup Manager lists
"logon-triggered scheduled tasks". The scan only requires that a task have some trigger — it never reads
which kind — so a task that runs daily or when the machine goes idle was always listed too. The README
now describes what the scan really does, and a test pins the wording to the code so the claim cannot
drift back: it becomes allowed only if the scan is one day taught to read the trigger type.
Verify the download
Get-FileHash .\SysManager-v1.66.1.exe -Algorithm SHA256
Expected SHA256: 8BED975C8ABA2FC16C59AC9E95210DAC033AC9AABA09B46187900C0EE4202842
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.66.1.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.66.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.