Why it asks for administrator rights
w0a shows the Windows elevation prompt every time it starts. Here is exactly what it needs those rights for, and what it never does with them.
w0a asks for administrator rights because most of what it changes lives outside your user account: machine-wide registry settings under HKEY_LOCAL_MACHINE, Windows services, power plans and the undo log in %ProgramData%\w0a\backup.json. Without elevation it could show you values but change nothing, so it asks every time it starts and does not open if you decline.
What you see
A Windows prompt — "Do you want to allow this app to make changes to your device?" — before w0a opens. It appears every time, not just the first.
Why
Most of what w0a changes lives outside your own user account:
- Machine-wide registry settings (
HKEY_LOCAL_MACHINE) — the scheduler, the network stack, the power path. A normal user account cannot write there at all. - Windows services — starting the print spooler, putting a service back to Manual.
- Power plans — powercfg refuses to change a machine's active scheme without elevation.
- The undo log itself. The list of what was changed is written to
%ProgramData%\w0a\backup.json, outside your profile, so that a repair can still find it if your user account is later removed or rebuilt. - RAM timings — a reading, not a change, and one Windows does not expose: the values come from the memory controller's own registers through PawnIO, the optional driver the RAM Timings page offers to install. Installing that driver needs administrator rights, and w0a cannot open it without them either. CPU and RAM temperatures come through the same driver.
Without elevation the application could show you most readings and change nothing. We would rather ask once, plainly, than ship something that half-works.
What it does not use them for
- No driver is installed and no kernel component is loaded by w0a itself. The one exception is optional and asks you separately: a third-party module used only to read RAM timings and RAM and CPU temperatures, published by its own developer, whose signature Windows verifies in front of you before anything runs.
- A tweak writes a registry value only on a path from w0a's own allow-list, and saves the old value first. That list is code, not documentation — a path not on it is refused even if a bug asked for it. It binds the tweaks, not every part of w0a. The Fix cards, the Startup page and Deep clean in Uninstall Apps work outside it on purpose: their job is to reach what Windows, another program or an older version wrote. So do the in-game switches that hold notifications and update downloads back during a match, and they put the value back when the game closes.
- No file of yours is read, indexed or uploaded.
Can I run it without administrator rights?
No. w0a asks Windows for administrator rights every time it starts, and if the prompt is declined, it does not open. There is no useful way around this: the settings live where they live.
If the prompt appears with a publisher you do not recognise, stop and check the file. Checking the download really came from us explains how to verify the hash.
Related
What a game booster or optimizer can change in Windows, what it cannot, and how to check one before you trust it: Do game boosters and optimizers actually work?
3 days of Pro, claimed inside the app through Discord with no card: How the free trial works
Did this page help?
What was missing, or what did not work? We read every one of these.
Only what you type is sent, with the name of this page. Our server also records the connecting IP address to limit abuse and deletes it with the report. Please do not use this box if you are under 16. Privacy Policy
If this page did not solve it, write to us — say which article you read, and we will fix the article.