Recover video sent to the wrong or phantom display before or after Windows starts

The computer is running, but the image is being presented through a different display path than the person is watching. Two catalog variations share the same physical isolation test but require different final repairs:

• Windows-stage wrong or phantom output: firmware video and perhaps the Windows logo are visible, but Windows changes to an inactive display, a disconnected monitor remembered in the desktop topology, a dock, a VR headset, a USB display adapter, or another GPU output at sign-in.
• Firmware-stage wrong output: the manufacturer logo, firmware setup, or preboot menu is sent to one port or GPU while Windows later appears normally on another. Windows display settings cannot change video selection before Windows loads.

The stage distinction matters; knowing a label such as “UEFI” or “legacy BIOS” does not. This procedure detects the stage by observing when the picture disappears and then branches. It does not ask the user to change firmware mode.

Searchable Windows error codes and exact messages

Record an exact code only if Device Manager displays it for the relevant display adapter, monitor, dock, or USB display device. Do not assign a driver code to an ordinary wrong-output selection that has no code.

Use this procedure when at least one of these observations is true:

• Windows finishes starting, but the visible desktop, sign-in screen, or pointer is on another attached display.
• The screen becomes blank at sign-in and returns after cycling Windows+P or disconnecting other displays.
• The sign-in sound, keyboard response, remote session, or visible image on a second display shows that Windows is running while the watched display is blank.
• Settings shows a numbered display that is no longer physically present, and Windows is extending to it or making it primary.
• The manufacturer logo or Windows image appears on one connector, but the firmware setup screen appears on a different attached output.
• A dock, VR headset, USB display adapter, television, projector, wireless display, eGPU, or second graphics adapter was recently connected, removed, or moved.

Do not use this procedure when:

• No display shows a manufacturer logo, firmware menu, Windows output, or other sign of video and the system does not complete POST.
• The computer reports a boot error, stop code, spinning-dot freeze, automatic-repair loop, or black screen with a blinking text underscore before Windows starts.
• A black screen follows a known third-party theme patch, shell replacement, corrupt profile, or failed update and remains identical with every extra display disconnected.
• Windows Explorer alone is not starting but Task Manager and all display topology are normal.
• The screen has visible corruption, colored blocks, lines, repeated GPU resets, thermal shutdown, or a persistent Device Manager Code 43. Those findings require graphics hardware or driver diagnosis.
• The external display is never detected on any known-good cable, port, and computer. That is not a phantom-primary problem until the hardware path works.
• The issue is only that windows open off-screen while the main desktop remains visible. Use window-movement controls rather than changing the entire display topology.

The exact EDID history, the firmware's internal port-priority rule, why Windows retained a removed display, and the precise time the topology changed may remain unknown.

The following may not remain unknown:

• whether the picture is lost before Windows begins or when Windows takes control;
• which physical cable, adapter, dock, GPU, and port feeds each display;
• whether the tested monitor is set to the matching input;
• whether one direct-connected display works with all other outputs removed;
• which numbered Windows display corresponds to each physical screen; and
• whether Device Manager shows an exact code for the relevant adapter or monitor.

• A wired keyboard connected directly to the computer
• One known-good monitor or the laptop's working internal panel
• One known-good direct video cable appropriate for the computer and display
• Physical access to disconnect docks, dongles, VR headsets, projectors, televisions, USB graphics adapters, wireless-display adapters, eGPUs, and extra monitors
• Access to the monitor's input-selection menu
• Administrator access if a display driver or non-present device must be changed
• The graphics or computer manufacturer's driver package available before uninstalling any display adapter
• A phone or paper on which to record the connector map and the result of each boot

Do not begin by opening the case, moving a graphics card, changing firmware mode, or resetting firmware defaults.

1. If any display currently shows Windows, save work and take screenshots of Settings > System > Display before changing the layout.

2. In Display settings, select Identify and record the number that appears on every physical screen. Note any numbered tile for which no physical screen displays a number.

