Have to Unplug and Replug the DisplayPort Cable Every Boot? Boot Handshake, Hot-Plug Detection & Link Retraining Diagnosis Guide

Key Summary
If the picture returns only when the DisplayPort cable is unplugged and plugged back in at every cold boot, and waiting does not help and restarting does not help, the fault sits in the boot handshake: the hot-plug detection or link training window at power-on was missed. Replugging re-triggers that window.
Four Ways a Picture Can Come Back — and They Point at Four Different Layers
A monitor that shows nothing at boot can come back in four different ways, and each way points at a different layer. Keeping them apart is the whole diagnosis, because a fix that works for one shape does nothing for another.
- Waiting works. The picture arrives on its own after a delay. The system was slow to settle, and the picture was late rather than absent.
- Restarting works. Pressing the restart button brings the picture back. The warm restart path succeeds where the cold boot path failed.
- Reordering works. Switching the monitor on before the PC, every time, brings the picture back. The power-on order was the problem.
- Only replugging works. Waiting does not bring the picture back. Restarting does not bring it back. The order is already correct. Only unplugging the DisplayPort cable and plugging it back in produces a picture — and this happens at every cold boot.
This article covers only the fourth shape. The monitor was already switched on, the order was correct, waiting does not help, restarting does not help, and the picture returns the moment the cable is replugged. If any of the first three shapes describes the machine, the fault is elsewhere, and the comparisons in this guide will show which one.
The shape is specific, and that specificity is useful. Four conditions, each checked, each ruling something out: the monitor was on early, the order was right, waiting failed, restarting failed. What is left is a single variable — the replug itself, and what the replug triggers.
What a Replug Actually Does
DisplayPort is a packet-based interface. Before any picture appears, the graphics card and the monitor have to complete a handshake. The card reads the monitor's capability registers over the auxiliary side channel, then trains the link: clock recovery, equalisation, and lane alignment, in sequence. If any step in that sequence fails, the monitor has no usable picture.
Two parts of that handshake matter here.
Hot-plug detection (HPD). The monitor asserts a hot-plug detection signal to tell the graphics card that a display is present. At cold boot, there is a window in which the card looks for that signal. If the monitor is not ready when the window opens — for example because it is still in a deep sleep state — the card can miss the signal. No signal, no enumeration, no picture. Unplugging and replugging the cable asserts the hot-plug signal again, at a moment when the monitor is ready, and the card enumerates the display.
Link training. Once the card knows a display is present, it has to train the link before sending pixels. Training can fail at cold boot — clock recovery, equalisation, or lane alignment can each break the sequence. Firmware typically retries only a limited number of times at boot; after the driver takes over, retries are more numerous. A replug triggers a fresh round of link training, and the fresh attempt can succeed where the cold-boot attempt failed.
Replugging also forces the card to re-read the monitor's EDID over the auxiliary channel, which is the data the card uses to learn the monitor's supported resolutions and timings. If that read failed at boot, the replug gives it another chance.
None of this means the connector is loose. That is a common misreading, and it is worth stating plainly: a picture returning after a replug does not mean the connector is loose. The replug may simply have triggered re-enumeration or link retraining. A loose connector is one possible cause among several, and it is tested by evidence — whether the fault follows the cable or the port — not by the fact that a replug helped.
The Five Layers
Layer 1: Hot-Plug Detection at Boot
The monitor may not assert the hot-plug detection signal at the moment the card is looking for it, or the card may miss the window. Deep Sleep can leave the monitor unready at the exact moment of boot. The replug re-asserts the signal when the monitor is ready, and the card enumerates the display. This layer is about timing, not about damage: the monitor and the card can both be healthy, and the window can still be missed.
Layer 2: Link Training
Cold-start link training can fail at any of its steps — clock recovery, equalisation, or lane alignment. Firmware retries at boot are limited in number, while retries after the driver takes over are more numerous. A replug triggers fresh link training. If the fresh attempt succeeds, the picture appears. This layer explains why the fault is specific to cold boot: the same link can train successfully when the driver is already running, and fail when training has to happen during the early boot window.
Layer 3: EDID and DDC
At boot, the card reads the monitor's EDID over the auxiliary channel. If that read fails, the card has no supported modes to offer and no picture to send. The replug triggers a fresh EDID read. This layer is easy to overlook because EDID is invisible when it works; it only becomes visible when it fails.
Layer 4: Monitor Wake and Power Behaviour
The monitor may not be ready when the card looks for it. Deep Sleep is the most common form of this: the monitor is in a low-power state and takes too long to wake. Automatic input detection can also be part of the problem — the monitor may be waiting on the wrong input while the card is trying to handshake on the DisplayPort input. How a monitor's firmware handles hot-plug detection after being fully powered off is a property of that monitor model, and it varies between models.
Layer 5: Cable, Port and Driver
The cable, the connector, and the DisplayPort output port are still a real layer, as is the driver. A faulty cable or a faulty port can break the handshake, and an individual driver version can introduce a wave of DisplayPort no-signal reports — one such event was reported with a specific NVIDIA driver version, and users recovered by removing the driver in safe mode and rolling back. That was an individual driver version event, not a general rule, and driver comparisons should always be made against the current official release rather than a fixed version number.
A related layer is pin 20 power backfeed, where power flows back through the cable's pin 20. That is a separate power behaviour question, not the handshake question covered here.
Four-Way Comparison: Which Shape Is This?
Before changing anything, confirm the shape with the four-way comparison. Each answer rules something out.
| What brings the picture back? | Shape | Where to go |
|---|---|---|
| Waiting — the picture arrives on its own after a delay | Delay | The picture was late, not absent; a different diagnosis |
| Restarting — pressing restart brings the picture back | Warm restart succeeds | The warm restart path works where the cold boot path fails |
| Reordering — switching the monitor on before the PC brings the picture back every time; restarting and replugging both work | Power-on order | The order was the problem |
| Only replugging — waiting and restarting both fail, the order is already correct | Boot handshake | This article: hot-plug detection or link training window missed at cold boot |
The comparison is the diagnosis. If reordering the power-on sequence fixes it, the fault was the order, and this article's handshake layers do not apply. If restarting fixes it, the fault sits on the difference between the cold boot path and the warm restart path. If waiting fixes it, the picture was delayed rather than absent. Only when all three fail and the replug succeeds does the fault narrow to the handshake window that the replug re-triggers.
One published user report matches this shape closely: the user switched the PC and the monitor off, switched them back on, found no signal, and found that only unplugging and plugging the cable again restored the connection — while leaving the monitor in standby avoided the problem entirely, and switching the monitor on first did not help. That is a user report, not an official conclusion, and it is cited as one user's experience. The replies to that report pointed at monitor firmware and Deep Sleep — at how the monitor handles DisplayPort hot-plug detection after being fully powered off — and suggested checking for a monitor firmware update and a Deep Sleep setting. That suggestion is worth testing per model, not assuming for every monitor.
Seven-Step Diagnosis
- Record the baseline. Note whether the monitor was switched on before the PC, the exact power-on order, how long was waited, what restarting did, what replugging did, and whether this happens at every cold boot. Do not judge anything until all six facts are recorded. A missing fact is a missing comparison.
- Run the order comparison. Try switching the monitor on before the PC, and then the PC before the monitor. If reversing the order makes the picture appear reliably, the fault is the power-on order, and the diagnosis belongs with the order question, not this one. Only continue if the fault happens with the correct order.
- Run the DisplayPort versus HDMI comparison. Connect the same monitor by HDMI. If HDMI works every time and DisplayPort needs a replug every time, the fault is in the DisplayPort handshake layer — hot-plug detection or link training. If HDMI also fails, the problem is broader than DisplayPort, and it belongs with general no-signal diagnosis. HDMI working does not mean DisplayPort should work: DisplayPort is packet-based and needs link training, while HDMI does not, so the two interfaces are not interchangeable evidence.
- Change the monitor settings, one at a time. Switch Deep Sleep off, fix the input source to DisplayPort instead of automatic detection, and switch automatic input switching off. Change only one setting at a time, and test a cold boot after each change. Changing three settings at once and seeing a fix proves nothing about which one mattered.
- Change the cable and the port, one at a time. Try a different DisplayPort cable, and try a different DisplayPort output on the card. Watch whether the fault follows the cable, follows the port, or stays with the monitor. Connect directly, without an adaptor — adaptor layers are a separate question. The fault following the cable is evidence about the cable; a single successful replug is not.
- Test Fast Startup and a clean driver, one at a time. Switch Fast Startup off and test a cold boot, because Fast Startup makes cold boot and warm restart take different paths. Then do a clean driver installation, using the current official release. Change only one thing at a time.
- Run the graphics-stack and monitor-power comparisons, then prepare for inspection. Press Win+Ctrl+Shift+B to restart the graphics stack: if the picture appears, the fault points at the graphics stack layer; if it does not, the fault points at the boot handshake layer. This is a comparison method, not a repair. Alternatively, power the monitor fully off and on again: if the picture appears, the fault points at the monitor wake layer. Bring the monitor model and firmware version, the cable, the power-on order, how long was waited, the restart result, the replug result, and the DisplayPort versus HDMI comparison result.
The DisplayPort Versus HDMI Comparison Is Evidence, Not a Workaround
Switching to HDMI permanently is not a fix for a DisplayPort handshake fault. It is a comparison that proves the fault is specific to DisplayPort. The comparison works precisely because the two interfaces handshake differently: DisplayPort is packet-based and requires link training, while HDMI does not. A monitor that works on HDMI every time and fails on DisplayPort every time has a working panel, a working cable path, and a working graphics card — the failure is in the DisplayPort handshake, and that narrows the search to hot-plug detection, link training, EDID, or the monitor's wake behaviour.
The same logic applies to the cable and port comparisons. A cable that works on another monitor but fails on this one is evidence about the combination, not about the cable alone. A port that fails with every cable is evidence about the port. The fault following the component is the evidence; the price of the cable is not.
Six Misconceptions
A replug fixing it means the connector is loose. Wrong. A replug fixing the picture does not mean there is poor contact. The replug may only have triggered re-enumeration or link retraining. A loose connector is tested by whether the fault follows the cable or the port, not by the fact that a replug helped.
A replug fixing it means it is repaired. Wrong. Having to replug at every boot is itself evidence that it is not repaired. The replug is a comparison method, not a repair. A repair is when a cold boot produces a picture without any intervention.
Waiting longer will bring the picture back. Wrong. The shape covered here is one where waiting does not help — the hot-plug detection or link training window has already been missed, and waiting longer does not reopen it. If waiting does bring the picture back, that is a different shape with a different diagnosis.
A more expensive cable will fix it. Wrong. The cable is only one of five layers. A cable comparison tests whether the fault follows the cable; the price of the cable is not evidence. An expensive cable that fails the same way proves the fault is elsewhere.
Restarting not working means the card is broken. Wrong. A restart takes the warm restart path, while a cold boot takes a different path. A fault that appears only on cold boot can sit in the monitor's Deep Sleep behaviour or firmware, not in the card.
DisplayPort and HDMI handshake the same way. Wrong. DisplayPort is packet-based and needs link training; HDMI does not. HDMI working does not mean DisplayPort should work — the DisplayPort versus HDMI comparison is itself diagnostic evidence pointing at the DisplayPort handshake layer.
Boundaries: What This Guide Does Not Cover
Waiting for the picture to arrive on its own is a different shape — the picture was late, not absent. Restarting bringing the picture back is a different shape — the warm restart path works. Reversing the power-on order bringing the picture back is a different shape — the order was the problem. A picture that disconnects and reconnects on its own during normal use, with no reboot involved, is a different shape — there is no boot trigger at all. One DisplayPort output permanently showing no signal while the others work is a different shape — a dead port, not a handshake window. A multi-monitor daisy-chain where one display is black at boot and returns after a replug is a different situation again: that is a daisy-chain arrangement, and the single-display direct connection covered here must be kept separate from it. A picture that appears only after entering Windows, a monitor that warms up slowly, a boot that stops at the motherboard logo, and a machine that never shows a picture under any method are all different shapes, each with its own diagnosis. Pin 20 power backfeed is a separate power question.
Note the waiting-time question honestly: different sources give different figures for how long to leave a cable unplugged — some say 30 seconds, some 60 seconds, some a minute. This guide does not state a universal number; follow the monitor's own instructions.
When to Send It In
If the comparisons point at a monitor setting — Deep Sleep, automatic input detection, or a firmware behaviour — the fix may be a setting change or a monitor firmware update, and there may be nothing to send in at all. If the fault follows the cable, replacing the cable is the fix. Inspection is worth considering when the evidence is consistent and unexplained: the monitor is out of Deep Sleep, the input is fixed, the order is correct, the cable and port have been swapped, Fast Startup is off, the driver is current, and every cold boot still needs a replug. Bring the monitor model and firmware version, the cable, the power-on order, how long was waited, the restart result, the replug result, and the DisplayPort versus HDMI comparison result.
For inspection, the workshop is at Room 1209, Dali Plaza, Shek Mun. Phone 2186 8010, WhatsApp 6558 6806. Inspection fees follow the published three-tier pricing, HK$400–2,800. There is no on-site service and no Mong Kok shop.
FAQ
I have to unplug and replug the DisplayPort cable every boot — is the connector loose?
Not necessarily. A replug fixing the picture does not mean there is poor contact. The replug may only have triggered re-enumeration or link retraining — the hot-plug detection signal being asserted again, or the link being trained again. Having to replug at every boot is itself evidence that the problem is not repaired. Test whether the fault follows the cable or the port before concluding anything about the connector.
Why doesn't restarting fix it, when replugging does?
A restart takes the warm restart path, while a cold boot takes a different path. The hot-plug detection and link training window at power-on is only re-triggered at the moment of replugging. Restarting does not re-trigger that window in the same way, so it cannot fix a fault that sits in the cold-boot handshake. That is why the shape — restart fails, replug succeeds — is itself diagnostic evidence pointing at the boot handshake layer.
The monitor was already on and the power-on order was right — why is there still no picture?
Correct order only rules out one cause. Deep Sleep can leave the monitor unready at the exact moment the card looks for the hot-plug signal. Link training can fail at cold boot even when the order is right. The EDID read can fail at boot even when the order is right. Correct order is a necessary check, not a guarantee — the handshake layers can still fail with the order correct.
Will waiting longer bring the picture back?
In the shape covered here, no. The hot-plug detection or link training window has already been missed, and waiting longer does not reopen it. Waiting bringing the picture back is a different shape (#324), where the picture was late rather than absent. If waiting does bring the picture back, the diagnosis belongs with that shape, not this one.
HDMI works every time but DisplayPort needs replugging — what does that mean?
DisplayPort is packet-based and needs link training; HDMI does not. HDMI working does not mean DisplayPort should work. This comparison is itself evidence pointing at the DisplayPort handshake layer — hot-plug detection or link training. The monitor panel, the graphics card, and the general display path are working; the failure is specific to the DisplayPort handshake at cold boot.
Does turning off the monitor's Deep Sleep help?
It can help. Deep Sleep leaves the monitor unready at the moment of boot, so it can miss the hot-plug detection window. Switch Deep Sleep off, fix the input source to DisplayPort instead of automatic detection, and switch automatic input switching off — changing only one setting at a time, and testing a cold boot after each change. If the fault disappears after one specific change, that setting was the cause.
Will a more expensive DisplayPort cable fix it?
Not necessarily. The cable is only one of five layers, and a cable comparison tests whether the fault follows the cable — not the price of the cable. Try a different cable and a different DisplayPort output, one at a time, and watch whether the fault follows the cable, follows the port, or stays with the monitor. An expensive cable that fails the same way proves the fault is elsewhere.
Does Win+Ctrl+Shift+B help?
It is a comparison method, not a repair. Pressing it restarts the graphics stack: if the picture appears, the fault points at the graphics stack layer; if it does not, the fault points at the boot handshake layer. It is a diagnostic comparison — it tells you which layer the fault sits in, and it does not fix a cold-boot handshake fault on its own.
How is this different from #325's "monitor powered on after the PC" issue?
In #325 the order is reversed — switching the monitor on before the PC works every time, and restarting and replugging are interchangeable ways of breaking the deadlock. In the shape covered here, the order is already correct and the fault still happens, restarting does not help, and only replugging works. The two shapes have different forks: #325 is an order problem, this one is a boot handshake problem.
What information should I bring if I send it in for inspection?
Bring the monitor model and firmware version, the cable, the power-on order, how long was waited, the restart result, the replug result, and the DisplayPort versus HDMI comparison result. The workshop is at Room 1209, Dali Plaza, Shek Mun. Phone 2186 8010, WhatsApp 6558 6806. Inspection fees follow the published three-tier pricing, HK$400–2,800.