Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    I'm running programs that requires admin to work. In the first account, it just works. In the second account, I have to right click and run as administrator. Third new account works like second. ... There were group policy or registry changes to the first account because the third account is operating normally.
    – anon
    Commented Aug 15, 2021 at 22:18
  • 1
    You are aware that those UAC settings don’t actually disable UAC? If one of these accounts are the built-in Administrator account that would be why the behavior is different
    – Ramhound
    Commented Aug 16, 2021 at 0:47
  • Admin accounts still need "run as admin" in order for something to actually run as admin. You've made some change to your "working" account that makes this not happen there. The other account is functioning normally. Commented Aug 16, 2021 at 2:20
  • The builtin Administrator by default intentionally doesn’t have UAC enabled which is the reason you had to change the registry key.
    – Ramhound
    Commented Aug 16, 2021 at 3:39
  • I’m voting to close this question because the author considers the issue has resolved.
    – Ramhound
    Commented Aug 16, 2021 at 3:40