Windows

Second monitor not detected on Windows 11

A second monitor not showing up on Windows 11 24H2/25H2? Work the layers: Win+P and Detect, the cable/input/port, the graphics driver (roll back or reinstall), and the difference between 'not detected at all' and 'detected but no signal'.

Evidence from the screen

Reference images and diagrams. Click any image to view full resolution.

Windows 11 Settings System Display page showing Scale 150%, Display resolution 3840x2160, and the expanded Multiple displays section with the Detect button used to re-scan for a connected display. — Settings → System → Display → Multiple displays → Detect re-scans for a connected display. First-party screenshot (Windows 11 25H2).

Device Manager with a display adapter's Properties open on the Driver tab, showing the Roll Back Driver button used to return to the pre-update driver version (greyed out when no previous driver is stored). — Device Manager → adapter → Driver tab → Roll Back Driver returns to the pre-update driver. First-party screenshot (Windows 11 25H2).

Problem summary

I'm here because Windows 11 won't detect my second monitor — it's not in Display settings, or it's plugged in but black. The key split to make first: is the display not detected at all (Windows doesn't see it) or detected but showing no signal (Windows sees it, the panel is on the wrong input)? That decides where to look. The layered fix: press Win+P and pick Extend, use Settings → System → Display → Detect, then check the cable/port/input source, then the graphics driver (roll back if it broke after an update, or reinstall it). If the monitor hangs off a dock or hub, the dock is its own variable — see USB-C dock not driving a monitor. This is the Windows companion to the device-agnostic dual monitors not working and monitor refresh rate wrong.

Operator snapshotEvidence first

First proof

Press Win+P and choose Extend (or Duplicate).

Screen to open

Settings → System → Display → Multiple displays → Detect | Win+Ctrl+Shift+B

Expected signal

The second display lights up — it was just set to 'PC screen only'.

Stop boundary

Don't assume a fixed monitor count over a dock — that depends on the hardware.

Layer path

1A second display fails in one of two distinct ways that need different fixes: Windows doesn't detect it at all (nothing in Display settings even after Detect — a connection/driver problem), or Windows detects it but the panel shows no signal (it's on the wrong input — a monitor-side problem). Naming which one you have is the whole game.

2Detection runs through a stack: the physical cable and port, whether the connection type carries video, the graphics driver, and Windows' display arrangement. Win+P and Detect handle the arrangement layer in seconds; the cable/port and driver layers are where most real failures live.

3A dock, hub, or adapter is an extra variable that masquerades as a monitor problem — Microsoft explicitly flags docks/adapters as a source of detection conflicts. Proving the monitor works plugged directly into the PC separates a display fault from a dock fault before you chase the wrong layer.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Try the instant fixes

Check: Press Win+P → Extend, then Settings → Display → Detect. If the screen was working, press Win+Ctrl+Shift+B.

Expected result: The display lights up or Windows re-detects it.

If not: If nothing, determine whether it appears in settings at all.

Classify: not-detected vs no-signal

Check: Check whether the monitor appears in Display settings. Appears but black = wrong input (fix on the monitor). Doesn't appear = connection/driver.

Expected result: You know which layer to work.

If not: If it's a monitor-input issue, set the correct input and you're done.

Work the cable, port, and dock

Check: Reseat and swap the cable, try a different PC video port, and if a dock/hub is involved, connect the monitor directly to the PC.

Expected result: You confirm whether the cable/port/dock is at fault.

If not: If direct-connect works, troubleshoot the dock; if it still fails, it's the driver.

Fix the graphics driver

Check: In Device Manager, roll back the GPU driver if this started after an update; otherwise uninstall (remove driver) and reinstall the current vendor driver. Reboot.

Expected result: The display is detected with a healthy driver.

If not: If still not detected, retest the cable/port and consider a GPU/port hardware fault.

Set the right mode

Check: With the display detected, set its native resolution and refresh rate (Advanced display). Use a higher-spec cable if high-refresh modes flicker or drop.

Expected result: The second display runs at its correct resolution/refresh, stable.

