Black Screen After Login in Windows 11, Explained
I had a client's desktop do this to me a couple of years back, on a machine I'd have sworn was fine the day before: type the password, screen goes black, cursor floats there like it's waiting for something that never shows up. Ctrl+Alt+Del still worked, which told me the machine hadn't actually locked up — something in the handoff between "you're logged in" and "here's your desktop" had stalled. That distinction matters more than almost anything else in this troubleshooting path, so it's worth sorting out before you do anything else.
A black screen after login in Windows 11 almost always means one of two things: the desktop shell (explorer.exe) never started or crashed immediately after starting, or the graphics stack is stuck and simply isn't drawing anything even though Windows itself is running underneath it. The first is a login/profile/shell problem. The second is a driver problem. They look identical from where you're sitting, so the first job is telling them apart, and the fastest way to do that is checking whether Task Manager opens.
Press Ctrl+Shift+Esc. If Task Manager pops up over the black screen, Windows is running fine — you're specifically missing the shell, which narrows things considerably. If Task Manager also refuses to appear, or your keyboard and mouse seem completely dead, you're looking at something lower-level: a driver that's hung the display pipeline entirely, or in rarer cases a USB power issue during boot cutting off input devices before the desktop loads. I'll cover both paths, but start with the Task Manager test because it decides which set of fixes is worth your time.
If Task Manager opens: it's the shell, not the display
The quickest thing to try, before touching anything else, is forcing a graphics driver reset without a full reboot: press Win+Ctrl+Shift+B. You'll likely hear a short beep and see a flicker. This restarts the display driver in place, and if a stuck GPU driver was the actual cause, your desktop appears immediately. It costs nothing to try even if you suspect the shell is the real problem, so I do this first regardless of which path I think I'm on.
If that doesn't help, go back to Task Manager, click File → Run new task, type explorer.exe, and check Create this task with administrative privileges before confirming. On most black-screen-after-login cases I've dealt with, this alone brings the desktop up. What it tells you afterward matters: if the desktop comes back clean and stable, explorer.exe simply failed to auto-launch that one time, and you're looking at something intermittent rather than a hard failure — worth watching for a pattern (does it happen every login, or once in a while) before spending more time on it.
If explorer.exe launches but crashes again within seconds, or won't launch at all, check the Windows Logon registry value, since a corrupted or manually-edited Shell value here will produce exactly this symptom on every single login rather than intermittently. Open regedit (via Run new task if Start isn't reachable), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon, and confirm the Shell string value reads exactly explorer.exe. If it's blank, points somewhere else, or has extra characters appended, that's your cause, and fixing it is a one-line edit rather than a reinstall. Back up the key before changing it — right-click the Winlogon key, Export, save the .reg file somewhere safe — so you have a rollback path if you mistype something.
Fast Startup is worth ruling out even without other symptoms
Fast Startup saves a hibernated kernel image to disk on shutdown and reloads it on boot instead of doing a full cold start, and on some hardware and driver combinations that saved state is corrupted or stale in a way that manifests as exactly this black-screen pattern — intermittently, and often worse after a driver or firmware update than it was before. I don't have a reliable figure for how often Fast Startup specifically causes this versus other things, so I won't claim it's a leading cause, but it's low-effort to rule out and it's genuinely fixed real black-screen cases I've worked on.
Open an elevated Command Prompt or Terminal and run powercfg /h off. This disables hibernation and Fast Startup together and deletes hiberfil.sys, freeing disk space roughly equal to your installed RAM as a side effect. If you'd rather use the GUI: Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → uncheck Turn on fast startup (recommended). On an SSD, forcing a full cold boot instead of Fast Startup typically only adds three to ten seconds to your next startup — a trade I'd take without hesitation given how many odd startup bugs Fast Startup has been implicated in over the years, this one included.
What if Task Manager won't open either
This points more toward the display stack itself being stuck rather than the shell, and your best move is getting into Safe Mode, where Windows loads a minimal driver set and bypasses whatever's hanging. If you can't reach the desktop at all to trigger Safe Mode through Settings, force it through three interrupted boots: as soon as you see the Windows logo appear, hold the power button for about ten seconds to force it off. Repeat this twice more. After the third interruption, Windows should boot into the Automatic Repair environment on its own — from there, go to Troubleshoot → Advanced options → Startup Settings → Restart, then press 4 for Safe Mode (or 5 for Safe Mode with Networking, if you need internet access from within it).
If the black screen doesn't happen in Safe Mode, that's a strong confirmation the problem sits in a non-essential driver rather than in Windows itself — most often the graphics driver. From inside Safe Mode, open Device Manager, expand Display adapters, right-click your GPU, and if this started shortly after a driver or Windows update, choose Roll back driver rather than reinstalling the same version. If no rollback option is available, update to the current driver from the GPU vendor's site directly rather than through Windows Update, since vendor packages sometimes include display stack fixes that the generic Windows Update driver doesn't.
One thing I'd flag before you go further: if this machine has BitLocker enabled, Safe Mode and Startup Repair may prompt for your recovery key. Have it ready — check your Microsoft account's device recovery keys page beforehand if you're not sure you have it written down anywhere, because getting stuck at a BitLocker prompt mid-repair with no key handy is its own special kind of frustrating.
Enterprise and managed devices: a known timing bug is worth checking
If this is a domain-joined or centrally managed PC on Windows 11 24H2 or 25H2, and the black screen happens specifically on the first login after a cold boot but not on subsequent sign-outs within the same session, that pattern matches a documented shell-initialization timing issue Microsoft has acknowledged and is actively rolling fixes for — XAML-dependent components including the shell not finishing registration before Windows tries to display the desktop. It's scoped by Microsoft to enterprise and managed environments rather than typical home PCs, so it's not the first thing to check on a personal laptop, but if your symptom pattern matches — self-resolves after a couple of minutes, or clears the moment you restart explorer.exe manually — flag it with whoever manages Windows Update deployment for your organization rather than treating it purely as a local repair.
Confirm-before-you-fix table
| Symptom | Confirming check | Fix |
|---|---|---|
| Black screen, cursor works, Task Manager opens | Run new task > explorer.exe brings the desktop back | Check Winlogon Shell registry value; watch for recurrence |
| Black screen every single login, same pattern each time | Winlogon Shell value is missing, blank, or altered | Correct the Shell string value to explorer.exe |
| Black screen only after certain shutdowns, not restarts | Disabling Fast Startup stops it recurring | Turn off Fast Startup / hibernation |
| Task Manager won't open, keyboard/mouse unresponsive | Same black screen persists in Safe Mode | Investigate hardware/firmware; graphics driver rollback less likely to help |
| Black screen resolves in Safe Mode but not normal boot | Recent driver or Windows update timing lines up | Roll back or update the graphics driver from vendor site |
| Managed/domain PC, resolves after 2-3 minutes on its own | Matches XAML shell timing bug pattern | Report to IT; check for the current cumulative update |
What I'd do differently if I hit this again
I spent almost forty minutes on that client machine trying driver rollbacks before I thought to just check Task Manager first — because the black screen looked so much like a display failure that I assumed it was one. If I'd tested whether Ctrl+Shift+Esc actually opened anything in the first two minutes, I'd have known immediately I was chasing a shell problem, not a driver one, and skipped a chunk of wasted effort. That's the one thing I'd tell past-me to do differently: don't assume which category a black screen falls into based on how it looks. Test it.
I'd also disable Fast Startup by default on any machine I set up from now on, particularly ones with older or unusual GPU/motherboard combinations. The time saved on boot is small, and the number of odd, hard-to-diagnose startup issues linked to Fast Startup over the years — this one included — makes it a poor trade for most desktop users, though laptop owners chasing every second of battery life on resume may reasonably decide otherwise.
If none of this works
Before reaching for a reset or reinstall, create a new local administrator account and test whether the black screen follows you into it — from an elevated Command Prompt, net user TempAdmin Str0ngP@ssTemp! /add followed by net localgroup Administrators TempAdmin /add, then sign out and into the new account. If the new profile loads a normal desktop, your original profile is corrupted rather than Windows itself, and migrating your files to a fresh profile is a smaller job than a full reset. If the black screen follows you into a brand-new profile too, that's your signal the problem is systemic rather than profile-specific, and at that point Settings → System → Recovery → Reset this PC (Keep my files) is the reasonable next step — back up anything irreplaceable from Safe Mode first regardless.