USB-monitor ASUS 169B+ not recognized on Intel NUC

[clkdiv]

Hello Alban,

I ran the Setup (8.2M3) on another machine (my ZOTAC) and assured the C:\ProgramData\DisplayLink\Debug to be empty before. Disconnected the machine from internet, switched to advanced logging tool and plugged in the monitor.

Monitor was recognized as device, then was disconnected after maybe 20 seconds, then reconnected again and then works like charme now (seemed to me that driver installed). But this is my ZOTAC PC, here evrything was fine for months now, both ASUS 169B+ working flawlessly.

On the NUC still really NOTHING happens when plugging in the monitor, nothing but the monitor showing the ASUS logo, then becoming somewhat grey (black with backlight on) for some seconds, then being and staying pitch black. There is no C:\ProgramData\DisplayLink\Debug-folder on the NUC either, I suppose that would be generated when the drivers install, right? But obviously they don't... When plugging in the monitor there is no response in the device manager and also non in "USBDeview", a tool to list all UDB devices. I attach the list created by that tool to this message too, maybe it is of some use? (Please have a look at USB Root Hub 3.0!).

Ok, I hope this helps. Thanks a lot! Martin...

[AlbanRampon]

Hello,
Thank you for the detailed report.
This proves the device doesn't appear on the USB.
There is no amount of trickery on the driver which would make it work as it is now: the driver is not even invoked by Windows as there's no device on the bus.
DisplayLinkManager log is created when the driver starts, not when it installs. The installation is visibly correct in the setupapi logs.
I can see two possible sources here:
- interoperability issue with the host controller of the NUC,
- power problem.

The last experiment I could suggest is to try in USB 2.0 mode via your externally powered hub.
This is WAY out of the USB specification for the power, but you'd be using a totally different path which is somewhat less prone to interop issues.

It is possible you would have to remove all elements of the j5create/MCT. Some elements may need to be removed manually if reports from other users of that competitive technology are correct... and I believe them.

Kind regards,
Alban