You plug the DisplayPort cable into your laptop’s dock or USB-C port, and the monitor reports ’no signal’ — while the same monitor works fine over HDMI. Or the monitor worked yesterday and shows nothing today after a Windows update. DisplayPort failures are maddening because the standard is technically superior to HDMI but far pickier about the handshake between devices.

DisplayPort uses a process called link training, where the GPU and monitor negotiate lane speeds before any image appears. When that negotiation fails — bad cable, confused driver, monitor stuck in deep sleep — you get a black screen with no useful error. Windows may not even know a monitor is attached.

These fixes attack the handshake from every angle: cable, monitor settings, driver, and Windows display configuration. Most DisplayPort problems surrender to the first four.

DisplayPort’s link training is sensitive to timing in a way HDMI is not: the GPU and monitor must complete their negotiation within a short window, and anything slow — a drowsy monitor, a marginal cable, a busy driver — can blow the window. That is why unplug-replug rituals sometimes work; you are just giving the handshake a second chance. The permanent fixes below remove the need for the ritual.

Why this happens

  • Substandard or damaged DisplayPort cable: Marginal cables fail link training at high bandwidth; the monitor never gets a signal to display.
  • Display driver link-training failure: A buggy or corrupted GPU driver botches the negotiation handshake with the monitor.
  • Monitor stuck in deep sleep: Some monitors sleep their DisplayPort input so deeply that the GPU gives up before the monitor wakes.
  • Wrong DisplayPort version selected on the monitor: A monitor set to DP 1.1 while the GPU offers 1.4 can fail negotiation.
  • Dock or adapter incompatibility: USB-C docks and DP-to-HDMI adapters vary wildly in quality; a failing dock breaks the chain.
  • Windows display configuration corruption: A corrupted multi-monitor profile can leave the DisplayPort output disabled or misrouted.
  • GPU output disabled in firmware: Some laptops disable the dGPU-linked DisplayPort output in certain power or MUX modes.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Test with a certified cable, direct connection

Cable quality is the number one DisplayPort fix. Bypass every adapter and dock for this test.

  1. Connect the monitor directly to the laptop with a VESA-certified DisplayPort cable — no dock, no adapter.
  2. Ensure the cable is rated for your resolution and refresh rate (HBR3 for 4K 144Hz).
  3. Try a different DisplayPort input on the monitor if it has several.
  4. If the direct connection works, your dock or old cable was the failure.

Fix 2: Power-cycle the monitor out of deep sleep

Monitors stuck in DisplayPort deep sleep miss the handshake window. A full power cycle wakes the input properly.

  1. Unplug the monitor’s power cable — not just the power button — for 60 seconds.
  2. Reconnect power, turn the monitor on, and set its input to DisplayPort manually.
  3. On the laptop, press Win + Ctrl + Shift + B to restart the graphics driver.
  4. Check whether the monitor now receives a signal.

Fix 3: Check the monitor’s DisplayPort version setting

A version mismatch between the monitor’s setting and the GPU’s offer kills negotiation silently.

  1. Open the monitor’s on-screen menu and find the DisplayPort version option.
  2. Set it to 1.2 first — the most compatible modern setting — and test.
  3. If that works, try 1.4 for full bandwidth; leave it at whichever is stable.
  4. Disable any DisplayPort deep sleep option in the monitor menu while you are there.

Fix 4: Reinstall the display driver

The driver conducts link training. A fresh driver conducts it correctly.

  1. Open Device Manager > Display adapters, right-click the GPU, and uninstall with driver deletion.
  2. Restart and let Windows reinstall, then test DisplayPort.
  3. For persistent issues, install the latest driver from NVIDIA , AMD , or Intel as appropriate.
  4. Retest at your target resolution and refresh rate.

Fix 5: Force detection in Windows display settings

Windows sometimes needs a manual nudge to acknowledge the DisplayPort monitor.

  1. Open Settings > System > Display and click Detect next to the display diagram.
  2. Press Win + P and cycle to Extend — the output may be routed to ‘PC screen only’.
  3. Scroll to Advanced display and confirm the monitor appears with the right refresh rate.
  4. If the monitor appears here but shows no image, the issue is link training, not detection — return to the cable fix. Related detection problems are covered in the second monitor guide .

Fix 6: Update the dock firmware or bypass the dock

Docks are computers in their own right, and their firmware governs the DisplayPort signal they pass through.

  1. Check your dock manufacturer’s support page for a firmware update utility.
  2. Install any available dock firmware update and retest.
  3. If no update exists, test the monitor connected directly to the laptop.
  4. A dock that cannot pass DisplayPort after a firmware update needs replacement — this is common with older USB-C docks. Thunderbolt docks add their own failure modes, covered in the Thunderbolt guide .

Fix 7: Lower the resolution and refresh rate as a test

Reducing bandwidth demands can complete link training that fails at full spec, proving the cable or port is marginal.

  1. In Settings > System > Display > Advanced display, drop to 1080p at 60Hz.
  2. If the monitor springs to life, the cable or port cannot sustain your target bandwidth.
  3. Replace the cable with a certified higher-spec one before restoring full resolution.
  4. If it still fails at 1080p60, the port, GPU output, or monitor input is likely faulty.

Fix 8: Test the monitor on another computer

Cross-testing the monitor isolates the laptop from the display in one move and ends all guessing about which side is at fault.

  1. Connect the monitor to a different computer with the same cable.
  2. If it works there, your laptop’s port, driver, or settings are the problem — focus there.
  3. If it fails there too, the monitor’s DisplayPort input or the cable is at fault.
  4. Swap the cable during the same test to separate the monitor from the cable.

Closing

DisplayPort is a negotiation, and ’no signal’ means the negotiation failed — usually the cable, the driver’s handshake, or a sleeping monitor. Test direct with a certified cable, wake the monitor fully, and refresh the driver. The standard works beautifully once every link in the chain is actually capable of the bandwidth you are asking for.

Frequently asked questions

Why does my monitor say 'no signal' on DisplayPort but works on HDMI?
The DisplayPort link training is failing — the GPU and monitor cannot agree on a connection. This is usually a cable quality issue, a driver problem, or the monitor’s DisplayPort version setting. HDMI uses a simpler handshake, which is why it works while DisplayPort fails.
Can a Windows 11 update break DisplayPort?
Yes. Display driver updates bundled with Windows updates can break DisplayPort link training, especially on multi-monitor setups. Rolling back the display driver or installing the manufacturer’s version restores the handshake. Use Win plus Ctrl plus Shift plus B to restart the graphics driver first; it is instant and sometimes enough.
Why does DisplayPort work after unplugging and replugging?
Replugging forces a fresh link-training handshake, which can succeed where the boot-time negotiation failed. If you must do this every boot, the underlying cause is usually the driver, the cable, or the monitor’s DisplayPort deep-sleep behavior. Disable the monitor’s deep-sleep option in its on-screen menu to stop the recurring handshake failure.
Does cable quality matter for DisplayPort?
Enormously. DisplayPort pushes high bandwidth, and marginal cables fail link training at higher resolutions and refresh rates. A VESA-certified cable rated for your resolution and refresh rate fixes a large share of ’no signal’ problems instantly. For 4K at high refresh rates, insist on a certified HBR3-rated cable, not just any DisplayPort cable.