Unable to turn off "Always run as administrator
Microsoft PowerToys version
0.61.1
Running as admin
- [X] Yes
Area(s) with issue?
General
Steps to reproduce
Turning off "Always Run as Administrator" doesn't work. Requires admin login at every startup.
✔️ Expected Behavior
Unchecking "Always Run as administrator" would save the setting. Restart of PowerToys would not require an admin login.
❌ Actual Behavior
PowerToys asks for admin login during next restart. "Always run as administrator" is checked on again.
Other Software
No response
/bugreport
Hi there!
We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks! 
Not OP but I have the same problem. In my case, the likely culprit is that PowerToys is started using UAC with another account that the session actually open.
Had to go to the desktop folder of that user to get the diagnostic zip and a bunch of other features are broken (fancyzone win+arrows, key remapping). PowerToysReport_2022-08-16-13-55-19.zip
Very likely the cause. Company policy now requires me to use a new administrator account separate from my main user account which I used to install initially. Uninstall and reinstall seems to keep everything linked to the original user account.
PowerToysReport_2022-08-25-16-18-58.zip Here is the Bug Report as requested.
Don't know if this helps anyone, but if you navigate to 'C:\Users%username%\AppData\Local\Microsoft\PowerToys' and open the settings.json in a text editor there is a "run_elevated" option. I changed that to 'false' and relaunched the app and it fixed my issue.
Don't know if this helps anyone, but if you navigate to 'C:\Users%username%\AppData\Local\Microsoft\PowerToys' and open the settings.json in a text editor there is a "run_elevated" option. I changed that to 'false' and relaunched the app and it fixed my issue.
Ah right, it reads the config from the launching user's config but saves it to the configuration of the elevated user. Makes sense.