Fix Windows Logon UI Initialization Failure – Black Screen

You power on your machine, see the spinning dots, enter your PIN or password—then nothing. Just a black screen with a movable mouse cursor. No taskbar, no desktop icons, no Start menu. This is the Windows Logon UI initialization failure. You didn't break your computer. Windows shell (explorer.exe) didn't start because logon service (LogonUI.exe) choked or was blocked by a broken component.

The trigger is almost always one of three things: (1) A recent Windows Update that replaced a critical system file with a buggy version. (2) A registry edit that removed or changed the shell path under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon. (3) A corrupted user profile—often after a forced shutdown or disk full error. What's actually happening here is the system successfully authenticates your credentials, but the session manager (winlogon.exe) can't launch the interactive shell (explorer.exe).

Root Cause

The Logon UI (LogonUI.exe) is just a fancy authentication front-end. Once you're authenticated, winlogon.exe runs userinit.exe, which then runs explorer.exe. If userinit.exe is missing, damaged, or pointed to the wrong registry value, you get a black screen. Alternatively, if a third-party shell replacement (like a custom launcher) is set, it fails silently. The real fix is to verify and repair the shell path or restore a missing userinit.exe.

Fix: Step-by-Step

Boot into Safe Mode with Networking
Force restart your PC 3 times—hold power button when you see the spinning dots, let it fail three times. On the fourth boot you'll get the Automatic Repair screen. Go to Troubleshoot > Advanced Options > Startup Settings > Restart. Then press 5 for Safe Mode with Networking. If you can, use a recovery drive.
Check the Shell Registry Key
Press Win + R, type regedit, navigate to:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
```
Look for a string value named Shell. It must be exactly explorer.exe. If it's something else (like powershell.exe or blank), right-click it and set it back to explorer.exe. Also check Userinit—it should be C:\Windows\system32\userinit.exe, (with a comma at the end). A missing comma breaks it too.
Run System File Checker
Open Command Prompt as Administrator (right-click Start, select Command Prompt Admin or PowerShell Admin). Run:
```
sfc /scannow
```
This checks system files and replaces corrupted ones. It takes 10-20 minutes. On Windows 11 22H2 I've seen this fix the issue after a bad cumulative update (KB5025239 was notorious).
Restore userinit.exe if Missing
After SFC, check if userinit.exe exists at C:\Windows\System32\userinit.exe. If it's missing, copy it from another working PC of the same Windows version (same build number, e.g., 22621 for Windows 11 22H2). Place it into your System32 folder using a recovery USB or by booting from a Linux live USB. Alternatively, run DISM:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Then SFC again.
Create a New User Profile
If the above doesn't work, your profile is corrupted. In Safe Mode, open User Accounts (type netplwiz in Run). Add a new user with admin rights. Log out, log into the new account. If it works, migrate your data. The reason step 3 works is that SFC replaces system files, but profile corruption is user-specific data—a new profile skips the broken load.

If It Still Fails

Check your Event Viewer logs under Windows Logs > Application. Look for errors from Winlogon or Application Error with event ID 1000 referencing LogonUI.exe or explorer.exe. A common culprit I've seen on Dell Latitude 5420 laptops is a corrupted Intel graphics driver that hooks into the logon process—roll back the display driver in Safe Mode. Also, run chkdsk C: /f from Command Prompt to fix file system corruption. If you're still stuck after all that, consider a repair install using a Windows 11 ISO (keep files option). But that's rare—90% of cases are fixed by step 2 or 3.