A dual-monitor setup that worked perfectly yesterday and shows “no signal” today — right after Windows 11 installed updates overnight — is a classic post-update regression. The second monitor is powered, the cable is seated, but Windows insists the display does not exist: it is missing from Settings > System > Display, and even the Detect button finds nothing.
The pattern is consistent enough to diagnose confidently. Windows updates routinely touch the graphics driver, and the new driver sometimes fails the EDID handshake — the negotiation where the monitor introduces itself to the PC — or resets the stored multi-display topology. The monitor itself is rarely at fault. Work through the fixes below from simplest to most invasive, testing detection after each step.
Why this happens
- Graphics driver replaced by the update: Windows Update installs its own graphics driver build, which may handle multi-monitor enumeration worse than the manufacturer’s version it replaced.
- Reset display topology: the update can clear Windows’ stored record of your multi-display arrangement, and the re-detection handshake fails on the first attempt.
- EDID handshake failure: the negotiation over HDMI/DisplayPort where the monitor reports its capabilities can fail with the new driver, leaving Windows unaware the display exists.
- Changed projection mode: updates sometimes flip the projection mode to “PC screen only,” which deactivates the external output entirely.
- Power-management changes: new USB-C/Thunderbolt power policies can prevent docks and USB-C display outputs from initializing at boot.
- Firmware mismatch: the update may expect newer monitor firmware or GPU firmware behaviors for features like Display Stream Compression.
- Stale monitor driver entry: Windows caches a monitor driver entry (the .inf describing the display) that conflicts with the re-enumeration after the update.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Force re-detection and cycle projection modes
Start with the built-in controls. The Detect button and projection-mode cycling re-run the exact handshake the update disrupted, and they resolve a surprising number of cases in under a minute.
- With the monitor powered on and connected, open Settings > System > Display and click Detect next to the display diagram.
- Press Windows key + P and select Extend — if it was flipped to “PC screen only” by the update, this restores the second display immediately.
- Try Duplicate briefly, then switch back to Extend; the mode change forces a full re-enumeration.
- Disconnect and reconnect the cable at both ends while Windows is running, waiting 10 seconds between attempts.
- If the monitor appears, rearrange the displays in Settings to match your physical layout and click Apply — then restart once to confirm the topology survives a reboot.
Fix 2: Test the cable, port, and monitor in isolation
Before blaming software, prove the hardware chain works. Post-update timing changes can expose a marginal cable that previously squeaked by, and ten minutes of isolation testing prevents hours of driver tinkering.
- Try a different cable — preferably a known-good High Speed HDMI or certified DisplayPort cable.
- Test a different port on the laptop (HDMI vs. USB-C/Thunderbolt) and a different input on the monitor.
- Connect the monitor to another computer or a game console to confirm the panel and its input work.
- If you use a dock, connect the monitor directly to the laptop to rule out the dock.
- Should the monitor work everywhere except with your laptop after the update, the fault is definitively in the laptop’s driver stack — continue to Fix 3 with confidence, as our external-monitor guide confirms this isolation approach.
Fix 3: Roll back the graphics driver
When detection fails right after an update, the prime suspect is the graphics driver Windows installed. Rolling back restores the version that detected your monitor yesterday.
- Open Device Manager (Windows key + X > Device Manager) and expand Display adapters.
- Right-click your GPU (Intel, NVIDIA, or AMD), open Properties > Driver, and click Roll Back Driver if available.
- Restart with a full shutdown (Shift + Shut down) and check Settings > System > Display for the second monitor.
- If rollback is grayed out, choose Update driver > Search automatically — occasionally a newer driver already fixes the regression.
- To prevent Windows from re-breaking it, block automatic driver updates as detailed in our driver-crash guide .
Fix 4: Clean-install the manufacturer’s graphics driver
If rollback is unavailable or did not help, do a full clean install of the graphics driver from the GPU or laptop manufacturer. This replaces whatever hybrid state the update left behind.
- Download the latest graphics driver from Intel, NVIDIA, AMD, or your laptop manufacturer’s support page.
- For Intel integrated graphics, Intel’s driver detection tool identifies the correct package automatically.
- Run the installer and choose the Clean installation option to wipe old settings and profiles.
- Restart, reconnect the monitor, and press Windows key + P > Extend.
- Verify detection survives a cold boot — driver-level detection faults often reappear only after a full shutdown.
Fix 5: Remove the stale monitor entry and update its driver
Windows caches a driver entry for each monitor it has ever seen. After an update, a stale entry can block re-enumeration of the same display — Device Manager may even show it grayed out under hidden devices.
- In Device Manager, click View > Show hidden devices and expand Monitors.
- Right-click any grayed-out or duplicate entries for your external monitor and choose Uninstall device.
- Click Action > Scan for hardware changes and let Windows rediscover the display.
- If it appears as “Generic PnP Monitor,” right-click it and choose Update driver > Search automatically.
- For monitors with a manufacturer .inf (Dell, LG, and Samsung publish them), install it from the monitor maker’s support page for correct EDID handling.
Fix 6: Check USB-C/Thunderbolt and dock firmware
If your second monitor connects via USB-C, Thunderbolt, or a docking station, the display signal depends on firmware in the dock and the laptop’s Thunderbolt controller — both of which Windows updates can desynchronize.
- Check your laptop manufacturer’s support page for Thunderbolt controller firmware and dock firmware updates released after the Windows update.
- Install any pending firmware, with the dock connected and the charger plugged in.
- In Settings > Bluetooth & devices > USB, verify Thunderbolt/USB4 settings allow the dock.
- Test the monitor connected directly to the laptop’s USB-C port versus through the dock to isolate the failing link.
- On some laptops, the USB-C port’s DisplayPort alternate mode must be re-enabled in the BIOS after major updates — check for a “USB-C DP” or “Thunderbolt pre-boot” setting.
Fix 7: Uninstall the update or repair the display stack
When a specific update is the certain cause and driver fixes fail, remove the update — or repair Windows’ component store if the update damaged shared display components.
- Go to Settings > Windows Update > Update history > Uninstall updates and remove the update that preceded the failure.
- Verify the monitor is detected after the required restart.
- If removal is not possible, run
DISM /Online /Cleanup-Image /RestoreHealththensfc /scannowin an elevated Command Prompt to repair the display stack. - Check Microsoft’s support hub for known multi-monitor regressions in your build.
- As a final measure, an in-place upgrade using the Windows 11 installer (keeping files and apps) rebuilds the driver stack without a full reinstall.
Closing
A second monitor that vanishes after a Windows 11 update is a software-handshake problem in the overwhelming majority of cases: the update disturbed the graphics driver, the display topology, or the EDID negotiation, and the monitor is patiently waiting to be rediscovered. The Detect button, a cable swap, and a driver rollback resolve most cases in minutes; the deeper fixes handle docks, stale monitor entries, and stubborn updates. Once the display is back, lock the working graphics driver against automatic replacement — the next update will try the same trick again.