3. Draw a connector map. For each display record:

   • physical display name;
   • selected input, such as HDMI 1 or DisplayPort;
   • direct PC, dock, adapter, or receiver connection;
   • GPU or motherboard connector bank; and
   • whether it shows the manufacturer logo, Windows logo, sign-in screen, or desktop.

4. In Device Manager, expand Display adapters and Monitors. Record device names, warning icons, and exact Device status text. Do not remove anything yet.

5. Shut down Windows normally. Do not use a firmware reset or forced power-off when Windows can still be controlled.

6. Disconnect every nonessential display path:

   • extra monitors and televisions;
   • projector and capture-device pass-throughs;
   • dock or port replicator;
   • VR headset;
   • USB display adapter;
   • wireless-display adapter;
   • eGPU, if the computer has a safe built-in display path; and
   • video KVM or splitter.

7. Leave one known-good display connected directly. On a laptop, start with the internal panel and no dock. On a desktop with a discrete graphics card, start with one port on that installed card. Do not move the cable to a motherboard video port unless the processor actually has an enabled integrated GPU and the computer manufacturer supports that path.

8. Use the display's own controls to select the exact connected input rather than relying on automatic input detection.

1. Start the computer with the single-display configuration and observe four stages separately:

   1. power-on/manufacturer logo;
   2. firmware or one-time boot menu, if invoked;
   3. Windows logo or spinning dots; and
   4. sign-in screen and desktop.

2. Record the first stage at which the picture disappears or moves.

   • If firmware or its setup screen is missing but Windows later becomes visible, use Branch A.
   • If firmware and the Windows logo are visible but the picture disappears at sign-in, use Branch B.
   • If the single display works at every stage, reconnect the other display paths one at a time and use Branch C to correct the topology.
   • If no stage is visible on a known-good direct path, stop; the evidence does not support a wrong-output diagnosis.

3. During a Windows-stage blank screen, press:

   Windows + Ctrl + Shift + B
   

   A beep or screen flicker means Windows processed the graphics reset shortcut. It does not prove the correct display path was selected.

4. Cycle projection modes in a controlled way. Press Windows+P, release the keys, press P once, and press Enter. Wait at least ten seconds. Repeat no more than three additional times, waiting after each attempt. This cycles through PC screen only, Duplicate, Extend, and Second screen only.

5. Interpret the projection test:

   • If an image appears in one mode, Windows was running and output selection or topology is implicated.
   • If the image appears only in Duplicate, keep that temporary mode until the physical displays can be identified.
   • If no mode produces an image, do not continue cycling indefinitely. Test Ctrl+Alt+Delete.

6. Press Ctrl+Alt+Delete once.

   • If the Windows security screen appears, choose Task Manager and continue with Windows-stage diagnosis.
   • If Task Manager appears on the watched display but the desktop is blank, select Windows Explorer > Restart. If that alone restores the desktop, route the case to a shell/Explorer repair; do not call it a phantom-display fix.
   • If neither appears, use the physical one-display test and WinRE Startup Settings in Branch F.

7. After any Windows image is recovered, open Settings > System > Display and choose Identify. Record:

   • the physical number shown by each screen;
   • any numbered tile with no matching physical display;
   • the selected Multiple displays mode;
   • which display is marked main; and
   • current resolution and refresh rate.

8. In Device Manager, read the complete Device status for every item with a warning. Route exact Code 22, 31, or 43 results to Branch D. A gray non-present monitor showing Code 45 is evidence of a disconnected historical device, not a fault that must be repaired.

9. If the affected connection uses USB-C, a dock, or an adapter, record any Windows notification such as Display connection might be limited, Use different USB port, or USB device not recognized and use Branch E.

Branch A — The firmware or preboot menu uses a different physical video output

1. Shut the computer down. Leave only one known-good monitor connected directly to a native GPU output.

2. Manually select the monitor input matching that cable.

3. Start the computer and note whether the manufacturer logo appears. If it does, invoke firmware setup using the computer manufacturer's documented key or, when UEFI Firmware Settings is available, through the matching Windows path:

   • Windows 11: Settings > System > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > UEFI Firmware Settings > Restart
   • Windows 10: Settings > Update & Security > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > UEFI Firmware Settings > Restart

