View Single Post
Old 06-26-2026, 09:01 PM   #1
tvalinho
Junior Member
 
Join Date: Jun 2026
Posts: 1
Exclamation Dell UD22 USB ports stop working on MacBook Pro M1 Pro after macOS Tahoe update

Device: MacBook Pro 14" M1 Pro
macOS version: Tahoe 26.5
Accessory: Dell UD22 Docking Station (DisplayLink technology, latest DisplayLink Manager driver installed)

Problem description:
After updating to macOS Tahoe, the USB ports on my Dell UD22 docking station stopped recognizing any connected devices. This same dock worked flawlessly with this same M1 Pro MacBook Pro on previous macOS versions, and it still works correctly with Intel-based Macs. The external display, connected via DisplayPort, continues to work normally — only the USB functionality is affected.

The issue has been intermittent: a clean reinstall of the DisplayLink driver plus a Safe Mode boot restored USB functionality for about one month, but it then stopped working again with no configuration changes on my end.

Troubleshooting already done, without permanent success:
1. Clean uninstall using the official DisplayLink cleaner tool, followed by a fresh install of the latest DisplayLink Manager version
2. Verified and enabled Screen Recording and Accessibility permissions for DisplayLink Manager in System Settings
3. Safe Mode boot followed by a normal restart (worked temporarily)
4. Power drain reset on the dock (fully disconnected for 2+ minutes)
5. Updated macOS Tahoe to the latest available version (26.5)
6. Tested the dock on a Windows machine (Dell Latitude) — the Dell firmware update utility shows the dock as "Undetected" with a generic serial number, despite power and LED working normally

Since the dock works fine with Intel Macs and worked with this same M1 Pro before the Tahoe upgrade, this points to a compatibility regression between macOS Tahoe and DisplayLink-based docks, rather than a pure hardware fault.

Has anyone experienced this same recurring pattern (works → breaks → temporary fix → breaks again) on an M1 Pro with Tahoe? Is there a known fix that addresses the root cause rather than just temporarily resetting it? Happy to provide additional details or system logs if useful.
tvalinho is offline   Reply With Quote