DisplayLink Forum - View Single Post - DisplayLink simply doesn't do anything on W10!?

udippel · 03-03-2019, 08:42 PM

I'm a Linux-er and installed the software on my main boot partition without any trouble, but a lot of success (lenovo Helix 2, lenovo ThinkPad PRO dock). After reboot, I have two displays, that I can move around, define as primary and secondary, you name it.

Next, I did the same on my secondary W10-boot. Before, when plugging in a monitor, it would simply mirror the built-in display. After the installation, and restart, it still ... simply mirrors the built-in display. It is installed, and there's even an icon in the taskbar. But with 'video' and 'audio' I cannot set anything different from what I could do without that software.
The display driver (Intel 5300) still shows nothing but the internal display.

What is going wrong here? No, I don't actually need to make it work, though it is curious that in this case the Linux-install works out of the box, and as expected, while under W10, it simply does nothing.

03-03-2019, 08:42 PM	#1
udippel Junior Member Join Date: Mar 2019 Posts: 14	DisplayLink simply doesn't do anything on W10!? I'm a Linux-er and installed the software on my main boot partition without any trouble, but a lot of success (lenovo Helix 2, lenovo ThinkPad PRO dock). After reboot, I have two displays, that I can move around, define as primary and secondary, you name it. Next, I did the same on my secondary W10-boot. Before, when plugging in a monitor, it would simply mirror the built-in display. After the installation, and restart, it still ... simply mirrors the built-in display. It is installed, and there's even an icon in the taskbar. But with 'video' and 'audio' I cannot set anything different from what I could do without that software. The display driver (Intel 5300) still shows nothing but the internal display. What is going wrong here? No, I don't actually need to make it work, though it is curious that in this case the Linux-install works out of the box, and as expected, while under W10, it simply does nothing.