If not: If high modes still fail, the cable or dock bandwidth is the limit.

Safe stop: Don't assume a fixed monitor count over a dock — that depends on the hardware.

Decision tree

If: Monitor doesn't appear in Display settings even after Detect.

Then: Windows isn't seeing it — connection or driver.

Action: Swap cable/port, connect directly (bypass dock), then roll back/reinstall the GPU driver.

If: Monitor appears in settings but the panel is black / 'no signal'.

Then: Detected but on the wrong input.

Action: Use the monitor's own menu to select the correct input (HDMI/DisplayPort/USB-C) and check its port-version setting.

If: Worked until a Windows/GPU update, then stopped.

Then: Graphics-driver regression.

Action: Device Manager → Display adapters → Roll Back Driver; if greyed out, uninstall (remove driver) + reinstall the vendor driver.

If: Only fails at high resolution/refresh, or flickers.

Then: Bandwidth/cable or refresh-rate limit.

Action: Set the native resolution/refresh in Advanced display; use a higher-spec cable; reduce refresh to test.

If: Works direct but not through the dock.

Then: It's a dock problem, not the monitor.

Action: Go to the USB-C dock page: power-cycle, approve Thunderbolt, update dock firmware/DisplayLink driver.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
Nothing appears after Detect.	Cable/port tested; connection type; whether direct-connect works.	Connection or driver.	Swap cable/port, connect direct, roll back/reinstall the GPU driver.
Appears in settings but screen is black.	The monitor's selected input source; its port-version setting.	Wrong monitor input.	Select the correct input on the monitor's menu.
Stopped after a Windows/GPU update.	Reliability Monitor timeline; driver version in Device Manager.	Driver regression.	Roll back the GPU driver; reinstall if roll-back is unavailable.
Flicker or dropout at high refresh/resolution.	Cable spec; whether lowering refresh stabilizes it.	Bandwidth/cable limit.	Use a higher-spec cable; set native resolution/refresh.

Reference

Commands and settings paths

Re-scan for the display and restart the graphics driver

Settings → System → Display → Multiple displays → Detect | Win+Ctrl+Shift+B

Where: On the PC (no terminal needed)

Expected: Detect forces Windows to re-enumerate displays; Win+Ctrl+Shift+B resets the graphics driver and often restores a dropped signal.

Failure means: If Detect finds nothing and the reset doesn't help, the cause is below Windows (cable/port/driver).

Safe next step: Move to cable/port swaps and the driver steps.

Roll back or reinstall the GPU driver

Device Manager → Display adapters → (GPU) → Properties → Driver → Roll Back Driver; or Uninstall device (remove driver) → restart → reinstall vendor driver

Where: Device Manager (devmgmt.msc)

Expected: Returns the GPU to the pre-update driver, or cleanly reinstalls the current one.

Failure means: If roll-back is greyed out, there's no stored previous driver — uninstall and reinstall instead.

Safe next step: Reboot after; install the vendor's current driver if Windows' is the regression.

Set the native resolution and refresh rate

Settings → System → Display → (display) → Resolution; Advanced display → Refresh rate

Where: On the PC

Expected: Forces the correct resolution/refresh so a mismatch isn't causing a black or flickering screen.

Failure means: If the native refresh isn't selectable, the cable/dock bandwidth or driver is limiting it.

Safe next step: Use a higher-spec cable or a direct connection to reach the native mode.

Hardware boundary

Hardware and platform boundary

Change only when

Replace a marginal or wrong-spec video cable when high-refresh/4K modes flicker or drop — the cheapest fix for bandwidth-limited dropouts.
Add a proper dock or a GPU with more outputs if you genuinely need more displays than the PC's ports provide.

Evidence that matters

A video-capable port and a cable rated for your resolution/refresh.
A current GPU driver from the vendor.
Knowing whether the monitor is connected directly or through a dock/adapter.

Evidence that does not matter

Vendor 'works with Windows 11' badges — what matters is a video-capable connection and a current driver, which you can verify directly.
Exact 'this GPU drives N monitors' marketing — confirm against the actual hardware, not the box.

Avoid

