Establish a stable one-monitor baseline, then compare direct and docked connections at a conservative supported mode. Change only one cable, output or setting at a time. A lower refresh rate stopping the flicker points to a mode-dependent problem but does not prove which component is at fault.
Component documentation · Not physically tested by NYBreakingRecord what actually goes black
Note whether the monitor’s power light stays on, whether its own menu remains visible, whether Windows/macOS still lists it, and whether other dock devices disconnect at the same time. A whole dock reconnecting suggests a different investigation from one screen losing video while Ethernet and a keyboard stay connected. Write down the current resolution, refresh rate, HDR setting, host socket, output socket and cable.
If the display’s own menu disappears or there is heat, visible damage or an electrical smell, stop using the affected equipment and contact manufacturer support. For an ordinary signal problem, the reversible checks below help create useful evidence without buying replacement hardware first.
Build a stable baseline
- Use one monitor and disconnect nonessential dock peripherals.
- Select the correct monitor input manually and confirm the dock’s proper power supply is connected.
- Choose a resolution/refresh/SDR combination documented for the entire path. A temporary lower mode is a diagnostic step, not a final performance claim.
- Where supported, connect the same monitor directly to the laptop using a known suitable video cable.
- Return to the dock, keeping the mode and monitor unchanged. Then test one replacement cable or alternate documented output at a time.
| Observation | What it narrows down | Next check |
|---|---|---|
| Direct stable, docked unstable | Something added by docked path | Host cable, output mode, dock firmware and power |
| Same cable fails on both paths | Cable or shared monitor/mode remains suspect | Known suitable cable at same mode |
| Both screens and USB devices reconnect | Whole dock link or power may be dropping | Host lead, power supply and supported port |
| Only higher mode flickers | Mode-dependent bandwidth/signal issue | Documented mode limits and cable capability |
Check native video topology
A dock port arrangement can be invalid before drivers become relevant. The WD22TB4 HDMI and MFDP USB-C outputs cannot carry video simultaneously. Other docks have grouped outputs. Read the exact model’s table rather than moving plugs randomly among identical-looking sockets.
If both screens show the same desktop instead of flickering, that is a separate symptom: inspect Extend mode and the platform’s MST support. The Mac and Dell daisy-chain guide explains a common topology mismatch.
Then check graphics or DisplayLink software
Use the laptop/GPU manufacturer’s supported update path for native graphics. Microsoft’s flicker guidance uses whether Task Manager also flickers as a clue in distinguishing a display-driver issue from an incompatible app; it is not a universal hardware diagnostic. Avoid third-party driver download sites.
For a DisplayLink output, verify the current supported DisplayLink Manager version, its running state and required macOS permission. A native screen and software screen may behave differently in the same dock. Read DisplayLink permissions and limitations before treating a software-dependent blank screen as a broken HDMI port.
Replace a cable when controlled comparisons consistently isolate it, or when it is visibly damaged. Escalate a dock fault with your component list and test log when the problem follows the dock across supported known-good paths. If no screen is detected at all, use the detection checklist instead.
Evidence you can inspect
Select Extend when independent desktops are needed; isolate adapters and test a known suitable cable and display.
Microsoft: external monitor troubleshooting ↗
Source location: Before you begin; troubleshoot connections
Evidence reviewed 2026-09-18 · Rule v1 · Next review 2026-10-18
Source retrieval: available. Last successful retrieval: 2026-09-30.
Limitations and evidence basis
Official documentation. Component-derived connection plans are not independently demonstrated end-to-end. No physical test by NYBreaking.
USB-C shape alone does not establish video support; capability must match at the host, cable and display.
Microsoft: USB-C connection problems ↗
Source location: Display connection might be limited
Evidence reviewed 2026-09-18 · Rule v1 · Next review 2026-10-18
Source retrieval: available. Last successful retrieval: 2026-09-30.
Limitations and evidence basis
Official documentation. Component-derived connection plans are not independently demonstrated end-to-end. No physical test by NYBreaking.
Windows 11 provides Identify and Detect controls in display settings and Windows+P display modes. Extend creates a desktop across supported connected monitors; settings do not add missing hardware capability.
Microsoft: use multiple monitors in Windows ↗
Source location: Identify and detect displays; Multiple displays; Windows+P
Evidence reviewed 2026-09-18 · Rule v1 · Next review 2026-10-18
Source retrieval: available. Last successful retrieval: 2026-09-30.
Limitations and evidence basis
Official documentation. Component-derived connection plans are not independently demonstrated end-to-end. No physical test by NYBreaking.
WD22TB4 HDMI and MFDP USB-C video outputs are mutually exclusive. Presence of both ports does not allow simultaneous video.
Dell WD22TB4 simultaneous output ports ↗
Source location: Important information; dual-display setup
Evidence reviewed 2026-09-18 · Rule v1 · Next review 2026-12-17
Source retrieval: available. Last successful retrieval: 2026-09-30. A source change is queued for review.
Limitations and evidence basis
Official documentation. Component-derived connection plans are not independently demonstrated end-to-end. No physical test by NYBreaking.
DisplayLink Manager needs the applicable macOS screen-capture permission; software and OS version matter.
DisplayLink: macOS Screen Recording permission ↗
Source location: Permission procedure
Evidence reviewed 2026-09-18 · Rule v1 · Next review 2026-10-18
Source retrieval: available. Last successful retrieval: 2026-09-30. A source change is queued for review.
Limitations and evidence basis
Official documentation. Component-derived connection plans are not independently demonstrated end-to-end. No physical test by NYBreaking.
Source availability and latest checks
- W1: last successful automated retrieval 2026-09-30.
- W2: last successful automated retrieval 2026-09-30.
- W3: last successful automated retrieval 2026-09-30.
- D4: last successful automated retrieval 2026-09-30.
- L1: last successful automated retrieval 2026-09-30.
A successful retrieval confirms availability, not unchanged meaning. An editorial source review is separate.
Additional manufacturer documentation reviewed 30 September 2026. These references support this guide; they do not create a tested finder result.
Put the conditions into your own setup.
Choose the exact equipment, then save or print the connection checklist.
Open the plannerFound a mismatch? Report a correction. No active paid affiliate links on this page.