Before you start

Confirm the monitor itself is alive: does it show a logo, a menu, or a "no signal" message when you press its buttons? A screen that shows nothing at all when powered — no backlight, no on-screen menu — is a different problem from one that is on and reporting no signal. Everything below assumes the monitor powers up and is telling you it cannot see a source.

Which socket you plugged into

On a desktop with a separate graphics card, this is the classic and it catches experienced people.

The machine has display sockets in two places: on the graphics card, low down at the back, and on the motherboard's own panel, higher up with the USB and network ports. When a graphics card is fitted, the motherboard sockets are frequently disabled entirely. A monitor plugged into one gets nothing, and the computer genuinely cannot see it.

The tell is that the first monitor works and the second does not, and the two are plugged into different areas of the back panel. Both displays should normally go to the graphics card.

Where the signal has to get through The display signal passes from the graphics card through a port, along a cable, possibly through a dock or adapter, into the monitor and finally to the input the monitor has selected. Any one of those five stages failing produces the same no signal result. GPU port not motherboard Cable rated high enough Dock? may allow one Monitor powered on Input selected All five say "no signal" in exactly the same words. The message tells you the monitor is fine and something upstream is not. Nothing more. Test by substitution, one stage at a time. Swap the working monitor onto the suspect cable and port. That isolates it in one move.
Five places the signal can stop, one identical error message.

The monitor's own input selection

Monitors with several sockets do not always find the live one on their own. A screen with two HDMI inputs and a DisplayPort will happily sit on HDMI 1 showing "no signal" while your cable is in HDMI 2.

This is worth doing early because it costs nothing and it is the answer often enough to justify the thirty seconds.

Cables that work at one resolution and not another

A cable is not simply a connector on each end. Both HDMI and DisplayPort have gone through generations with substantially different bandwidth, and a cable built for an older one physically fits a newer socket while being unable to carry the signal.

The result is confusing because it is conditional:

Two practical moves: try a different cable, and try setting the monitor to a lower resolution or refresh rate to see whether it appears. If it does, the cable or the port is the limit rather than the monitor.

Length matters too. Passive HDMI and DisplayPort cables lose signal integrity over distance, and a long cheap cable is a common cause of a display that works at the desk and fails when moved.

Docks, adapters and USB-C

This is the modern cause, and it is the one most likely to be missed because everything looks connected.

When a monitor is connected through a docking station, a USB-C hub or an adapter, several extra conditions apply.

The decisive test: plug the second monitor directly into the computer, bypassing the dock entirely. If it appears, the dock or its configuration is the problem and the monitor is fine.

Making the computer look again

Sometimes the hardware is fine and the operating system simply has not noticed.

That last distinction matters. "Not detected" and "detected but showing nothing" are different faults, and the display settings panel tells you which one you have.

Drivers, and what changed

If the second monitor worked yesterday and does not today, something changed. Usually one of these:

Installing the graphics driver from the graphics card manufacturer's own site, rather than relying on the version the operating system supplies, resolves a meaningful share of these. Where a recent update caused it, rolling back to the previous driver is a legitimate test rather than a superstition.

Laptop-specific causes

What to check, in order

  1. Does the monitor show its own menu? If yes, it is alive and the problem is upstream.
  2. Cycle the monitor's input manually to the socket you actually used.
  3. On a desktop, confirm both cables go to the graphics card, not the motherboard panel.
  4. Bypass any dock or adapter and connect straight to the computer.
  5. Swap the working monitor onto the suspect cable and port. This isolates cable and port from monitor in one move.
  6. Try a different cable, preferably a shorter one rated for your resolution.
  7. Press Detect in display settings, and check the projection mode with the Windows key and P.
  8. Look at whether the monitor is listed in display settings even while blank — detected and misconfigured is a different problem.
  9. Lower the resolution or refresh rate to test whether bandwidth is the limit.
  10. Update the graphics driver from the manufacturer's site, and the dock firmware if a dock is involved.
  11. Check the manual for how many external displays your specific laptop supports, and which ports carry video.
The short version

Five things sit between the graphics chip and the picture, and all five report the same "no signal". Work through them by substitution rather than guessing. On a desktop, the classic is a cable in the motherboard's display socket instead of the graphics card's — those motherboard ports are often disabled when a card is fitted. On a laptop, the modern classic is a USB-C port that carries data and power but not video, or a dock that can only drive one external display on your particular machine. Cycle the monitor's input manually rather than trusting auto-detect, and bypass any dock as an early test. And separate the two states: a monitor that is not listed in display settings is a connection problem, while one that is listed but blank is a configuration problem.