SysManager 1.101.0

[1.101.0] - 2026-09-14

Turning off a service now tells you what else will stop. The prompt used to say "this may affect
system functionality", which is true of every service on the machine and so tells you nothing you can
decide against. When other services need the one you are switching off, they are now named in the
confirmation by the names you would recognise — so the question becomes "my printer will stop working,
do I want that?". The names also appear on the safety badge's tooltip, which you can read without
administrator rights.

Added

• Stop and Disable confirmations name the services that depend on the one being turned off. Each one is
  worded for what that action actually does: stopping a service stops its dependents now, while disabling
  it means they will not be able to start — the same sentence for both would have been wrong about one.
• The safety badge's tooltip lists them too. The confirmation sits behind an administrator check, so
  without this the information would have been invisible to anyone not running elevated.
• A long list is capped at five names plus a count of the rest. A service with 25 dependents exists on an
  ordinary install, and an unbounded list pushes a confirmation dialog's own buttons off screen.

Changed

• Loading the Services tab reads each service's dependents, measured at 17 ms on top of a 167 ms scan
  (10%). Read for every row rather than on selection because that cost does not justify the complexity.
  The opposite direction — what a service itself needs in order to run — is deliberately not read: six
  times the cost, for a question that would not change the decision.

---

Verify the download

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

Expected SHA256: E072054BDE2B1A7366EAA1436DF1AF25BC607E35C4A61B4A900309D958EF13A2

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