DisplayLink Forum - View Single Post - Windows 10 => Blank Screen with Version 7.9

dant2757 · 08-19-2015, 02:11 PM

I have the same problem. Just updated to Windows 10 and installed Displaylink 7.9 (and reinstalled with clean) USB 3.0 to Targus ACP70USZ. Everything works fine except the display will not wake when booted and some times after the PC wakes from idle. Problem started after install of Win 10.

When I cycle the power on the display twice, everything works fine. Always 2 power cycles at the display (an aged Dell SP2008WFP) to wake and it works fine.

Displaylink always recognizes the extended display even if it is blanked.

I have tried both the Digital and HDMI interface and both have the same issue. My wife has the same setup with an aged HP extended display and a RGB Analog interface. Everything works fine on that HP17 with Win 10??

Both PCs have Intel and NVIDIA video. Just forced displaylink to use the NVIDIA and hoping that solves the issue.

Any comments appreciated

08-19-2015, 02:11 PM	#2
dant2757 Junior Member Join Date: Aug 2015 Posts: 2	7.9 Extended Display Remains Blank when PC is Booted I have the same problem. Just updated to Windows 10 and installed Displaylink 7.9 (and reinstalled with clean) USB 3.0 to Targus ACP70USZ. Everything works fine except the display will not wake when booted and some times after the PC wakes from idle. Problem started after install of Win 10. When I cycle the power on the display twice, everything works fine. Always 2 power cycles at the display (an aged Dell SP2008WFP) to wake and it works fine. Displaylink always recognizes the extended display even if it is blanked. I have tried both the Digital and HDMI interface and both have the same issue. My wife has the same setup with an aged HP extended display and a RGB Analog interface. Everything works fine on that HP17 with Win 10?? Both PCs have Intel and NVIDIA video. Just forced displaylink to use the NVIDIA and hoping that solves the issue. Any comments appreciated Last edited by dant2757; 08-19-2015 at 02:24 PM. Reason: BTW: Everything worked fine on Windows 8.1.