Displaylink driver fails to recognise AOC display

[AlbanRampon]

Your new log files still show the screen as not connected.
You can open the DevManView.html yourself and see the No in the connected column. It also shows another USB monitor called "e1649Fwu" on top of "E1659Fwu".

It could be useful to delete them from the Device Manager to see if Windows does recognize the "E1659Fwu" during a new connection.

[bazinga]

e1649Fwu is a colleagues older generation model of an AOC display that I was testing on my machine to see if it would detect it. I have tried to delete it from Device Manager and scan for new hardware however Windows searches for a driver via Windows update then fails to find one. Is there a driver that I can point to from Device Manager to force it to find the correct driver instead of searching windows updates?

[bazinga]

Ok an update - I managed to get it working by unzipping the DisplayLink_7.9M3.exe and manually installing the driver (NIVO\DisplayLinkUsb.inf) from Device Manager. The only downside now is that whenever I reboot my machine it looses the driver and I have to manually point it to the .inf. I have attached a new log file for you.

[AlbanRampon]

Nonetheless, the association of a driver to a device is a core functionality: the device arrives on the USB, the operating system matches a driver from its driver store. If no driver is available, Windows looks on Windows Update (if configured that way).
I am sorry but I don't know how to address this Windows issue. I would check around the permissions.