0

New Windows 10 account not seen as admin despite same config as old account

I have two accounts on my computer.

Both are admin.

Both have UAC set to "Notify me only apps try to make changes to my computer (default) / Don't notify me when I make changes to Windows settings.", therefore UAC isn't a relevant factor.

However, only one gets treated like an admin. 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.

How can I have the second account treated like the first account? What exactly is the state of the first account (UAC enabled but it doesn't have any prompts?)

What I've tried from looking at: https://answers.microsoft.com/en-us/windows/forum/all/windows-10-wont-recognize-me-as-administrator/b05b36ba-8b10-4d1a-869c-23403f7da72e

#1. Create a new account with command line "net user {username} /active:yes"

This has no effect. It creates a third account with the same behaviour as the second.

#2. Open up registry editor and go here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System Change EnableLUA to 0

This does not answer the question. The first account runs fine without this setting change.

UPDATE: Resolved as far as I'm concerned:

The whole purpose of this was to get a task running in startup (and avoid manually opening it each time). Assuming it's some unknown registry setting (I don't seem to have Group Policy), I got the task running a different way following these instructions: Disable UAC for a specific program (Windows 10)

Also the main purpose of switching to a new account was to change the username (and all corresponding files), but that's also a complicated procedure.

UPDATE:

Unsure what changes I could have made, I get the impression there is a "built-in administrator account" (the first one), which is treated differently than regular administrator accounts.

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.
    – John
    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
    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. 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
    Aug 16, 2021 at 3:39
  • I’m voting to close this question because the author considers the issue has resolved.
    – Ramhound
    Aug 16, 2021 at 3:40

1 Answer 1

0

Answer: built-in administrator and regular administrator accounts behave differently.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.