4. If the firmware screen is visible, the working preboot connector has been identified. Make no firmware changes merely to prove it.

5. If Windows later uses a different connector, shut down and label the two paths:

   • preboot/firmware-active port; and
   • Windows-preferred port.

   Use the preboot-active port whenever firmware setup or a recovery menu must be viewed. This is a valid resolution when firmware offers no supported output-selection control.

6. If the first direct GPU port never displays the manufacturer logo, power down fully and test one other native output on the same graphics adapter. Change one cable or port at a time and record the result.

7. Disconnect VR, dock, television, capture, KVM, projector, and adapter outputs before entering firmware; reconnect them only after exiting firmware and reaching Windows.

8. If the exact computer's firmware has a documented Primary Display, Initial Display Output, or equivalent control, record its original value before making one reversible change. Do not guess among PEG, PCIe, IGD, or similar labels without model-specific documentation. Restore the original value immediately if no picture appears on the intended connector.

9. Do not update or flash firmware solely because it selected a different working port. Escalate to the manufacturer only if no supported direct connector can show the firmware screen.

Branch B — Windows switches to the wrong output at sign-in

1. Keep only the one intended display connected directly. Restart Windows.

2. Press Windows+Ctrl+Shift+B once and wait ten seconds.

3. Press Windows+P, then P, then Enter, waiting ten seconds. Repeat until a visible mode appears, but no more than four total selections.

4. When the image returns, choose Duplicate temporarily if more than one physical display must be connected for identification. Duplicate reduces the chance that Settings opens on the unseen extended desktop.

5. Open Settings > System > Display and select Identify.

6. Select the tile for the intended physical display. Under Multiple displays, enable Make this my main display when the option is available.

7. Select each tile that corresponds to no connected physical display. Choose Disconnect this display when Windows offers that choice, then select Apply.

8. Arrange the remaining numbered tiles to match their physical positions. Select Apply, then move the pointer across each boundary to confirm the map.

9. Select the manufacturer's recommended resolution for each physical screen. Do not choose an untested refresh rate while recovering visibility.

10. Shut down, start again with the same single display, and confirm that the sign-in screen stays on it before reconnecting other outputs.

Branch C — A disconnected display remains in the Windows topology

1. With one working display, open Settings > System > Display > Multiple displays and select Detect once.

2. Select Identify and match every visible number to a physical screen.

3. Select the unmatched numbered tile and choose Disconnect this display, then Apply. Do not disconnect the tile currently carrying the only visible desktop.

4. On Windows 11, set Remember window locations based on monitor connection according to the intended docking behavior. If windows repeatedly become stranded after undocking, also enable Minimize windows when a monitor is disconnected. These controls are not present on every Windows 10 build; Windows 10 users should skip this step when the controls are absent.

5. Restart and inspect Settings again. If the phantom tile is gone, stop; do not remove devices from Device Manager.

6. If a phantom tile persists, disconnect all external display hardware, open Device Manager, and select View > Show hidden devices.

7. Expand Monitors. A truly non-present monitor is gray and may show Code 45. Compare its name and hardware history with the physical connector map.

8. As an optional topology-reset experiment, uninstall only the gray, non-present monitor entry that corresponds to disconnected hardware. Code 45 itself needs no repair. Do not uninstall the active monitor, a display adapter, an internal panel, or every generic monitor entry.

9. Select Action > Scan for hardware changes, then restart. Windows will enumerate a genuinely connected Plug and Play monitor again.

10. Reconnect one display path at a time. After each connection, use Identify, select the desired Duplicate or Extend mode, and confirm which display is main before adding the next device.

Branch D — Device Manager reports an exact display-adapter code

1. Keep a single working display connected and obtain the correct graphics package from the computer or graphics-device manufacturer before changing the driver.

2. For Code 22, right-click only the disabled intended display adapter and choose Enable device. Restart and check Device status again.

3. For Code 31, open the adapter's Properties > Driver tab. If the problem started immediately after a driver update and Roll Back Driver is available, select it, give the reason, and restart.

