Λήψη SysManager 1.136.96

[1.136.96] - 2026-11-03
System Logs and the System Report explain an event only for its own source, and a blue screen is explained as one.
Fixed
- System Logs and the System Report explained events by their ID alone when they had nothing for the source and ID
together, and an event ID belongs to its source. So every event 1000 was "A program crashed", with advice to look
for a faulting module, though many sources use 1000 for ordinary messages, an informational .NET Runtime trace
line among them, and IDs 1001, 41 and 6008 had the same problem. An explanation now applies only to the source it
was written for; any other event is described from its severity and source.
- A blue screen got the explanation of an application's crash report, because its row was keyed by "BugCheck", the
source Event Viewer shows, rather than the provider Windows records. It now says Windows blue-screened and points
to the memory dump. Tcpip 4227 was blamed on Wi-Fi or a cable; Windows' own text says a program opened and closed
connections so fast that it ran short of local ports, which a link cannot cause. All three were there since the
first release, 0.3.0.
Verify the download
Get-FileHash .\SysManager-v1.136.96.exe -Algorithm SHA256
Expected SHA256: CAAF30DEA0E4D0B98131AF45B505C7851FDBF6F84077CBCDC84B7433BE5591F4
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.96.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.96.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.