Thanks for posting again. Let’s try to get this figured out!
OK - if your setup was working fine, but then was broken by the version 5.3.25973.0 update that DisplayLink pushed, then that’s our most important clue.
Background: DisplayLink pushed an update which triggered a driver signing error, apparently particular to 64-bit systems. The error would show up in device manager as a Code 52.
This driver was only pushed for a few hours - once problems were seen the update was pulled, and DisplayLink went back to the prior version. So I think the great majority of users never had time to respond to the “update available” message and get this driver. But your system did, unfortunately.
So if your setup is was working fine at some point, as a first step, I’d recommend:
* Uninstall and then reinstall the latest DisplayLink drivers. In addition to anything lingering from the prior problems, I’ve seen at least one case where a display configured under a prior version, would then not come up after an upgrade (probably because something about the way DisplayLink remembers displays in the registry, had changed between versions). A fresh install fixed it.
* At the same time, also unplug power and USB from the dock. If the dock gets in a bad hardware state, but is still getting AC power, it will stay in that bad state until power is unplugged.
Let’s just try those two simpler things to start, and if that doesn’t do it, we’ll dig deeper …
Thanks for your patience while we figure this out!