Displaylink ceases to work in 10.13.4

Sofla David · 08-11-2018, 09:33 PM

I'm seeing a lot of posts on the internet from people who had gotten it working under Mojave Public Beta 5, and then are experiencing the blank screen with cursor just like me after installing Mojave Public Beta 6. Especially those of us with the newer 2017/1018 MacBook Pros.

I hope I'm wrong, but it would appear that Apple broke it again with Public Beta 6.

I'm hoping DisplayLink can comment and either confirm, or deny that assumption soon so we can stop beating our heads against the wall trying to get it to work again or that Public Beta 7 comes out and fixes it again (one can hope).

I guess the big lesson here is to always come check the DisplayLink forums before installing ANY update. Unfortunately, I got my new 2018 MacBook Pro the SAME day that Public Beta 6 was released, so I wasn't even aware I was installing a newer Beta at the time, and didn't consider that the next Beta might break it again.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

08-11-2018, 09:33 PM	#11
Sofla David Junior Member Join Date: Jul 2018 Posts: 16	I'm seeing a lot of posts on the internet from people who had gotten it working under Mojave Public Beta 5, and then are experiencing the blank screen with cursor just like me after installing Mojave Public Beta 6. Especially those of us with the newer 2017/1018 MacBook Pros. I hope I'm wrong, but it would appear that Apple broke it again with Public Beta 6. I'm hoping DisplayLink can comment and either confirm, or deny that assumption soon so we can stop beating our heads against the wall trying to get it to work again or that Public Beta 7 comes out and fixes it again (one can hope). I guess the big lesson here is to always come check the DisplayLink forums before installing ANY update. Unfortunately, I got my new 2018 MacBook Pro the SAME day that Public Beta 6 was released, so I wasn't even aware I was installing a newer Beta at the time, and didn't consider that the next Beta might break it again.