Repair a post-login black screen caused by Explorer, shell configuration, or the user profile

Windows reaches the sign-in screen and accepts credentials, but the desktop, taskbar, or Explorer never appears or appears only after a long delay. Task Manager usually remains available. This includes failures that begin after a Windows feature update makes an installed ExplorerPatcher build, Start/taskbar replacement, third-party theme patcher, or other shell-injection component incompatible.

There is no unique Windows code for a missing desktop after sign-in. The useful identifiers usually come from Application or User Profile Service events, the faulting process, and its exception code.

Useful exact-message searches include The User Profile Service failed the sign-in. User profile cannot be loaded, explorer.exe - Application Error, sihost.exe - System Warning, and Unknown Hard Error. Search Event ID + process + exception code + faulting module; searching black screen alone merges graphics, profile, shell, update, display-output, and storage causes.

Use this procedure when manually starting Explorer, using a second account, Safe Mode, or disabling a shell customization changes the result. A strong variation-specific match is a black or grey post-login screen that begins immediately after Windows or the customization program updates and disappears when that exact shell, taskbar, theme, or UX patcher is removed.

Do not use it when the display is absent in firmware or WinRE, when Safe Mode and Task Manager are also unavailable, or when the system stops before sign-in.

The exact Windows build can remain unknown initially. Whether the problem follows the user profile, Explorer process, Winlogon shell values, startup service, or shell-customization program must be narrowed before permanent changes.

Before you start:

Task Manager or Safe Mode access
Administrator rights for configuration repair
A record of any shell, Start-menu, taskbar, theme, or Explorer customization installed before the failure

At the black screen, press Ctrl+Shift+Esc. If Task Manager opens in compact view, select More details.

Do not replace the entire Winlogon registry key.
Do not copy a complete old user profile over a new profile.
Do not disable Microsoft services in msconfig.
Do not permanently disable App Readiness solely because doing so shortens the black-screen delay.
Do not reset Windows before testing Explorer, a second account, and a clean boot.

Stop if the display is also absent in Safe Mode, registry values cannot be backed up, DISM requires an unmatched repair source, or the black screen occurs before sign-in.

Check the cause

In Task Manager, locate Windows Explorer.
If present, right-click it and select Restart.
If absent, select Run new task, enter:
```
explorer.exe
```
If the desktop appears, Explorer or shell startup is implicated.
If Explorer immediately exits, inspect Task Manager's process list for shell-customization software.
If Explorer does not restore the desktop, enter Safe Mode through WinRE Startup Settings.
In Safe Mode, determine whether the desktop loads promptly.

Proceed in order and stop when a step permanently resolves the failure.

Step A — Remove incompatible shell customization

In Safe Mode or the temporarily restored desktop, open Settings > Apps > Installed apps.
Locate recently installed or recently updated taskbar, Start-menu, Explorer, theme, or shell-patching software. Examples include ExplorerPatcher and third-party UX/theme patchers, but the product name alone is not proof; confirm the installed version and timing.
Uninstall only the implicated customization.
Restart normally.
If Explorer now starts, do not reinstall the same version.

Step B — Verify Winlogon values without blindly overwriting them

Open an administrator Command Prompt.

Query the shell values:

reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Shell
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Userinit

Normal values are:
- Shell = explorer.exe
- Userinit = C:\Windows\system32\userinit.exe,
If both values are already correct, do not rewrite them. Continue to Step C.

If one is demonstrably wrong, export the key first:

md C:\BootRepairBackup
reg export "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" C:\BootRepairBackup\Winlogon-before-shell-repair.reg

Correct only the wrong value:

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Shell /t REG_SZ /d explorer.exe /f
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Userinit /t REG_SZ /d C:\Windows\system32\userinit.exe, /f

Restart and test.

Step C — Test whether the problem is profile-specific

