Why does admin sign-in fail after reboot with Administrator Protection enabled?

November 16, 2026 5 answers
Asked by 9b~ferrulecabin_263

On a domain-joined Windows 11 26H2 workstation, an administrator account fails to sign in after a reboot when TypeOfAdminApprovalMode is set to 2. Setting it to 1 restores access. A 25H2 computer baseline is enforcing the value of 2.

What should I check to understand the failure? Also, the policy setting isn't visible in Group Policy Management on Server 2022. Would updated ADMX files expose it?

Answers

_d62!modspindle.4

Start with the exact sign-in error and the events from the time of the failure. Check the Windows User Account Control log under Applications and Services Logs in Event Viewer, along with any relevant sign-in or access-denied events.

Compare the affected account on another machine, and try another account on the affected workstation. That can help narrow down whether the problem follows the account, its local profile, or the machine. Also check whether elevation with the same credentials fails.

9b~ferrulecabin_263:

The error says the specified account does not exist. The account works on other machines, while other accounts can sign in to this one. Elevation using the affected credentials fails too.

_p92~hingecradle.4:

That makes the local account profile and the relevant sign-in events useful places to look. The error alone doesn't explain which part of the process is failing.

Reply to this answer
h.618+buttonrivet

For the missing policy, this is a Security Option rather than an Administrative Templates setting. Updating ADMX and ADML files alone may not make it appear in an older editor. The available Security Options depend on the system running the management tools, including its sceregvl.inf definitions.

Try opening the GPO from an up-to-date Windows 11 machine with the Group Policy management tools installed. That can help you inspect the setting without changing the baseline.

Reply to this answer
4w!framepiston_896

Check whether the affected administrator uses a roaming profile or another configuration that Administrator Protection doesn't support. Microsoft lists roaming profiles and backup administrator accounts among the unsupported cases. It's a lead to investigate, not proof that either is causing this failure.

Reply to this answer
_j48+hexwicket.7

Changing the registry value is a useful test, but it doesn't identify the underlying failure. Since a GPO is enforcing the other value, check the applied policy and whether the value changes back. Keep that separate from the investigation into why the account fails with protection enabled.

Reply to this answer
2p~ticketgrommet_671

Was the workstation upgraded in place or freshly installed? Comparing those two cases could be useful if you have similar machines available. An upgrade-related difference is a possibility, though there isn't enough here to call it the cause.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions