Undoing what w0a changed

To undo what w0a changed, pick one of three ways: a Fix page card for one thing that broke, Backups & Restore to reverse a whole group of changes from a checkpoint, or restore every checkpoint and then uninstall to have all of it gone. Fix cards write the Windows default and need no backup.

Three ways back

1. You know what broke — the Fix page

If one specific thing stopped working, repair that one thing. The Fix page has a card per symptom; search what you are seeing — "sound", "printer", "search" — and press the card's button.

Each card writes back the Windows default unless its own description says otherwise. Most cards do not read a backup, which means they also repair a machine that some other tool changed, and they work even if w0a's own backup file is gone. The two CS2 cards and the card that shows updates w0a hid are the exceptions: they work from what w0a itself saved, and without it they do nothing.

It also tells you what it did: "Fixed — 3 setting(s) put back to the Windows default." or "Nothing to fix — this was already at the Windows default." The second answer is real information: whatever is wrong, it is not this.

2. You want a whole change undone — Backups & Restore

The pages that change Windows settings in a group write a checkpoint before they run — system optimization, the CS2 profile, USB priority, internet settings, DNS and the Regedit Tweaks page. The GPU tuner is the exception: it writes driver values rather than Windows settings, and Reset is its undo. Log cleanup and removing an application write a checkpoint too, but only as a record of what ran: deleted files and a removed program cannot be brought back, so those two have no Restore to This Point button. A Fix card leaves nothing in the undo log; the one exception is the IPv6 card, which writes a value that is not the default and so saves the old one first. Backups & Restore lists the checkpoints, and restoring one puts back everything applied after it — that checkpoint's own changes and every later checkpoint as well. The confirmation says so before it starts. That is the honest behaviour rather than a limitation: what was applied after a point is what sits on top of it, so putting the machine back to that point means undoing those too.

This is the right choice when a session of changes went wrong and you want that session reversed rather than a specific symptom fixed.

3. You want all of it gone — restore everything, then uninstall

Restore every checkpoint, then uninstall. In that order: uninstalling first leaves the settings in place, because they are Windows settings and not w0a's files.

Where the undo log lives

%ProgramData%\w0a\backup.json — outside your user profile on purpose, so it survives a profile rebuild, and written by the elevated part of the application. That is also why a tweak writes only to registry paths on w0a's own allow-list: a restore accepts only records on a list compiled into the application, so a tampered log cannot send it anywhere else, and a value written outside the list could never be put back.

Related

• Uninstalling w0a
• Why it asks for administrator rights