From the restored desktop or Safe Mode, open Settings > Accounts > Other users.
Create a temporary local test account.
Sign out and sign in to the test account.
If the test account loads normally, the original profile or its per-user startup configuration is implicated. Do not immediately copy the entire old profile over the new one.
If both accounts fail identically, continue to Step D.

Step D — Isolate third-party services and startup items

Run msconfig.
On Services, select Hide all Microsoft services before disabling anything.
Record the enabled third-party services, then select Disable all.
Open Task Manager's Startup apps page and disable nonessential startup items, recording each one.
Restart normally.
If the desktop loads, re-enable items in halves until the failure returns. The last group can then be tested one item at a time.

Step E — Repair Windows components when no third-party cause is found

From a working Safe Mode or temporary desktop, open an administrator Command Prompt.

Run DISM first:

DISM /Online /Cleanup-Image /RestoreHealth

Record the final DISM result.
Then run:
```
sfc /scannow
```
Restart and test.

Verify the result

The desktop and taskbar appear promptly after three sign-ins.
Explorer remains running.
The original and test-account results are understood.
Required third-party services have been re-enabled.
Sleep/wake and a cold boot return to the desktop normally.
Starting Explorer restores the desktop: Focus on shell startup, customization, and Winlogon values.
Removing the evidenced ExplorerPatcher, taskbar replacement, or theme/UX patcher restores the native desktop: Preserve its former version and the Windows build; do not reinstall the same incompatible combination.
A second account works: Preserve the original profile and migrate data selectively after identifying per-user startup or profile damage.
Clean boot works: A third-party service or startup item is responsible; binary-search the recorded items.
Explorer starts only after a long delay: Inspect App Readiness and profile-loading events. Disabling App Readiness may be a diagnostic test but is not a preferred permanent fix because it can interfere with application provisioning and updates.
DISM requires source files: Exact Windows build and edition become required. Stop rather than using arbitrary installation media.

Undo the change if needed

Re-import the saved Winlogon registry file if a corrected value makes the condition worse:

reg import C:\BootRepairBackup\Winlogon-before-shell-repair.reg

Re-enable clean-boot services and startup items from the recorded list. Remove the temporary account only after any required data and comparisons are complete.

Type	Searchable identifier	When it applies
Application event	`Event ID 1000` — `Application Error`	A shell process such as `explorer.exe`, `sihost.exe`, `ShellExperienceHost.exe`, or `StartMenuExperienceHost.exe` crashes. Record the faulting application, module, and exception code.
Windows Error Reporting	`Event ID 1001`	Windows Error Reporting records the crash bucket or follow-up report. Pair it with the application name and bucket/fault data.
Application event	`Event ID 1002` — `Application Hang`	Explorer or another shell process stops responding rather than immediately crashing.
User Profile Service	`Event ID 1500`	Windows cannot log the user on because the profile cannot be loaded.
User Profile Service	`Event ID 1508`	Windows cannot load the profile's registry file.
User Profile Service	`Event ID 1509`	Windows cannot copy or access a profile file during sign-in.
User Profile Service	`Event ID 1511`	Windows logged the user on with a temporary profile.
User Profile Service	`Event ID 1515`	Windows backed up or is using a profile state associated with profile-loading failure.
Exception status	`0xc0000005` — `STATUS_ACCESS_VIOLATION`	Event ID 1000 shows Explorer or a shell component accessing invalid memory, often because of a faulty shell extension or injected component.
Exception status	`0xc0000374` — `STATUS_HEAP_CORRUPTION`	The faulting shell process detects heap corruption; third-party extensions are a common suspect, not a proven cause.
Exception status	`0xc0000409` — `STATUS_STACK_BUFFER_OVERRUN`	A shell process terminates after a fast-fail/security check; use the faulting module to identify the component.
Windows stop/status	`0xc000021a` — `STATUS_SYSTEM_PROCESS_TERMINATED`	Winlogon or CSRSS terminated. This is an escalation beyond an ordinary Explorer-only black screen; preserve the named process and stop data.