Assuming it's the monitor before ruling out the dock with a direct connection.
Reinstalling the GPU driver before checking the monitor's input source.
Forcing a refresh rate the cable/dock can't carry.
Treating DDU (a third-party tool) as Microsoft's recommended reinstall path.

Related tool/checklist

Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.

USB-C dock monitor setup planner

Last reviewed

2026-06-02 · Reviewed by HomeTechOps. Reviewed against Microsoft's multiple-monitors, troubleshoot-external-monitor, refresh-rate, and Device Manager driver pages; splits 'not detected' from 'detected but no signal', leads with Win+P/Detect and the Win+Ctrl+Shift+B graphics-driver reset, isolates docks with a direct connection, and treats DDU as an optional third-party tool rather than the Microsoft path.

Sources/assumptions

Assumes Windows 11 24H2/25H2 with a directly-connected external display; the Win+P modes, Detect/Identify paths, restart-graphics-driver shortcut, and driver roll-back/reinstall steps follow Microsoft Support current to mid-2026.
Display Driver Uninstaller (DDU) is noted as an optional third-party clean-reinstall tool, not a Microsoft tool; the documented clean reinstall is the Device Manager uninstall-with-remove-driver flow.
Per the no-fake-compatibility rule, exact monitor-count limits over a given GPU/dock aren't asserted — those depend on the hardware and are verified, not guessed.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Microsoft Support: How to use multiple monitors in WindowsUsed for the four Win+P modes and the Settings → System → Display → Multiple displays → Detect / Identify paths.Microsoft Support: Troubleshoot external monitor connections in WindowsUsed for display-detection order, one-monitor isolation, driver checks, and safer escalation.Microsoft Support: Change the refresh rate on your monitor in WindowsUsed for setting refresh rate (Settings → System → Display → Advanced display) when a detected monitor shows the wrong rate/resolution.Microsoft Support: Update drivers through Device Manager in WindowsUsed for the Roll Back Driver and uninstall/reinstall steps (network and display adapters) after an update breaks a device.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Avoid unsafe electrical or data-loss steps.
4. Stop when the evidence says the risk moved.

FAQ

What's the very first thing to try?

Press Win+P and choose Extend (or Duplicate) — sometimes the second display is simply set to 'PC screen only.' Then go to Settings → System → Display → Multiple displays → Detect to make Windows re-scan. If the screen was working and just went black, press Win+Ctrl+Shift+B to restart the graphics driver. These take seconds and fix a surprising share of cases.

How do I tell 'not detected' from 'no signal'?

If the monitor doesn't appear in Settings → Display even after Detect, Windows isn't seeing it — suspect the cable/port, the connection type, or the driver. If the monitor appears in Settings but the panel says 'no signal' or is black, Windows sees it but the monitor is on the wrong input — use the monitor's own menu to select the right source (HDMI/DisplayPort/USB-C) and check its port-version setting. Two different problems, two different fixes.

How do I check the cable and port?

Reseat the cable at both ends; try a different cable and a different video port on the PC (HDMI, DisplayPort, USB-C); and test the monitor on another device to prove the panel works. If you're going through a dock, dongle, or adapter, connect the monitor directly to the PC to rule the dock out — Microsoft specifically calls out docks/adapters as a source of detection conflicts.

It broke after a Windows update — driver?

Likely. Open Device Manager → Display adapters, right-click your GPU → Properties → Driver → Roll Back Driver to return to the version from before the update. If roll-back is greyed out, Uninstall device (tick 'attempt to remove the driver'), restart, and let Windows reinstall — or install the current driver from the GPU vendor. A clean reinstall with the third-party tool DDU is an option some prefer, but Microsoft's documented path is the Device Manager flow.

The monitor's detected but the resolution or refresh rate is wrong.

Set it explicitly: Settings → System → Display → choose the display → set the resolution, and under Advanced display set the refresh rate to the panel's native value. A wrong refresh rate can also cause flicker or a dropped signal, especially through a dock or a marginal cable. If it only happens at high refresh/resolution, the cable or the dock's bandwidth is often the limit.