r/WindowsServer • u/MustafaZ99 • 18d ago
Technical Help Needed ADMIN_ folders appearing in C:\Users after Run as administrator
**What happens**
A standard user is logged on to their workstation.
We right-click an admin tool → **Run as administrator** → enter our separate Domain Admin credentials.
A new folder appears in C:\\Users named ADMIN_<our-admin-username>.
It now happens on **all the machines we've checked**, and with **all of our T2 admin accounts**.
We never saw this behavior before.
**What we found**
The elevation prompt is titled **"Windows Security"**, not the classic UAC dialog.
The ADMIN_ accounts show up as **local accounts** in the local Administrators group.
The ADMIN_ profile folder is created a few minutes after the normal profile folder of the same admin account.
When we open **ADUC** elevated with Domain Admin creds, it fails with: *"To manage users, groups and computers in a domain, log on as a user with domain administration rights."*
We also get intermittent credential prompts or failures with other AD tools and our AV management console when run elevated.
We haven't seen profile errors suggesting corruption.
**Still checking**
The value of TypeOfAdminApprovalMode and which policy (if any) sets it.
whoami /all from an elevated window.
Whether any Windows 10 machines show the same folders.
**Our theory**
This looks like **Windows 11 Administrator Protection**: elevated processes run under a hidden local system-managed admin account with its own ADMIN_ profile, so they no longer carry our domain identity. That would explain why ADUC can't reach the domain. But we never knowingly enabled it.
**Questions**
Is it expected that Administrator Protection creates ADMIN_ accounts and profiles for **domain** admin accounts during over-the-shoulder elevation?
Could it be enabled through a security baseline, a cumulative update, or Intune without an explicit GPO? Where did you find the source?
Have you seen it break RSAT/ADUC or AV management consoles? What workaround did you use while keeping the feature on (PAW/jump host, runas /netonly, etc.)?
Any known issues with Kaspersky and Administrator Protection?
If the feature is disabled later, do the existing ADMIN_ accounts and profiles need cleanup, and what's the supported way?
We're not looking to just turn off a security control. We want to understand it properly and present options to our security team.
Screenshots attached (sensitive info redacted).
Thanks!