SysManager 1.111.0 አውርድ

[1.111.0] - 2026-09-18
If SysManager misbehaves, you can now hand somebody one file instead of four. Producing evidence for a
bug used to mean copying the environment info, exporting the system report, then leaving the app, opening a
hidden folder inside AppData, and working out which of up to fourteen daily log files covered the moment it
went wrong. The last two steps are not something most people can do, which meant most bugs simply could not
be reported. About now has a "Save diagnostics bundle" button that puts all of it into one .zip wherever
you choose. Nothing is sent anywhere — there is nowhere for SysManager to send it.
Added
- "Save diagnostics bundle" on the About tab. One .zip holding the system report, your environment
info, and the three most recent daily log files. A README.txt inside names every file, says plainly that
nothing was uploaded, and lists what was deliberately left out.
- The bundle leaves out your hardware addresses. Your network adapters' MAC addresses are not included,
and the last two parts of each local IP are replaced with x. A MAC address identifies your hardware
permanently, it survives reinstalling Windows, and it cannot be taken back once it is posted somewhere
public — and neither it nor your exact IP answers any question a bug report asks. Your Windows user name is
already removed from every log line before it is written to disk.
- An oversized log is cut to its most recent activity rather than left out or making the zip too large to
attach, and says at the top of the file how much was dropped. The end of a log is kept, not the beginning:
a log reads in order, so the problem being reported is at the end.
Changed
- SECURITY.md supported version moved to 1.111.x.
Verify the download
Get-FileHash .\SysManager-v1.111.0.exe -Algorithm SHA256
Expected SHA256: 269E57ECD46C5C07DEF606F69E4B6FA7FB8634121FFFEBF461702C0AD8B25A3A
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.111.0.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.111.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.