I’m re-visiting this issue (last updated a year ago), because this issue has actually never gotten better for me, but I just lived with it and never came back to this thread. Moreover, the most recent other post in this subforum seems to describe exactly the same crash problem. Additionally, if you read the Amazon reviews for this adapter, more than 10 of the total 43 reviews for this product complain of this same crash/freeze(!!)…there’s clearly a pervasive defect with the hardware…in the year since I posted here has Plugable gotten to the bottom of what is quite clearly a bug affecting a large percentage of its users?
In case it helps further troubleshoot, I’ve followed all of the directions that I’ve seen given to users who complain about this behavior, including:
- removed, cleaned, and reinstalled the DisplayLink software (i now have 9.0.1809)
- disabled the USB selective suspension thing
Nothing helped. Some additional info, in response to Gary’s suggestion in the most recent post in this thread: I did as you suggested and when the display froze, I disconnected it and reconnected a DIFFERENT usb device (my mouse) to that USB port, and it worked. So the crash isn’t because the USB port itself is dying/being corrupted. But here’s a curious thing I discovered that might help: when the display crashes, I can disconnect it from the USB port and plug it into a DIFFERENT USB PORT on the same machine, and it will work. Furthermore, I discovered that if I did that and kept working away, and then it crashed again (when plugged into the 2nd port) – which sometimes happened – I could actually switch it back to the FIRST port, where it was originally plugged in before crashing, and it would resume working again (not ALWAYS, but sometimes). So as you can see, I don’t know precisely what’s going on, but there’s some sequential dance of crashing / unplugging / switching-ports that seems to let me recover functionality…but there’s not a firm rhyme or reason to it. Hopefully this curious behavior helps troubleshoot whatever’s going on…
But either way, it’s clear there’s a pervasive defect with this product, given the deluge of complaints describing the exact same crash, so it feels as though a refund or replacement of some sort might be in order…?