Timeline for New Windows 10 account not seen as admin despite same config as old account
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 18, 2021 at 7:24 | vote | accept | Adventurous | ||
Aug 16, 2021 at 7:08 | answer | added | Adventurous | timeline score: 0 | |
Aug 16, 2021 at 3:57 | review | Close votes | |||
Aug 31, 2021 at 3:08 | |||||
Aug 16, 2021 at 3:40 | comment | added | Ramhound | I’m voting to close this question because the author considers the issue has resolved. | |
Aug 16, 2021 at 3:39 | comment | added | Ramhound | The builtin Administrator by default intentionally doesn’t have UAC enabled which is the reason you had to change the registry key. | |
Aug 16, 2021 at 2:38 | history | edited | Adventurous | CC BY-SA 4.0 |
added 201 characters in body
|
Aug 16, 2021 at 2:20 | comment | added | music2myear | 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 0:47 | comment | added | Ramhound | 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 | |
Aug 15, 2021 at 23:27 | history | edited | Adventurous | CC BY-SA 4.0 |
added 548 characters in body
|
Aug 15, 2021 at 22:18 | comment | added | anon | 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. | |
Aug 15, 2021 at 22:03 | review | First posts | |||
Aug 16, 2021 at 6:00 | |||||
Aug 15, 2021 at 22:02 | history | asked | Adventurous | CC BY-SA 4.0 |