How to Fix Windows 11 Black Screen After Login — Cursor Visible But No Desktop, No Taskbar
You type your password. The login screen accepts it. The welcome message appears briefly. And then nothing. A solid black screen with your mouse cursor floating in the void. No desktop icons. No taskbar. No Start button. No wallpaper. Just blackness and a cursor that moves when you push the mouse but does nothing when you click.
Your computer is running. You can hear the fan. If you had music playing before the restart, you might even hear it resume in the background. The system booted, you logged in successfully, and Windows is running underneath. But the visual layer — the desktop, the taskbar, the icons, everything you actually interact with — is missing.
This is not a dead computer. This is not a hardware failure. This is Explorer.exe failing to start.
What Explorer.exe Actually Does
Most people think of File Explorer as the file browsing application — the window you open to navigate your folders. But Explorer.exe is far more than that. It is the Windows shell — the entire graphical layer that makes Windows look and feel like Windows.
Explorer.exe is responsible for:
- The desktop — the background wallpaper and all desktop icons
- The taskbar — the bar at the bottom with the Start button, pinned apps, system tray, and clock
- The Start menu — the menu that opens when you click Start or press the Windows key
- File Explorer windows — the folder browsing interface
- Desktop Window Manager integration — the compositing engine that renders transparent effects, shadows, and window animations
When Explorer.exe crashes or fails to start during login, ALL of these components are missing. The only thing that remains is the cursor, which is managed by a lower-level system process (csrss.exe) that started before Explorer.
The Immediate Fix: Launch Explorer Manually
You can bring back your desktop in 30 seconds:
- Press Ctrl+Shift+Esc — this opens Task Manager even when the desktop is not loaded
- If Task Manager opens minimized or in compact mode, click “More details” at the bottom
- Click File → Run new task
- Type
explorer.exe - Click OK
Within 2 to 3 seconds, your desktop wallpaper appears, the taskbar slides up from the bottom, and your desktop icons populate. Everything is back to normal.
If Ctrl+Shift+Esc does not open Task Manager, try Ctrl+Alt+Delete first — this opens the security options screen where you can click “Task Manager.” If neither works, press Windows+R to attempt opening the Run dialog directly, then type taskmgr and press Enter.
This manual launch is a temporary fix — it gets you back to work immediately. But if you do not fix the underlying cause, the black screen will return on the next login.
Why Explorer.exe Crashes at Startup
Explorer.exe is one of the first user-mode processes that loads after login. During initialization, it:
- Reads the shell configuration from the registry
- Loads the desktop composition engine (requires the GPU driver)
- Initializes the taskbar and system tray
- Loads shell extensions from installed applications
- Processes the Startup folder and Run registry keys
- Renders the desktop icons and wallpaper
A failure at any of these steps can crash Explorer before the desktop appears. The most common causes:
GPU driver crash. The desktop composition engine depends on the GPU driver to render the visual shell. If the GPU driver is corrupted, outdated, or incompatible, Explorer crashes during step 2 — before anything visual appears. This is the most common cause of the black screen with cursor, especially after Windows updates that replace GPU drivers.
Corrupt shell extension. A broken DLL from a third-party application that registers a shell extension (context menu handler, icon overlay, property sheet handler) can crash Explorer during step 4. The extension loads inside the Explorer process, and a crash in the extension takes down all of Explorer.
Fast Startup restoring corrupt state. Fast Startup saves the kernel session to disk during shutdown and restores it during boot. If the saved session includes a corrupted Explorer state, the corruption is faithfully restored on every boot, causing the black screen repeatedly.
Malware modifying the shell registry entry. The registry value at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon → Shell tells Windows which executable to use as the desktop shell. Normally this is explorer.exe. If malware changes this value to something else — or to nothing — the desktop shell never loads.
Fixing the GPU Driver
Since GPU driver problems are the most common cause, address this first:
From the black screen, open Task Manager (Ctrl+Shift+Esc) and use File → Run new task:
- Type
devmgmt.msc→ OK (opens Device Manager) - Expand Display adapters
- Right-click your GPU → Update driver → Search automatically
- If the problem started after a recent driver update: right-click → Properties → Driver tab → Roll Back Driver
For a completely clean GPU driver installation:
- Uninstall the GPU driver from Device Manager (check “Delete the driver software”)
- Restart — Windows will use a basic display driver (low resolution but functional)
- Download the latest driver from NVIDIA, AMD, or Intel
- Install and restart
If you cannot access Device Manager from the black screen, boot into Safe Mode — Safe Mode uses a basic display driver that bypasses GPU driver issues entirely.
Disabling Fast Startup
Fast Startup is the most frequent cause of the black screen returning after you have fixed it once. You fix the problem, restart successfully, and the next time you shut down and boot up, the black screen is back — because Fast Startup saved and restored the pre-fix corrupted state.
From the recovered desktop (after launching Explorer manually):
- Open Control Panel (search for it or run
control.exe) - Go to Power Options → Choose what the power buttons do
- Click “Change settings that are currently unavailable”
- Uncheck “Turn on fast startup”
- Click Save changes
With Fast Startup disabled, every shutdown is a true full shutdown, and every boot is a true clean boot. No corrupted state is preserved across power cycles.
Checking the Shell Registry Value
If you suspect malware or if Explorer never starts even when launched manually from Task Manager, check the shell configuration:
-
Open Registry Editor (run
regeditfrom Task Manager → File → Run new task) -
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon -
Find the value named Shell
-
Its data should be exactly:
explorer.exe
If it says anything else — a different executable path, or if the value is empty — that is the problem. Double-click the Shell value and change it back to explorer.exe. Restart and the desktop should load normally.
Also check HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon for a user-specific Shell override. If a Shell value exists here, delete it to let the system-wide value take effect.
The Safe Mode Diagnostic
If none of the above fixes work from the black screen, Safe Mode is your diagnostic environment:
- From the login screen (before the black screen occurs), hold Shift and click the power icon → Restart
- Select Troubleshoot → Advanced options → Startup Settings → Restart
- Press 4 or F4 for Safe Mode (or 5/F5 for Safe Mode with Networking)
Safe Mode loads Windows with minimal drivers and no third-party startup programs. If the desktop loads normally in Safe Mode, the problem is a driver or a startup application — not a Windows system file corruption.
From Safe Mode, you can:
- Update or reinstall GPU drivers
- Disable startup programs in Task Manager → Startup tab
- Run
sfc /scannowandDISM /Online /Cleanup-Image /RestoreHealth - Check the Shell registry value
- Uninstall recently installed applications that might have caused the conflict
The black screen after login is terrifying because it looks like your computer is broken. In reality, the computer is running perfectly — it is just the visual shell that failed to load. Pressing Ctrl+Shift+Esc and launching Explorer manually gets you back to work in seconds. Then fixing the root cause — usually a GPU driver issue or Fast Startup restoring bad state — prevents it from happening again.