When Windows does not recognize any administrator account and Safe Mode is not available or fails, the issue is typically tied to Windows Recovery Environment (WinRE) configuration or security policies, or to deeper startup/profile problems. The following approaches are supported by the provided information.
- Check for the known WinRE administrator issue (policy blocking Microsoft accounts)
If the error appears inside Windows Recovery Environment (for example, when trying System Restore or Reset) and shows a message like:
You need to sign in as an administrator to continue, but there aren't any administrator accounts on this PC.
then a known issue may apply:
- If the Group Policy Accounts: Block Microsoft accounts is set to User can’t add or log with Microsoft account, WinRE can fail to recognize administrator accounts.
- The documented workaround is:
- Avoid setting Accounts: Block Microsoft accounts to User can’t add or log with Microsoft Account, or
- Set the MDM policy Security/RecoveryEnvironmentAuthentication to
2.
This change must be made from a working Windows session (for example, via another admin account, domain policy, or MDM) before booting into WinRE again.
- If Windows will not boot normally but can boot in Safe Mode
If at any point Safe Mode does become available and works, a driver or third‑party service is likely preventing normal startup:
- Boot into Safe Mode or Safe Mode with Networking.
- Use Event Viewer to inspect System and Application logs for driver or service errors around startup.
- Remove or update problematic third‑party drivers or software.
A more advanced registry‑based method (for experienced administrators only) is documented:
- In Safe Mode, open Registry Editor.
- Export
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal to SafeBoot.reg.
- Export
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services to Services.reg.
- Edit
SafeBoot.reg in Notepad and replace all occurrences of:
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal
with
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
- Save and merge
SafeBoot.reg (double‑click it), then restart in Normal Mode.
This forces services that load in Safe Mode to be used as a baseline for Normal Mode, which can bypass a faulty third‑party driver. Editing the registry is risky and should only be done by experienced administrators.
- If Windows logs on and immediately logs off
If the system appears to accept credentials but immediately logs off and returns to the sign‑in screen, the problem may be with the shell configuration (for example, userinit.exe or explorer.exe) in:
-
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
In that case, verify from a working environment (such as WinPE, another Windows installation, or offline registry editing) that the Userinit and Shell values point to valid binaries (for example, userinit.exe and explorer.exe).
- If startup is stuck (kernel phase issues)
If the system hangs at the spinning dots, shows a Stop error, or a black screen after the logo, advanced startup troubleshooting is required:
- Attempt Safe Mode or Safe Mode with Networking from Advanced Boot Options.
- If Safe Mode works, use Event Viewer to identify failing drivers or services and remove/update them.
If Safe Mode cannot be reached at all and WinRE also fails to recognize administrators, recovery may require:
- Reimaging or reinstalling the operating system from external media.
- Restoring from a known good backup.
- When none of the above works
If:
- No administrator account is recognized in WinRE due to policy, and
- Windows cannot boot to any mode that allows policy or registry changes,
then the supported path is typically to repair or reinstall Windows using installation or recovery media and then re‑join the device to the domain or MDM so that policies can be reapplied correctly.
References: