Hili ni toleo la zamani. Toleo la sasa ni 1.136.161. SysManager 1.136.161 · Lilitolewa:
Faili za kisakinishi 1.136.53
| Usanifu | Aina | Upeo | Ukubwa wa faili | Pakua | SHA256 |
|---|---|---|---|---|---|
| 64-bit | Portable | — | — | github.com | VirusTotal |
Kiungo na SHA256 vinatoka kwenye manifest ya jumuiya ya Windows Package Manager. Linganisha hashi ya faili uliyopakua kabla ya kuiendesha.
Maelezo ya toleo
[1.136.53] - 2026-10-31
Refresh and F5 ask before they throw away changes you have not applied yet.
Fixed
- Privacy & Telemetry, Notification Blocker, Environment Variables and the hosts file on DNS &
Hosts keep your changes until you press Apply or Save. Refresh read everything again and
dropped those changes without a word, and F5 runs Refresh, even with the cursor in a box.
Choices staged from an imported profile could not come back afterwards without importing the
profile again. Refresh now asks first when there is a change not made yet, and No keeps every
change as it was. This was there since each list could be refreshed with changes waiting:
1.6.0 for the hosts file, 1.18.2 for Privacy & Telemetry, 1.22.0 for Environment Variables and
1.56.0 for Notification Blocker, and F5 has reached it since 1.86.0.
- DNS & Hosts read the hosts file only once its DNS query had finished, which can take seconds,
and an entry added in that time was replaced when the file was read. The file is now read
alongside the query, and Add and Remove wait until it has been read. This was there since the
tab was added, in 1.6.0.
Verify the download
Get-FileHash .\SysManager-v1.136.53.exe -Algorithm SHA256
Expected SHA256: AE535141AE40FE54E586E3C224208BC453C207C19C90974C471F59157A885892
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.53.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.53.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.136.53