This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
My monitor (LG 29UM68) is connected to Surface Dock -> SP4, via direct miniDisplayPort.
It keeps entering sleep mode and waking up repeatedly, even though my SP4 is asleep. This does not happen when I connect the monitor to SP4 directly.
Another issue is that if I set to PC Screen Only, after few seconds, it will automatically switch back to external monitor only. Again, this does not happen if I connect monitor to SP4 directly.
These 2 issues only arise if I use Surface Dock.
I have gone through all the steps here (https://www.microsoft.com/surface/en-sg/support/hardware-and-drivers/troubleshoot-docking-station-surface-dock) successfully, but issue persist.
Please help.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I am having this exact same issue -- your video captures it perfectly. Surface Book connected to Surface Dock, which is connected to an LG 27UD58 4K monitor, and also an older ASUS monitor. (Both connected via DisplayPort.) When I sleep the Surface Book the ASUS monitor also goes to sleep normally, but the LG monitor cycles on and off continuously as shown in the video above.
Hi Everyone,
Lately I bought a "Club3D CAC-1170 Mini Displayport - HDMI 2.0 adapter". It converts the 1.2 mini display port to HDMI 2.0. If I connect my Surface Dock with this adapter and a HDMI 2.0 cable to my LG 27UD68P monitors second (!!! and only the second!!!) HDMI port, then I can use the monitor in 4K, with 60Hz refresh rate, and if I put the Surface Pro 4 into standby, then the monitor goes to standby as well, and stays in standby. If I turn the Surface back on, the monitor turn back on.
So we can get it work, but I must say, this was the 6th converter that I bought. So now I have a lot of minidisplay to anything adapters if someone interested:)
Still don't know why the dock wakes the monitor from standby if I connect them directly with minidisplay port - display port cable and the Surface goes into stand by mode.
You've heard correctly.
I have two of the most recent LG Ultrawides. One is connected via mini-DP to HDMI adapter/cable. The other is connect by mini-DP to DP cable. When I put the Surface to sleep or let it shut off the displays after going idle, the HDMI-connected monitor sleeps fine, but the DP monitor cycles in and out of power saving mode.
If I connect the DP monitor to the Surface, it goes to sleep fine and has no issues.
If I actually shut down the PC, they also sleep fine.
I'm able to replicate this exact issue on my SP4 i7 when using the Surface Dock. The issue does not occur when using the SP3 dock with the same SP4 and monitor (which points to it not being port related).
My dock firmware and Surface are both fully up to date.
This is clearly an issue that needs to be addressed. Let's hope Microsoft steps up and fixes it!
You're absolutely right in that certain aspects of this problem are getting muddied.
Bottom line, the issue of having a monitor connected and setting the Surface Pro 4 / Surface Book to "PC screen only" does NOT stay for more than 2 seconds - the external monitor wakes up again immediately.
While your solution of "turning off the monitor" may work manually, the problem exists where if an app was previously opened on the external monitor and closed there, it will again open on the "powered off" external monitor - whereas if the monitor was really "asleep" in PC screen only-mode, the app would now appear on your Surface screen where it should.
So we shouldn't let workarounds allow support to get off-the-hook. This is a problem that needs to be fixed.
