SysManager 1.130.13: prenos za Windows

[1.130.13] - 2026-10-20
Scheduled Maintenance can save a schedule, and each Windows account on the PC has its own.
Fixed
- Saving a schedule never registered it. SysManager handed the task's command line to Windows under a name
PowerShell keeps for its own use, so the command line always arrived empty, Windows refused to create the task, and
Save said "Could not register the scheduled task." for every schedule. The command line arrives now, and a step that
fails stops the save, so nothing half-built is registered. Since Scheduled Maintenance was added (1.50.0).
- Two Windows accounts on one PC would have shared one schedule. The task had one name for the whole PC, so with
saving fixed each account's tab would have shown the other account's schedule as its own, an account without
administrator rights could not have saved one beside it, and Save or Remove run as administrator would have replaced
or deleted the other account's. Each account has its own task now, named with the account's security ID and run as
that account, and the tab reads, saves and removes only that one. Since Scheduled Maintenance was added (1.50.0).
Verify the download
Get-FileHash .\SysManager-v1.130.13.exe -Algorithm SHA256
Expected SHA256: B20F184637BC524F183B8F37A1D7F604062337D2D61A05C754879AD078C88C9A
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.130.13.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.130.13.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.