Monitor Not Detected? Fix HDMI and USB-C Display Issues

Monitor showing no signal or not detected? Work through these fixes from quick cable checks to EDID overrides. Most issues are handshake or cable problems.

First, the 30-second fix: reseat the cable and check input

Half of the time, the monitor isn't actually broken — you've got a loose cable or the monitor is on the wrong input. Sounds dumb, but I've spent twenty minutes debugging a handshake issue when the real problem was the HDMI cable had wiggled halfway out of the port.

Unplug the cable from both the monitor and the computer. Wait five seconds. Plug it back in firmly — you should feel the connector click or seat fully.
Press the input button on the monitor (or use its OSD menu) and cycle through HDMI 1, HDMI 2, DisplayPort, USB-C. Monitors don't auto-detect inputs as well as you'd hope. My Dell U2720Q sometimes decides to sit on DisplayPort even when I've plugged in HDMI.
If you're on a laptop, make sure it's not in a clamshell mode that disables the external output. Some think they're being smart.

If that doesn't do it, move on. You've eliminated the dumb stuff.

5-minute fix: force the output and check for driver weirdness

What's actually happening here is often a display handshake failure. The GPU sends a signal, the monitor doesn't respond, and the OS gives up trying to detect it. Forcing a re-detection can kick things loose.

On Windows 10 or 11

Press Win + P and select "Duplicate" or "Extend". Wait a few seconds.
Right-click the desktop, go to Display settings, scroll to Multiple displays, and click "Detect".
If the monitor still doesn't show up, open Device Manager, expand Display adapters, right-click your GPU, and select "Update driver". Choose "Search automatically". A stale driver can cause detection failures, especially after a Windows update.

On macOS (especially with USB-C)

Macs are picky about USB-C connections. The reason step 3 works is that macOS caches display settings per port, and a glitch can leave it confused.

Unplug the monitor. Go to System Settings > Displays. Hold the Option key — the "Detect Displays" button appears. Click it, then plug the monitor back in.
If you're using a USB-C hub, skip it. Plug the monitor directly into the Mac's port. Cheap hubs cause more no-signal problems than anything else I see.

The 15+ minute fix: EDID override and hardware sanity checks

Still nothing? Now we're dealing with a deeper issue: your computer can't read the monitor's EDID. EDID is the little blob of data the monitor sends to the GPU that says "I'm a 27-inch 4K panel, these are my supported timings, and I can do 60Hz." When that handshake gets corrupted or lost, the GPU refuses to light the port.

Check the basics first

Try a different cable. Not just any cable — DisplayPort cables get marked as "DP 1.2" when they're really only 1.1. HDMI cables that claimed 18Gbps can fail to negotiate at 4K60. Borrow a known-good cable from another device.
Test the monitor with another computer (even a friend's laptop). If it works there, the problem is your machine's port or GPU. If it doesn't work anywhere, the monitor's input board might be toast.

Force an EDID update

If the monitor works elsewhere but not on your machine, you can override the EDID on Windows using CRU (Custom Resolution Utility). This tool gets into the nitty-gritty of what the GPU thinks the monitor supports.

Download CRU from monitortests.com. It's a portable exe, no install.
Run it. You'll see the active monitor in the top dropdown. If it lists "No monitor" or shows something generic, that's your smoking gun.
Click "Import" and select a monitor's data from the "Exports" folder if you have one. Otherwise, use "Add" to create a detailed resolution that matches your panel's native spec (find it in the manual or online).
Click OK, then run restart64.exe in the CRU folder. This restarts the graphics driver. Your screen will flicker.

CRU isn't for everyone. If you're not comfortable with resolution timings, skip it — you could end up with a worse mess. But when a monitor is physically fine and the OS just can't see it, this override often gets a stubborn panel to wake up.

The nuclear option: reseat the GPU or try another port

If you're on a desktop, power down, open the case, and reseat the graphics card. Dust in the PCIe slot can cause intermittent detection failures. Also try a different physical port on the GPU — I've seen one HDMI port die while the neighboring DisplayPort stays alive.

For laptops, check if the USB-C port supports video out at all. Some ports are data-only on budget machines. The USB-C port that looks the same as the Thunderbolt one might not carry a display signal.

When to stop and call it

If you've done the cable dance, forced detection on both OSes, tried a different cable and port, and run CRU with no luck, the monitor's EDID chip or input board is likely failing. Replacement boards on eBay run $30–60 for most models, but soldering is involved. If it's under warranty, claim it. If not, weigh that against a new monitor — a 27-inch 1080p panel runs under $150 these days.

One last thing: if the monitor shows "No Signal" but the power LED is blinking, that's the monitor telling you it's not receiving anything — cable or output problem, not the panel. If the LED stays solid but the screen stays black, the backlight or logic board is likely dead.