SysManager 1.136.32: prenos za Windows

[1.136.32] - 2026-10-31
Ping's Gateway card follows the network you are on, so a laptop that wakes up on another Wi-Fi
pings the router there.
Fixed
- The Gateway card was the router found when SysManager started, and it was never looked up again.
SysManager stays in the notification area for days, so after the PC woke up on another network,
Start pinged the old router's address: every ping timed out, and the verdict read "Problem on your
local network" while your router was fine. If SysManager started before Wi-Fi connected, there
was no Gateway card until it restarted. The router is now looked up again each time you press
Start and whenever the PC's connection changes: the card moves to the new router, appears when
one is found, and goes when there is none. A card you turned off stays off. This was there from
the first version.
Verify the download
Get-FileHash .\SysManager-v1.136.32.exe -Algorithm SHA256
Expected SHA256: BCFB0B4338B7FB3D511B076A57720D1C10CFB07FB5D367EB1E0B67D2F948E2DF
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.32.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.32.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.