Black screen after login in Windows 11 — where you enter your PIN or password, Windows appears to start loading, and then the screen goes black (possibly with just a cursor visible) — is recoverable in most cases. It looks worse than it is. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
First thing to check, before anything else: is the cursor movable? Move the mouse around. If the cursor moves, Windows loaded but Explorer or the display driver failed to initialise the desktop. That’s fixable. If there’s no cursor and no response to keyboard input at all, it’s either a display/driver problem or a more serious boot issue.
If the cursor is visible — restart Explorer
This is the fix for a large share of black screen after login reports. Ctrl + Alt + Delete → Task Manager → File → Run new task → type explorer.exe → check “Create this task with administrative privileges” → OK.
Desktop appears immediately. Done. Explorer crashed during startup and needed to be manually relaunched.
To prevent it from recurring: this usually means a shell extension or startup application is crashing Explorer during the login sequence. If it happens every time, check ShellExView (NirSoft, free) and disable non-Microsoft shell extensions to identify which one is crashing Explorer.
The display driver issue
Win + Ctrl + Shift + B sends a reset signal to the display driver without rebooting. Works even on a black screen. The screen will flicker once. If the desktop appears after the flicker, the GPU driver had crashed and needed resetting. Update the driver from the manufacturer’s website (not Windows Update) to prevent recurrence.
If Win + Ctrl + Shift + B produces a flicker but the desktop still doesn’t appear: the issue is beyond just a driver crash — Explorer isn’t starting either. Use Ctrl + Alt + Delete to reach Task Manager and run explorer.exe as described above.
Safe Mode to diagnose what’s causing it
If the black screen happens consistently on every login: boot into Safe Mode. Hold Shift while clicking Restart from the login screen’s power icon → Troubleshoot → Advanced options → Startup Settings → restart → press 4 for Safe Mode.
Safe Mode loads only essential Windows components. If the desktop appears normally in Safe Mode, something that loads at normal startup is causing the black screen — a startup app, a service, or a shell extension. From Safe Mode, disable startup items (Task Manager → Startup apps) and third-party services (msconfig → Services → Hide Microsoft services → disable the rest). Restart into normal mode and test after each group of disabled items.
The most common non-Explorer cause: graphics driver conflict
If the cursor is missing entirely and the screen is blank immediately after login, the GPU driver is failing before the desktop even loads. This often correlates with recent driver updates or Windows updates that changed display driver behaviour.
Boot into Safe Mode → Device Manager → Display Adapters → right-click the GPU → Properties → Driver → Roll Back Driver (if recent update) or Uninstall device → restart. Windows reinstalls a basic driver. If the desktop loads with the basic driver, update the GPU driver to the latest from the manufacturer — not from Windows Update.
Fast Startup leaving the display in a bad state
Fast Startup saves the Windows kernel session during shutdown and resumes it on boot. When connected monitors change between sessions — or when the display driver updates during the saved state — the resumed session tries to output to a display configuration that no longer matches reality. Black screen results.
Test: use Restart instead of Shutdown (Restart bypasses Fast Startup). If Restart gives a working desktop but Shutdown → Start gives a black screen every time, Fast Startup is the cause. Disable it: Control Panel → Power Options → Choose what the power buttons do → uncheck “Turn on fast startup.”
Profile corruption causing the black screen
A corrupted user profile can prevent the desktop from loading correctly while other user accounts work fine. Test: at the login screen, log into a different user account (or create a temporary one from Safe Mode: net user TestUser Password123! /add then net localgroup Administrators TestUser /add).
If the test account gets a working desktop: the issue is specific to the original user’s profile. The ProfileList registry key fix from the login loop guide applies here — particularly the .bak key removal that corrects corrupted profile path entries.
Second monitor connected but receiving the signal
This one is surprisingly common and easy to miss. After login, Windows might be outputting to a second display — an HDMI monitor that’s turned off, a projector that’s disconnected, a TV in standby. The primary display gets no signal because Windows sent the desktop elsewhere.
Win + P cycles through display modes. Press it even on the apparently black screen — if you hear the display mode sound or see a brief change, cycle through Duplicate, Extend, Second Screen Only, and PC Screen Only until something appears on your primary display. Pressing Win + P four times should return to PC Screen Only, which outputs to just the primary display regardless of what’s connected.
SFC and DISM from recovery
If none of the above resolve it and Safe Mode itself shows a black screen: boot into the Windows Recovery Environment (interrupt startup three times to trigger WinRE, or use a Windows 11 installation USB). Advanced options → Command Prompt.
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowRunning these offline fixes system file corruption that SFC in normal mode can’t address because the files are actively in use. After both complete, restart and test.
For the broader login failure scenarios that include but go beyond black screens, the Windows 11 login loop guide covers profile and registry repair approaches. If the display is entirely absent and this might be a GPU hardware issue, the display connection troubleshooting guide addresses display detection at the hardware level. Microsoft’s black screen troubleshooting documentation covers the full WinRE-based diagnostic sequence for cases where both Safe Mode and normal mode produce black screens.
Windows Hello PIN vs password login behaviour difference
Something worth noting: if the black screen happens when logging in with a PIN but not with a password (or vice versa), the issue is with the specific credential provider, not with the session loading. PIN credential provider problems can cause Windows to appear to accept the PIN but then fail during the post-authentication desktop load.
At the login screen, click “Sign-in options” → try the password option instead of PIN. If password login gives a working desktop: Settings → Accounts → Sign-in options → Windows Hello PIN → remove the PIN and set it up again. The re-setup process goes through a fresh verification that clears whatever was corrupted in the PIN’s stored data.
Third-party shell replacements
Applications like StartAllBack, Start11, or Classic Shell modify the Windows Explorer shell. When these applications encounter a compatibility issue with the current Windows 11 version — often after a major Windows update — Explorer either fails to load or loads the shell replacement software which itself crashes, resulting in a black screen after login where nothing visible ever appears.
If you have any such software installed: boot into Safe Mode → uninstall the shell replacement through Settings → Apps → reinstall it after confirming the base desktop works. The shell replacement’s own uninstaller properly removes its hooks from the Windows shell registration; using Safe Mode ensures the software isn’t running during its own removal.
Antivirus or security software initialising slowly
Some security products that perform boot-time scanning or hook deeply into the Windows startup process can cause a delay of several minutes between login and desktop appearance. The screen appears black during this period, not because the desktop failed to load, but because the security software is blocking Explorer from starting until its own scan completes.
Wait 5 full minutes on a black screen before concluding the desktop won’t load. If the desktop eventually appears (even after a delay), the security software is causing the wait. Check the software’s boot-time scan settings — most products allow disabling boot-time scanning while keeping real-time protection active.
Microsoft Teams or other startup apps crashing Explorer
Startup applications that crash during login can sometimes bring Explorer down with them, particularly if they have shell extensions registered. Teams, some versions of OneDrive, and certain cloud backup clients have been known to cause startup-phase crashes that result in a black desktop.
From Safe Mode with Task Manager access: Startup apps tab → disable all “High” impact startup apps → restart into normal mode. If the desktop loads normally, re-enable startup apps one at a time. The app that causes the black screen to return when re-enabled is the one crashing Explorer during startup.
Graphics card in a secondary PCIe slot (desktop)
On desktop machines with a GPU that may have moved or become partially unseated: if the black screen started after moving or transporting the machine, check the GPU’s physical seating in the PCIe slot. A partially unseated GPU can initialise during POST (which is why you see the BIOS screen and Windows loading) but fail to properly activate under the full Windows display driver — resulting in Windows outputting to integrated graphics (if available) or no signal at all.
Power down, reseat the GPU firmly, reconnect all PCIe power cables, and restart. Connect the monitor to the GPU’s ports, not the motherboard’s ports — if the monitor is connected to the motherboard video output on a machine with a dedicated GPU, you’re likely seeing integrated graphics output which may not receive the Windows desktop if the GPU is primary.
Restore point as a recovery path
If the black screen started on a specific date and hasn’t been present before that: Settings (accessible from Safe Mode) → System → Recovery → Advanced startup → System Restore → choose a restore point from before the issue started. System Restore reverses software changes without affecting personal files — it undoes driver installations, system updates, and software changes but leaves documents, photos, and settings intact.
This is often faster than systematic diagnosis when the cause is clearly related to something that changed on a specific date, especially if that something was a Windows update or driver installation that’s clearly visible in the restore point timeline.
When everything else is ruled out
If Safe Mode works, no startup app or service causes the black screen when individually re-enabled, no driver rollback helps, and system restore doesn’t resolve it: a Windows in-place upgrade (running setup.exe from Windows 11 installation media → “Upgrade this PC” → keep files and apps) reinstalls Windows from scratch while preserving everything. It’s the definitive software fix for cases where the desktop loading mechanism is broken in ways that can’t be repaired through individual component fixes.
This takes 45–90 minutes and requires a Windows 11 ISO or USB, but it’s genuinely the last resort before a full wipe and reinstall — and it almost always resolves persistent black screen issues that other approaches don’t.
The waiting test — longer than you think
One thing that saves a lot of unnecessary troubleshooting: after seeing a black screen at login, wait. Not 30 seconds — actually 5 full minutes. Background processes (antivirus scans, Windows Update staging, indexing) can completely block the desktop from appearing while they run at startup. The screen eventually lights up. If it does eventually appear, even after 3–4 minutes, the problem is a slow startup process, not a broken one. Reducing startup app count (Task Manager → Startup apps) and disabling boot-time antivirus scans is the fix for this pattern — not driver reinstalls or system repairs.
HDCP compliance and protected content
A specific and obscure cause: HDCP (High-bandwidth Digital Content Protection) handshake failing between the GPU and monitor. This can cause the display to receive a signal but refuse to show it, appearing as a black screen. It affects mainly setups using HDMI connections to TVs or monitors with strict HDCP enforcement.
Test by connecting a different monitor via DisplayPort instead of HDMI. If the display works on DisplayPort but not HDMI: the HDCP handshake is failing on the HDMI connection. Try a different HDMI cable (some older cables don’t support HDCP 2.2 required by newer content), check the TV’s HDMI input settings for an “HDCP” or “HDCP mode” option, or update the GPU driver which includes updates to the HDCP compliance module.
Remember that the fastest diagnostic for black screen after login is still the cursor test combined with the display mode cycle (Win+P). Two actions, both doable on a blank screen, and they immediately tell you whether the desktop is running but invisible (cursor present, wrong monitor), whether Explorer failed to start (cursor present but Win+P does nothing), or whether the display driver itself is the problem (no cursor at all). Getting that answer in 20 seconds is worth more than reading through every possible cause. Related: Windows 11 Black Screen.