4. For Code 31 when rollback is unavailable, or for Code 43 after a known bad driver installation:

   1. select the affected adapter in Device Manager;
   2. choose Uninstall device;
   3. do not remove a second working adapter in the same session;
   4. restart Windows so Plug and Play can reinstall the device; and
   5. install the prepared manufacturer package if Windows does not restore a working driver.

5. Reopen Device Manager and read Device status.

6. If Code 43 persists after one clean re-enumeration and the correct driver, stop. Treat it as an adapter, power, firmware, dock, or hardware problem. Do not keep rewriting the display topology around a failed device.

7. If the adapter has no code after restart, return to Branch B or C and rebuild only the desired display topology.

Branch E — The missing path uses USB-C, a dock, or a display adapter

1. Disconnect the dock or adapter and prove the same display works through a direct native video connection where available.

2. If direct video works, power-cycle the external display and dock. Disconnect dock power and the PC cable, wait 30 seconds, restore dock power, and then reconnect the PC.

3. Use the cable supplied for the dock/display or another cable explicitly rated for its video mode. A USB-C cable that charges successfully is not necessarily capable of carrying display data.

4. Connect the dock or adapter directly to the computer, not through another hub.

5. If Windows displays Display connection might be limited or Use different USB port, move the connection to a computer port documented to support DisplayPort, Thunderbolt, or the required alternate mode. Do not assume every USB-C-shaped port has the same capabilities.

6. Reconnect one display to the dock, use Windows+P to select Duplicate or Extend, and choose Detect in Display settings.

7. Add further dock displays one at a time. Stop at the first connection that makes an existing output disappear; the dock, adapter, GPU, cable, or bandwidth limit needs model-specific review.

8. If Windows reports USB device not recognized, inspect Device Manager for the actual USB device code. Resolve that connection/device failure before changing the Windows primary display.

Branch F — Windows-stage output is still blank with one direct display

1. Enter Windows Recovery Environment and choose Troubleshoot > Advanced options > Startup Settings > Restart.

2. First try Enable low-resolution video. This starts Windows with the current video driver at a low resolution and refresh rate.

3. If the image appears, open Display settings, choose the recommended resolution for the one physical display, and then review the driver in Branch D.

4. If low-resolution video remains blank, return to Startup Settings and select Safe Mode.

5. In Safe Mode, inspect Device Manager and Display settings. Do not force a permanent BCD Safe Mode setting.

6. If Safe Mode is visible but normal mode is not, the evidence points away from firmware-only output selection and toward a Windows driver, startup software, or topology problem. Use Branch D and reconnect extra displays only after normal mode is visible.

7. If WinRE, low-resolution video, and Safe Mode all remain invisible on every known-good direct output, stop. The wrong/phantom-output diagnosis is not sufficiently supported.

• One direct display works at every stage: the computer and display can generate video; reconnecting devices one at a time should reveal the topology, dock, adapter, or port that diverts output.
• Firmware appears only on one port and Windows only on another: BP-016 is confirmed. Label and use the firmware-active connector for preboot work, or use only a documented model-specific primary-display setting.
• Windows+P makes the sign-in screen appear: BP-015 is strongly supported. Correct the main display and disconnect the unmatched topology tile.
• Removing a gray Code 45 monitor removes the phantom tile: the topology-reset experiment succeeded. It does not prove that the disconnected-device record caused the original black screen. Reconnect devices one at a time and verify the final topology through two restarts.
• Restarting Windows Explorer restores the desktop: route to shell/startup diagnosis; it was not proven to be a display-output problem.
• Code 31 clears after rollback/reinstall: the driver caused or contributed to the output change. Rebuild topology only after Device status is normal.
• Code 43 remains: stop topology changes and diagnose the adapter or hardware path.
• Direct output works but the dock path does not: isolate dock power, cable, USB-C capability, firmware, driver, and supported display count with the computer/dock manufacturer.
• No direct output works in firmware, WinRE, or Safe Mode: stop; wrong-output selection is no longer the most credible explanation.

