Network Error on install using latest driver

luiset83 · 04-24-2013, 01:24 AM

The network driver changed, so as a result Windows thinks the network connection is a 'new adapter', and explains the error message you saw, as I did as well. All said, it's probably a slightly bad coded installer/uninstaller issue, that alone is should not be an issue, as you said your connection had a driver installed, as mine did as well.

In my case, I get annoyed when things like that happen and I ended up removing all the USB devices related to DisplayLink with USBDeview -- http://www.nirsoft.net/utils/usb_devices_view.html and deleted references to the older network connection, rebooted and plugged in the dock to re-detect the hardware to get rid of the stale devices.

That being said, if your USB network connection is fine (as mine was -- I did the above to get rid of stale remnants of old drivers) you shouldn't need to worry about that. In re: to the audio, it's possible that might be some sort of bug. It might help the developers if you capture a log as mentioned here:

http://www.displaylink.com/support/ticket.php?id=269

04-24-2013, 01:24 AM	#2
luiset83 Member Join Date: Feb 2012 Posts: 48	The network driver changed, so as a result Windows thinks the network connection is a 'new adapter', and explains the error message you saw, as I did as well. All said, it's probably a slightly bad coded installer/uninstaller issue, that alone is should not be an issue, as you said your connection had a driver installed, as mine did as well. In my case, I get annoyed when things like that happen and I ended up removing all the USB devices related to DisplayLink with USBDeview -- http://www.nirsoft.net/utils/usb_devices_view.html and deleted references to the older network connection, rebooted and plugged in the dock to re-detect the hardware to get rid of the stale devices. That being said, if your USB network connection is fine (as mine was -- I did the above to get rid of stale remnants of old drivers) you shouldn't need to worry about that. In re: to the audio, it's possible that might be some sort of bug. It might help the developers if you capture a log as mentioned here: http://www.displaylink.com/support/ticket.php?id=269