HDMI Monitor Not Working After macOS 15.4 Update with Dell UD22 Dock

[rboerner]

Originally Posted by renan

Hello everyone,

I've been using DisplayLink with the Dell UD22 dock for the past two years, connected to my MacBook Pro M3 Max. My setup includes three Dell monitors: two P2418D models (connected via DisplayPort) and one P2219H in vertical orientation (connected via HDMI). The dock itself is connected to the MacBook via USB-C.

Everything has worked flawlessly until today, when I updated my system to macOS 15.4. After the update, the third monitor (the P2219H connected via HDMI) stopped working. The other two monitors continue to function normally.

I’ve already tried several troubleshooting steps, including updating the system further to macOS Sequoia 15.5, but the issue remains.

I rely on all three monitors for my work, and this issue is seriously affecting my productivity.

Has anyone else experienced this, or does anyone know of a potential fix?

Thanks in advance for your help.

For your reference, the Dell UD22 docking station combines two different technologies internally in order to drive the connected displays.

The two DisplayPort video outputs on the back of the dock are driven by DisplayLink technology.

The HDMI and USB Type-C video output are driven by the video output capabilities of the host computer.

Your description suggests that the two Dell P2418D displays connected to the dock's DisplayPort outputs driven by the DisplayLink technology are working properly.

Your description also suggests that the Dell P2219H display connected to the dock's HDMI output (driven by the video output capabilities of your host computer) is not working as expected.

If my understanding is correct, then the issue of the non-working display is not related to the DisplayLink component within the dock.

As a result, I would suggest:

- Ensuring your dock has the latest firmware update applied --> https://www.dell.com/support/product...k-ud22/drivers

- Contacting Dell directly for assistance

- Contacting Apple directly for assistance (since the issue appears to have occurred as a result of an OS update)