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.
Without elevation the application could show you 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 and CPU temperatures, published by its own developer, whose signature Windows verifies in front of you before anything runs.
- Nothing is written outside the registry paths on w0a's own allow-list. That list is code, not documentation — a value not on it is refused even if a bug asked for it.
- No file of yours is read, indexed or uploaded.
Can I run it without administrator rights?
You can start it, and the pages that only read will still show you things. Anything that changes a setting will fail. 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. Windows blocked the download explains how to verify the hash.
Related
Did this page help?
What was missing, or what did not work? We read every one of these.
If this page did not solve it, write to us — say which article you read, and we will fix the article.