Apr 04 2020 12:02 AM
Apr 04 2020 12:02 AM
Hello, first of all to start with the preface: Windows 10 Pro Version 2004 (OS Build 19041.172) - using an account that belongs to the administrator group....
When I try to open the (running as an administrator) mmc.exe or any derivative, i.e. local security policy manager, device manager. UAC blocks the app from running with the error "An administrator has blocked you from running this app. For more information, contact the administrator." The only way to open the apps is to run them using an administrative command prompt.
If anyone has any help that they can offer, or any questions would be greatly appreciated
Thank you, Teylor
Apr 06 2020 10:34 AM
This is by design. Being in the "Administrators" group is not the same as being THE Administrator. When you "run as Administrator" you are elevating to Ring 0, which has access to privileged areas of the OS. This is a security measure to prevent accidental access. Here's an [old but correct] article that should help. https://blogs.technet.microsoft.com/mrsnrub/2010/08/06/user-account-control-but-im-an-admin/
Apr 07 2020 05:45 AM
So what you are saying is that I shouldn't be able to access device manager, disk management, local security policy, etc. Just to clarify, I can access these through command prompt and it has only started blocking me recently
Apr 07 2020 06:55 AM
First, what build is this on? Just want to verify :)
Second, is this device managed by an IT department, or is it just a personal device?
I want to make sure I clearly understand your scenario.
1. You are logged in with a user that is a member of the local administrators group.
2. You are attempting to run various admin tools (mmc, Device Manager, etc.) from the Start Menu.
3. In doing so you are blocked by UAC.
4. You open an elevated command prompt ("run as administrator")
5. You can now open the admin tools from the elevated command prompt.
If this is your scenario, then that is correct and by design. You mentioned this changed. This is why I'm asking if your device is managed or not. If it is, then someone may have previously disabled UAC and it has either been reset, or intentionally turned on.
If this is an Insider build and is not managed AND you had previously disabled UAC and it was reverted to default, please file feedback and share the link so we can look into it.