UD-ULTC4K sporadically disconnects/reconnects - happens with Apple M1 Pro and M3 Pro

Hi there, I’m back again.

I reported this issue back in 2023, got a replacement unit the but the issue never really goes awayl. It happens a lot more with the M1 Pro than the M3 Pro but it can happen with either laptop.

Both laptops are on the latest version of Tahoe (26.4.1 as of today) and the latest DisplayLink Manager (16.0 as of today).

Sometimes when this happens I’ll power cycle the dock, reboot the laptop and try switchign around to different USB-C ports on the laptop. I’m using the USB-C cable that came with the dock.

With my work laptop (M3 Pro) I can have weeks of stability and then an afternoon of frustration. The M1 is barely usable with the dock. It connects, displays light up (two external Dells connected via HDMI) and then suddenly the laptop beeps because power has been cut and displays disconnect and then immediately reconnect.

Sometimes it’ll take 30 seconds, other times it will take a few minutes.

Basically I’m pretty disappointed that such an expensive dock has never really worked reliably without the threat of sudden disconnect. I really appreciate the support you guys have given me, but in the end the equipment is just not fit for purpose it seems.

I keep hoping you’ll release some firmware updater or something but to no avail.

Any other suggestions before I trash these things? I don’t strictly need them any more because they were purchased when I had another work laptop with M2 CPU. Still though, it’s a great hub and I’d hate to replace it because of what seems like a.) a known issue and b.) something that should be solveable with a software/firmware update.

Seems like the according to this FAQ - https://kb.plugable.com/usb-c-docks/why-is-my-plugable-ud-ultc4k-dock-disconnecting-on-macos-and-how-can-i-fix-it
the issue is with the cable provided by Pluggable. As my dock is past warranty I’m going to try a replacement cable (from Cable Matters, equivalent specs to Pluggable) and see if this resolves my issue.

Seeing as I’d previously reported this problem it would have been nice to get an alert about this finding, but no biggies, hopefully this is the final step in closing this topic for good :smiley: