Monitor Not Detected? Fix HDMI, DisplayPort & Cable Issues

1. Faulty or Loose Cable (This is the culprit 90% of the time)

I've seen it a thousand times – someone swaps a monitor, moves a desk, or even just bumps the tower, and suddenly the screen goes black. Nine times out of ten, it's the cable. HDMI and DisplayPort cables are finicky. They wiggle loose just enough to lose the signal but still look plugged in. Don't waste time troubleshooting anything else until you've done this:

1. Completely unplug the cable from both the monitor and the PC or laptop.
2. Inspect the connector and the port for bent pins. DisplayPort is especially bad for pin 20 bending.
3. Plug it back in firmly. You should feel a solid click, especially with DisplayPort.
4. If you're using an adapter (HDMI to DisplayPort, USB-C to HDMI), remove it and try a direct connection. Adapters cause weird handshake failures – skip them if you can.
5. Try a different cable. Not just a different port – a different cable. I keep a cheap $10 HDMI cable in my bag specifically for this test.

Still no picture? Reboot the PC with the monitor connected and powered on. The GPU does a handshake with the monitor during boot. If the cable was disconnected during the handshake, the monitor might stay dark until the next restart.

2. Wrong Input Source Selected

This one makes me groan every time. The monitor is on, the cable is good, but you've got the monitor set to HDMI 1 and the PC is plugged into HDMI 2. Or you're using DisplayPort and the monitor is set to HDMI. It's not your fault – monitor menus are terrible. Here's the fix:

• Look at the monitor's physical buttons – usually on the bottom edge or back. Press the one labeled 'Input' or 'Source'. Cycle through HDMI 1, HDMI 2, DisplayPort, USB-C, VGA – whatever it lists. Watch the screen as you do it.
• If the monitor has an on-screen display (OSD), press the menu button, find 'Input Source' or 'Signal Source', and pick the one you're actually using.
• Pro tip: Most monitors let you rename inputs. If you have multiple devices, rename them on the monitor. Saves you this headache later.
• If you're using a KVM switch or docking station, bypass it temporarily. Plug the monitor directly into the PC. If it works, the KVM or dock is the problem, not the monitor.

3. GPU Driver or Power Management Interference

If the cable is solid and the input is correct, the problem is almost always software. Modern GPUs from NVIDIA, AMD, and Intel have aggressive power saving features. They'll turn off the video output to a monitor that's been idle for a while, and sometimes they forget to turn it back on when you wake the PC. I've also seen driver updates break detection entirely.

Try these steps in order:

1. Press Windows key + Ctrl + Shift + B on your keyboard. This resets the graphics driver without a full restart. If you hear a beep and the screen flickers, the driver came back. If the monitor stays black, move on.
2. Open Device Manager (right-click Start > Device Manager). Expand 'Display adapters'. Right-click your GPU and select 'Disable device'. Wait 10 seconds. Right-click it again and select 'Enable device'. This forces a full driver re-initialization.
3. Update or roll back the driver. If the problem started after a recent driver update, roll it back. If it's been happening for a while, download the latest driver from the GPU manufacturer's website (not Windows Update) and do a clean install. For NVIDIA, use the 'Custom (Advanced)' option and check 'Perform a clean installation'.
4. Check power management settings. Go to Control Panel > Power Options > Change plan settings > Change advanced power settings. Expand 'PCI Express' > 'Link State Power Management'. Set it to 'Off'. This stops the GPU from going into a low-power state that sometimes kills the monitor signal. Reboot after.

I've had a few stubborn cases where nothing above worked. On those, I booted into Safe Mode (press F8 or Shift + Restart during boot), uninstalled the GPU driver completely with DDU (Display Driver Uninstaller) in Safe Mode, then reinstalled from scratch. That's the nuclear option, but it works when the driver is completely corrupted.

Quick-Reference Summary Table