• Do not change UEFI/legacy mode, Secure Boot, storage-controller mode, or partition layout for a display-output problem.
• Do not flash firmware merely because preboot video appears on a different working connector.
• Do not connect a desktop monitor to the motherboard video port unless the processor and firmware provide a supported active integrated GPU path.
• Do not uninstall all display adapters or all monitor entries at once.
• Do not treat a gray Code 45 monitor as broken hardware; it normally records a disconnected device.
• Do not delete display registry keys, force EDID overrides, or use an unverified display-switching utility.
• Do not choose an unsupported resolution or refresh rate while only one screen is usable.
• Do not repeatedly force power off while Windows is updating.
• Do not leave a VR headset, capture device, dock, KVM, or projector attached during the one-display isolation test.
• Do not call a persistent Code 43 a harmless phantom-display issue.
• Do not reset or reinstall Windows until firmware/preboot and Windows-stage output have been separated and the simple physical/topology tests have failed.

1. If a Display Settings change removes the visible desktop, wait for Windows to revert an unconfirmed resolution change. If it does not, use Windows+P, then P, then Enter, waiting after each selection until Duplicate or the previously visible mode returns.

2. Reconnect the last known working monitor directly to the port recorded in section 6 and manually select that input.

3. If a non-present monitor was uninstalled, reconnect that physical device and choose Action > Scan for hardware changes in Device Manager. Windows should enumerate it again.

4. If a display driver was rolled back and the old driver is worse, open Device Manager > Display adapters > Properties > Driver > Update Driver, or reinstall the prepared manufacturer package.

5. If a display adapter was uninstalled, restart Windows once. If Plug and Play does not restore it, install the prepared manufacturer package. Do not remove the remaining working adapter.

6. If a model-specific firmware primary-display setting was changed, power down, connect the monitor to the original known-good preboot port, return to firmware setup, and restore the exact recorded original value.

7. Return to the baseline one-display configuration before attempting another branch. Do not combine a driver rollback, firmware setting change, dock reconnection, and topology rewrite in one untestable step.

1. With only the intended primary display connected, perform a complete shutdown and start. Confirm that the manufacturer logo, Windows startup, sign-in screen, and desktop are visible at the expected stages.

2. If firmware output uses a different port by design, perform one controlled entry into firmware setup with the monitor on the labeled preboot-active connector. Exit without changing settings and confirm Windows still starts.

3. In Windows, open Settings > System > Display > Identify. Every numbered tile must correspond to a connected physical display. No disconnected tile should be selected as main.

4. Confirm the intended PC screen only, Duplicate, Extend, or Second screen only mode with Windows+P.

5. Open Device Manager. Confirm that active display adapters and monitors have no warning icon and no Code 22, 31, or 43. Code 45 is acceptable only for a device that is intentionally disconnected and hidden.

6. Reconnect each additional display path one at a time. After each one:

   • select Identify;
   • confirm the main display;
   • confirm the arrangement;
   • confirm recommended resolution; and
   • restart once before adding another complex dock or adapter path.

7. Test one undock/re-dock or disconnect/reconnect cycle if that transition originally caused the phantom output.

8. Perform two normal restarts with the final topology. Confirm that neither the sign-in screen nor desktop returns to an absent display.

Confidence is approximately 80% when the image is reproducibly restored by selecting the matching physical port, reducing the system to one display, cycling Windows+P, or disconnecting an unmatched display tile, and the corrected layout persists through two restarts.

Confidence is high for the stage distinction when firmware is visible on one connector and Windows is visible on another during the same unchanged boot. Confidence is low when the only evidence is a black screen with no proof that Windows completed startup.

Stop immediately if:

• no known-good direct output shows firmware, WinRE, Safe Mode, or Windows;
• the computer does not complete POST;
• the active adapter reports a persistent Code 43;
• video corruption or thermal/power symptoms appear;
• the next step would require an undocumented firmware option, firmware flash, registry EDID edit, or removal of every display driver;
• a motherboard video port's integrated-GPU support is unknown;
• the dock or adapter exceeds its documented display count or bandwidth and model-specific guidance is unavailable; or
• more than one variable must be changed at once to keep any display visible.