Preuzmi SysManager 1.136.135 za Windows

[1.136.135] - 2026-11-06
Tab goes through five rows in the order they are drawn, where it went backwards or skipped ahead.
Fixed
- On five rows Tab ran against the screen, because a control was docked right or at the bottom ahead of one drawn
before it. On DNS & Hosts Tab went Reset to DHCP, Apply, Undo and then the preset picker, the reverse of the row, so
someone entering the card from the keyboard landed first on the button that changes the PC's DNS (since 1.6.0).
Bulk Installer reached Search before its search box (since 1.7.5), Boot Analyzer Refresh before the Cancel to its
left (since 1.58.2), Environment Variables the PATH editor's add row before the folders above it (since 1.22.0), and
Speed Test Run before the Ookla server picker. Each row declares its controls in the order they are drawn now, laid
out exactly as before: every control, text and list on the five tabs sits where it did, measured at two window
widths. A check fails the build when a row is docked that way again.
Verify the download
Get-FileHash .\SysManager-v1.136.135.exe -Algorithm SHA256
Expected SHA256: D46876598EB2976C4139A5DBB481B99822ACFEEBA5019AFFCFB08F32A550BF3A
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.135.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.135.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.