A cursor that still moves means the display path is working and the desktop shell is not. Restart explorer.exe from Task Manager first, then reset the graphics driver with Win+Ctrl+Shift+B. If the screen is still black in Safe Mode, or the cursor is gone or frozen, stop treating this as software and test the display path.
At a glance
- Class
- PC Hardware
Provenance
- Nov 16, 2026Published
TL;DR · Black screen with a cursor
- A cursor that moves is good news. It means the graphics card, cable and panel are all still doing their jobs.
- Restart the shell first: Ctrl+Shift+Esc, then right-click Windows Explorer and pick Restart, or File > Run new task and type explorer.exe.
- No picture but a live cursor after a blink: Win+Ctrl+Shift+B resets the display driver, and a Windows log entry records the recovery.
- Stop at Safe Mode. Black there too, or no cursor anywhere, and the fault is below Windows.
A Windows 11 desktop that goes black while the pointer still glides across it is one of the more misleading failures in PC troubleshooting. Nothing is frozen. The fans are running, the disk light blinks, and the mouse moves, but every window, icon and taskbar button is gone. What you are looking at is a session where Explorer, the process that draws the desktop, has stopped painting, while the rest of the display pipeline keeps working.
That single observation decides everything after it. A pointer that tracks your hand is drawn on top of whatever the desktop is producing, so the graphics card is scanning out an image and the panel is displaying it. The fault is above the hardware. Work it in this order, and you will usually be back on the desktop in under a minute without touching a driver.
What a visible cursor tells you
| What you see | What it points at | First check |
|---|---|---|
| Cursor moves, everything else is black | Explorer stopped painting | Restart the desktop process |
| Picture blinks and returns on its own | The display driver timed out and recovered | Driver log, then a clean install |
| Cursor moves, black only since a specific update | A change in that update | Uninstall that update |
| Cursor moves, black only with a dock attached | The external display path | Undock and test the panel alone |
| Cursor frozen, or no cursor at all | The display path itself | The monitor’s own menu and a second source |
The last row is the one people skip. A frozen pointer is not a shell problem wearing a disguise; it means Windows is not delivering a usable image, and no amount of Explorer restarting will change that. Take it to the no-signal guide and start with the monitor’s built-in menu.
Restart the shell from Task Manager
Microsoft’s blank-screen troubleshooting article gives this as the fix for exactly the symptom you are looking at. Press Ctrl+Shift+Esc to open Task Manager, find Windows Explorer in the Processes list, right-click it and choose Restart. If the entry is missing, the same page says to “go to File > Run new task, type explorer.exe, and press Enter”.
Two details make the difference between this working and this looking broken:
- Task Manager opens on top of a black screen. It draws its own window, so it appears even when the desktop does not. If it does not open at all, skip to Safe Mode below.
- Ctrl+Alt+Delete is the alternate door. Microsoft’s guidance is that if you see the security screen, launch Task Manager from there and restart Windows Explorer. That route works when the Ctrl+Shift+Esc shortcut is swallowed.
If the taskbar and icons return, note how long they survive. A desktop that stays up means you had a one-off crash of the shell. A desktop that dies again within minutes means the process is being killed by something that loads with it, and the Safe Mode test later in this article is how you find out whether that something is a startup program, a shell extension or the driver.
This fix does not survive a reboot, and it is not meant to. It gets you a working desktop so the rest of the checks can be run from Windows instead of from a recovery menu.
Reset the display driver and read the log
Press Win+Ctrl+Shift+B. It resets the graphics driver in place. Microsoft’s page describes the expected result precisely: you “should hear a beep or see a screen flicker if successful”. If your picture returns on that blink, you have learned something specific. The black screen was consistent with a timeout detection and recovery event, which is Windows detecting that the GPU did not finish an operation and resetting the graphics stack to keep the machine responsive.
Microsoft’s WDDM driver documentation explains the default behaviour: the operating system waits two seconds for the GPU to complete or preempt a task, and if it cannot, the OS diagnoses the GPU as frozen and resets it. When that completes, the OS displays an informational message, “Display driver stopped responding and has recovered”, and logs that message in Event Viewer.
That log line is worth finding, because it is the difference between a theory and a record:
- Open Event Viewer (press Win+R, type
eventvwr.msc, press Enter). - Go to Windows Logs > Application.
- Press Ctrl+F and search for
Display driver stopped responding.
Read the timestamp. If it matches the moment your screen went black, you have a driver recovery on record, and the clean reinstall further down is the right repair. If the log is empty at that time, that is not proof of anything by itself. It only means this particular mechanism left no entry you can find.
One more line from Microsoft’s documentation explains a symptom that confuses people after a successful recovery: “Some legacy DirectX applications might just render black at the end of this recovery, which requires the end user to restart these applications.” So if the desktop comes back but one game or one window is still a black rectangle, close and reopen that application before you conclude anything about the GPU.
Safe Mode is the test that separates shell from firmware
Safe Mode answers one question and answers it well: does this still happen with a minimal Windows? Microsoft’s Startup Settings page states that “Safe mode starts Windows in a basic state, using a limited set of files and drivers”, and adds that a problem which does not occur there is likely not caused by default settings or basic drivers.
You can reach it two ways, depending on whether you have a desktop to click on:
- From a working desktop, or from Task Manager’s File > Run new task if you can reach Settings: go to Settings > System > Recovery > Advanced startup and select Restart now, which Microsoft documents on its recovery options page.
- When the desktop is dead: hold the power button for ten seconds, repeat two or three times until Windows enters Recovery Mode, then choose Troubleshoot > Advanced Options > Startup Settings > Restart. On the Startup Settings screen, F5 starts Safe Mode with Networking according to Microsoft’s blank-screen page, while 4 or F4 selects plain Safe Mode on the Startup Settings page.
Read the result carefully:
| Safe Mode result | What it means | Next step |
|---|---|---|
| Desktop draws normally | The shell works with a minimal driver set | The conflict loads with the normal driver set or a startup program |
| Black screen, cursor still moves | Not a third-party startup app | Roll back or reinstall the display driver |
| Black screen, no cursor | Not a Windows shell problem | Stop and test the display path |
In the middle case, roll the driver back before you remove it. Microsoft’s blank-screen page says that if the issue started after an update, select Roll back driver — you reach it through Device Manager > Display adapters > your GPU > Properties > Driver. If no previous driver is stored, the clean install below is the alternative.
Disconnect docks and extra displays
A dock or an external monitor can leave a laptop panel dark while Windows happily believes it is drawing to a working screen. Microsoft’s page is blunt about the test: “If using a laptop, disconnect external displays and peripherals.” It also suggests cycling display modes with Win+P, which is faster than unplugging and often enough to bring the internal panel back.
If the internal panel lights up the moment the dock is out, you are not troubleshooting Windows any more. The desktop is fine; the external path is not. Work that with the second-monitor detection checks, and if the external screen drops and returns rather than staying dark, the random blackout guide matches the symptom better.
The inverse is also worth stating, because it sends people down the wrong path: if one monitor is black and the other shows your desktop, this article does not apply. A shell failure blanks every display at once.
Remove the update that started it
If the timeline points at an update, undo that update rather than the whole system. Microsoft’s uninstall guide gives the Windows 11 route: Start > Settings > Windows Update, then under More options choose Update history, and under Related settings choose Uninstall updates, select the update and choose Uninstall.
When you cannot get into Settings far enough to click anything, the same page documents the recovery-environment equivalent: reach Windows RE, then Troubleshoot > Advanced options > Uninstall updates, and select the option for the latest quality update.
Two cautions come from the same page and are easy to skip in a hurry. Some updates cannot be uninstalled, and Microsoft warns that you should understand the risks of removing a security update, recommending that Windows 11 users try reinstalling Windows before going that route. I would add a practical one: write down the KB number and the date before you remove anything, because if the black screen returns you will want to know exactly which change you reversed.
Unlike the shell restart, this one survives a reboot. That is the point of doing it.
Clean driver reinstall, and when to stop
A clean install is the right repair when you have a driver recovery on record, a black desktop that began after a driver update, or a shell that fails in Safe Mode with a normal driver set loaded. The sequence:
- Download the current driver for your exact card from the vendor’s site and leave the installer on the desktop.
- Boot to Safe Mode using the path above.
- Run Display Driver Uninstaller to remove the existing driver, choosing the clean-and-restart option for your vendor.
- Install the downloaded driver after the reboot, then test the desktop for a full session.
Do not stack a driver reinstall on top of three other changes. One change, one observation, recorded. The Diagnostic Workbench keeps those observations in order if you expect to hand the machine to someone else.
When to stop
Stop testing software the moment one of these is true.
- The screen is black in Safe Mode. Safe Mode strips the startup programs and third-party drivers, so a failure that follows you there is not a shell extension problem.
- There is no cursor at any point, or it freezes. The pointer is your proof that the display is working. Without it, the cable, the output, the panel or the firmware is the suspect, and monitor says no signal is the right guide.
- The motherboard logo never appears at power-on. If the firmware splash does not show, Windows has not started drawing anything yet, so no Windows repair can be the answer.
- The same driver recovery repeats at stock clocks with a clean install. Repeated recoveries point at hardware, power delivery or thermals rather than the driver, and the GPU driver crash guide covers that lane.
At that point the useful thing to carry to a repair desk is a short record: the Safe Mode result, whether a cursor was present, the driver log entry and its timestamp, and the update history around the date the problem started. That is worth more than a list of settings you changed.
Frequently asked questions
Why is my screen black but I can see and move the mouse cursor?
Does Ctrl+Shift+Esc work when the screen is black?
What does Win+Ctrl+Shift+B actually do?
Should I reinstall Windows for a black screen with a cursor?
Can a Windows update cause a black screen with a cursor?
Why is the screen still black in Safe Mode?
My cursor is frozen or missing. Is that the same fault?
How do I reset the desktop without rebooting?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 6 cited sources, listed below, each checked against the original page on the date above. Every procedure here comes from Microsoft’s own support and driver documentation read on 2026-11-16. The menu paths are quoted from those pages rather than from a machine I repaired, and no diagnostic was performed on a failing system for this page. Two behaviours drive the structure: a moving pointer and a black picture indicate a desktop-process failure, while an absent or frozen pointer indicates the display path. The timeout detection and recovery detail is from Microsoft’s WDDM driver documentation, which also states that some applications render black after a successful recovery. Where Microsoft does not publish a general rule, the article says so instead of inventing a threshold.
- Sources
- Microsoft Support: Troubleshooting blank screens in Windows accessed 2026-11-16
- Microsoft Learn: WDDM Support for Timeout Detection and Recovery (TDR) accessed 2026-11-16
- Microsoft Support: Windows Startup Settings (including Safe Mode) accessed 2026-11-16
- Microsoft Support: Recovery options in Windows accessed 2026-11-16
- Microsoft Support: How to uninstall a Windows update accessed 2026-11-16
- Wagnardsoft: Display Driver Uninstaller (DDU) accessed 2026-11-16
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.