I’m trying to use the TBT3-HDMI2X-83 with the NUC8i3BEH. This one supports thunderbolt, and is even mentioned by Intel as exemple of supported device.
I want to connect a second display through USB-C (first one is connected to the HDMI port of the NUC).
But it doesn’t work.
When I connect the device to the NUC, windows 10 doesn’t react. Nor when the display is connected with the Plugable.
Windows 10 is updated. Drivers too.
In the bios, Thunderbolt controller is checked.
The USB-C port works. When I connect a smartphone to it, this one charges (but that’s all ; I can’t load data).
Yes, I have installed the drivers you have linked.
I have done it by doing a right click on each inf file.
Then I tried to install the Thunderbolt control center, but it doesn’t work. According to the reviews, like many many other users.
Error 0x803FB005. I followed the method to manage this error, but it make no difference.
Thanks for trying. After further research it appears even if we can get the system to recognize the adapter, it appears that system will only support a single display over its Thunderbolt 3 port due to how it was designed by Intel (a hardware limitation between the graphics chipset and the Thunderbolt 3 chipset).
Unfortunately due to this limitation I’d suggest to return the adapter for a full refund and look into an alternative option like a USB-C to HDMI adapter/cable.
Oh !
I hoped you had a solution.
I had already tried a cable, but it didn’t worked.
I will try the UD-3900 Docking Station.
I think my problem is the USB-C port. It don’t allow data transfert. So, maybe through a USB3 port, I will have this second display.
Just for the knowledge, my wish was fulfilled.
Before to receive the UD-3900, I have installed the DisplayLink driver.
Without believe it, I have tried another time my USB C -> HDMI cable I had bought before the TBT3-HDMI2X-83. And it works.
The second display is usable.
No mention about Thunderbolt in windows, though.
So my problem is half solved. I can connect a second display through the USB C port, but not due to Thunderbot.