SysManager 1.123.0

[1.123.0] - 2026-10-07

Undo Changes puts back what SysManager changed, one change at a time, from one page. Five tabs each kept what they
needed to undo their own change, and each copy could only be used from the tab that made it, so putting something back
meant remembering which tab that was.

Added

• Undo Changes, a new tab in System, above Restore Points (#1525). It lists, in plain words, what SysManager can
  still put back, one row for each copy:
  • Performance Mode's settings, once game mode is off, since until then they are game mode's. Its question lists each
    one from how it is now to how it was before Performance Mode was first used: "Power plan: Ultimate Performance →
    Balanced";
  • the services SysManager turned off that are still off, in one row that turns them all back on, each to the startup
    type it had;
  • the hosts file once SysManager has written it, and the environment variables, from the copy kept before
    SysManager first changed them, for as long as they differ from it;
  • game mode, while it is on, or after a run that did not end cleanly left it on;
  • and the settings saved in Settings Watchdog that have changed since and that it can write back, as one row that
    opens that tab, where Restore changed puts them back.
• Each one asks first, saying what will change, and goes back through the same restore its own tab uses. It reads
  the copy again before changing anything, and changes nothing if the copy no longer says what the question did. One
  that stops part-way says what went back and what did not, and the list then shows what is still different. A row
  that needs administrator rights says so. A copy that could not be read just now, could not be compared with how
  things are now, could not be used, or is damaged, is named as such rather than shown as nothing to put back. There
  is no "undo everything". The page looks again each time it is shown, and on Refresh or F5.
• Each change put back shows in the Dashboard's Recent activity, as Undo Changes with what went back, such as
  "Turned services back on".
• The page also says where else to look: the tabs whose switches are their own undo, Restore Points for the whole
  PC at once — naming the newest restore point when SysManager runs as administrator — and, plainly, what cannot be put
  back: files deleted for good, removed preinstalled apps and uninstalled programs.
• Searching the sidebar for "undo", "put back" or "revert" finds it, and Restore Points now says it is there. The
  issue forms list it too.

Changed

• The tab that made a change hears that Undo Changes put it back. Performance Mode, Services, DNS & Hosts,
  Environment Variables and Gaming Profile read their state again, so none of them goes on showing a change that is
  gone. Without that, Gaming Profile would have kept its Start button off after Undo Changes turned game mode off, and
  DNS & Hosts would have saved its old list over the restored file. An edit not yet saved on DNS & Hosts, or not yet
  applied on Environment Variables, goes with the old list, since it was made to what Undo Changes just replaced.
• Performance Mode reads its record of your original settings from disk before every change and every Restore All,
  rather than trusting the copy it read when it opened. A copy kept in memory after the record was put back and deleted
  would have made the next change record no original at all. Restore All, and each Apply, now say when that record
  cannot be read just now, or is damaged, instead of going on with what was read earlier. Each Apply, and Restore All,
  acts on what its question showed, even when the settings are read again while the question is open.
• Environment Variables says when its copy could not be read just now, on Apply and on Restore backup, rather than
  calling it invalid, so a copy another program happened to have open is not taken for a damaged one.

Fixed

• Restore All on Performance Mode can finish once the NVIDIA card it recorded is gone. Since 1.56.7 it stopped
  at the graphics setting when the card it was recorded on had been taken out, or its driver removed so that its
  place in the registry belonged to another card. By then the power plan, visual effects, Game Mode and the Xbox
  settings were back, but the processor minimum was not, and the record of your original settings stayed, so every
  later Restore All failed the same way. It now leaves that one setting out, says so in its question, and puts back
  everything else.
• Restore All's question no longer promises a power plan called "Unknown". Since the first Performance Mode, in
  0.12.0, a record that could not read the plan when it was made listed one, though Restore All leaves the plan alone
  then; it now says the plan stays as it is.
• Gaming Profile no longer says it reverted a session it could not read. Since crash recovery came in, in 1.52.38,
  a record of the session left on that could not be read once you answered "revert" read as no session at all, and
  the tab said the leftover changes were reverted while they were still on. It now says nothing was reverted, keeps
  the record, and asks again the next time it starts.

---

Verify the download

Get-FileHash .\SysManager-v1.123.0.exe -Algorithm SHA256

Expected SHA256: 3F8ED90D37BE3935D4021CED5A7C67CB0C70A65EC805498E4C668B568F145B21

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.123.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.123.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.