Displaylink ceases to work in 10.13.4

[ralfonso]

I can confirm that DL 5.0 also works with upgrade to Mojave 10.14.

1. upgraded to Mojave
2. downloaded DL 5.0
3. ran uninstaller from 5.0 (and restart)
4. installed 5.0 (and restart)
5. plugged in dock, and it dual extended mode works
6. docked/undocked a few times and it continues to work.

Note: I had to do Steps 2-4 a few times.
1st time I did while docked.. this was unsuccessful.
2nd time i did while undocked, and only docked after install/restart and that worked for me.

[Pagany]

As an IT support in company that has like 100 MacBook Pro devices i can confirm the following. New drivers 5.0 are working on all models except on models from 2018, where we can see only black screen with cursor on extended mode. Previous models are working like a charm. Because we suggested our employees not to update Mac OS version 10.13.4 to 10.13.6 they were using old 4.3 drivers, when they did an upgrade to Mojave now all the old drivers worked like a charm as well. So my question is how come all the models are working properly except for the ones made in 2018.. Isnt software the same? How come the hardware can make such a difference in a device that is only passing through and not doing any hardware acceleration? And when can we expect fix for devices made in 2018?

[Pbowater]

Originally Posted by RainbowShooter

Everything back to normal for me on 10.14 Mojave using version 5.0 driver - we got there in the end, thanks!

Originally Posted by ralfonso

I can confirm that DL 5.0 also works with upgrade to Mojave 10.14.

1. upgraded to Mojave
2. downloaded DL 5.0
3. ran uninstaller from 5.0 (and restart)
4. installed 5.0 (and restart)
5. plugged in dock, and it dual extended mode works
6. docked/undocked a few times and it continues to work.

Note: I had to do Steps 2-4 a few times.
1st time I did while docked.. this was unsuccessful.
2nd time i did while undocked, and only docked after install/restart and that worked for me.

My experience as well, now I think about it, I undocked it before trying the second time using the 5.0 cleaner.