Microsoft Surface Pro X (Arm SQ1) Loses Display Configuration After Reboot

Ryan Buzar 20 Reputation points
2026-07-15T05:59:38.82+00:00

Hello,

I am troubleshooting a persistent external display issue on a user's Surface Pro X and could use some fresh eyes.

System Specs & Hardware:

  • Host: Microsoft Surface Pro X (Microsoft SQ1 processor)

OS: Windows 11 Pro (recently upgraded from Windows 10 Pro during troubleshooting)

Docking Station: Dell WD19/WD15 (or similar "G5" class) and a Lenovo USB-C Dock (tested both)

Monitors: * Monitor 1: Samsung (via HDMI) – Works fine

Monitor 2: Acer (via DisplayPort) – Loses connection on reboot

The Issue:

Whenever the Surface is rebooted or powered on from a cold start while connected to the dock:

Windows loses the extended display configuration.

The displays revert to "Duplicate" on Monitor 1 & 2.

Monitor 3 (the DisplayPort Acer monitor) is no longer detected at all.

Temporary Fix: If I unplug and re-plug the DisplayPort cable or the dock's USB-C cable after logging in, Windows instantly detects the third monitor and restores the correct extended layout.

Troubleshooting Already Attempted (No Improvement):

Cables: Swapped out brand-new HDMI and DisplayPort cables.

Monitors: Swapped physical monitors (the issue stays with the DisplayPort port/path, not the physical monitor itself).

  • Docks: Tested with both a Dell dock (with up-to-date firmware) and a Lenovo USB-C dock (with up-to-date firmware).

OS Upgrade: Upgraded from Windows 10 Pro to Windows 11 Pro.

Power Settings: Disabled sleep/power-saving settings on the monitors.

Device Manager: Disabled "Allow the computer to turn off this device to save power" for USB controllers.

Display Cache: Ran the Surface Display Cache clearing tool. This fixed the issue immediately, but the problem returned on the very next reboot.

Current Workaround:

I have instructed the user to boot the Surface, log in, and then plug in the USB-C dock. This workaround successfully loads the correct saved configuration every time, but it is not a viable long-term solution.

Given that this is an ARM-based SQ1 device, I suspect this might be a specific driver initialization handshake issue on boot over Type-C alternate mode and the DisplayPort power status on reboot.

Are there any known registry fixes, specific ARM-compatible display topology patches, or firmware updates to address this handshake failure on boot?

Thanks in advance for the help!

Windows for business | Windows 365 Business
0 comments
Answer accepted by question author
VPHAN 43,900 Reputation points Independent Advisor
2026-07-15T06:40:01.91+00:00

Hi Ryan Buzar,

The diagnostic logic in the previous assessment is technically sound and requires no fundamental correction. The persistent extended display failure on reboot is not an operating system corruption issue, but rather a hardware-level initialization latency inherent to the Qualcomm SQ1 architecture when paired with third-party docking firmware. During a cold boot, the Dell and Lenovo docks require a fraction of a second longer to initialize their internal DisplayPort hubs compared to native Microsoft hardware. Because the operating system receives no Hot Plug Detect signal during this critical pre-boot window, it assumes the Acer monitor is disconnected and fails to load the saved topology from the Configuration, Connectivity, and ScaleFactors registry keys.

Software interventions cannot retroactively correct a pre-boot hardware synchronization failure. Modifying registry parameters or attempting to force an Alternate Mode handshake via Windows power settings will not circumvent this physical timing mismatch. The hot-plug workaround is currently your only functional software-side mitigation because it forces the dock to send a fresh interrupt signal to the USB controller after the operating system has fully loaded.

To achieve a permanent resolution without manual user intervention, deploying a Microsoft Surface Dock is the correct engineering path forward. The native firmware of the Surface Dock initializes synchronously with the Surface Pro X hardware, ensuring the DisplayPort topology is immediately recognized by the UEFI and maintained seamlessly throughout the boot sequence.

Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VPHAN

Was this answer helpful?

2 people found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.