Baixar SysManager 1.125.0 per a Windows

[1.125.0] - 2026-10-08
A new Recent Changes tab answers "it was fine last week — what changed?". It lists, day by day, what SysManager
did, what Windows installed or could not install, the programs installed, updated or removed, and the settings that
changed from the ones you saved, each with who made the change (#1507).
Added
- Recent Changes, in Info beside System Logs. It reads SysManager's own activity log; the history behind Windows'
Reliability Monitor, which records the Windows updates, Microsoft Store app updates, Defender definitions and
drivers that were installed or could not be, and the programs installed or removed with Windows Installer, including
while SysManager was closed, and needs no administrator rights; what New App Alerts noticed; and the settings saved
in Settings Watchdog. Each change is listed once: a program that Windows Installer and New App Alerts both saw within
ten minutes appears once, from Windows' record.
- Each time it is shown it keeps the list of installed programs, so a program that appears, goes away or changes
version between two looks is listed with the time between them — all that can be known about an installer Windows
keeps no record of. The first look only starts the list, and the page says so.
- Two or more updates Windows installed on one day are one row, with what they were by kind, that opens to the full
list. The list filters by kind — SysManager, Windows, Programs, Settings — and by period: 7, 30 or 90 days. Crashes
and programs that stopped responding in the same days are counted in one line that opens System Logs, and a source
that could not be read is named rather than shown as nothing changed. Rows open the Uninstaller, New App Alerts or
Settings Watchdog, and Export CSV saves what is shown.
- The Dashboard's Recent activity card has a See all changes button that opens it.
- %LocalAppData%\SysManager\installed-programs.json and settings-drift.json, the two records the tab keeps. A
profile export carries neither, since both describe this PC.
Changed
- New App Alerts keeps what it noticed between sessions: the last 200 detections, in
%LocalAppData%\SysManager\app-alerts.json. Until now the list was lost when SysManager closed. Clear History clears
the saved copy too, and its question now says Recent Changes loses them as well.
- Settings Watchdog records, each time it looks, when a setting that differs from your baseline was first seen and
when it went back or changed again, for Recent Changes. Saving a new baseline starts that record again.
- The activity log behind the Dashboard's Recent activity card keeps 200 entries instead of 60, to reach further back.
When it still does not reach the start of the period shown, Recent Changes says from when SysManager's own actions
are listed.
Verify the download
Get-FileHash .\SysManager-v1.125.0.exe -Algorithm SHA256
Expected SHA256: BD9AB2C86A426960D3A35F716BD53919FB472209E466ADDBF1A1CB21260D013A
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.125.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.125.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.