Black screens on macOS High Sierra 10.13.4+ and Mojave 10.14 Early Previews
The driver (DisplayLink Installer 4.1.11) doesn't work anymore withe macOS High Sierra bêta 10.13.4 (17E139) and newer.

Dear DisplayLink macOS users,
We are pleased DisplayLink 5.0.1 driver for macOS enables multiple extended display support on the latest Apple macOS 10.14.2 with additional features (clamshell and clone). We continue our strong support for the Mac platform and are working on delivering future updates with further performance improvements.
Driver 5.0.1: https://www.displaylink.com/downloads/file?id=1257
If your DisplayLink enabled device does not seem to work on 10.14, this is most likely due to the OS blocking our kernel extension. Please ensure our kernel extension is enabled by the OS as described in our FAQ: https://support.displaylink.com/knowledgebase/articles/1188004
Should you still miss extended displays on latest macOS with latest DisplayLink driver, please create a support ticket so your particular case can be investigated. Here is how: https://support.displaylink.com/knowledgebase/articles/755301
Due to changes in 10.13.4-10.13.6, it is not possible to enable DisplayLink extended displays, except one using Apple AirPlay. If your Mac is from 2011 running 10.13.4-10.13.6 and can’t update to macOS 10.14, you should remain with DisplayLink macOS driver v4.3.1 to enable one extended USB display using AirPlay, with additional displays cloned. An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode: https://support.displaylink.com/knowledgebase/articles/1854724
Audio and Ethernet functionality, where supported, stays unaffected in all versions.
We thank you for your feedback on DisplayLink products that helps us further improve our product offering.
Kind regards,
Alban
-
Keegan commented
@Antonio Esnaurrizar yes I have. Still the same issues.
-
Julian R. Vera commented
I installed the 5.0.1 Version and now my Mac doesn't allow me to go back to 4.3...
Is there any suggestions? I would highly appreciate you!
Julian R. Vera
-
Antonio Esnaurrizar commented
@Keegan: Have you tested Mojave Beta 5 on MBP 2018?
-
Hohentho commented
I am on MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports) with macOS 10.14 and have still only black and grey screen. Unfortunately @Peter P solution did not work for me. Any other ideas?
-
Anonymous commented
Hi everyone, seems like I have the same problem as you after updating my macbook air to Mojave : my mac does not send the signal to the videoprojector via HDMI.
I tried the sudo kextcache solution, but I don't have the same answer as you did : I have my kernelCache ID. That's all.
Is there nothing to do, but wait for a new udpate ... ?? -
Anonymous commented
So, does this mean that if I download and run macOS 10.14, that Mojave driver v 5.0 will allow me to run two additional displays with that OS?
-
rostow commented
@Peter P I have been doing some tests rebooting and shutting down the laptop a few times and the fix you found is still working for my MacbookAir Mid-2013. I will report here in case the black/grey screen comes back indicating what could have caused the issue. So far it´s working like a charm!
-
Keegan commented
@Antonio Esnaurrizar Nope. the `sudo kextcache -i /` trick does not work on my 2018 MBP. I also just updated to Mac OS 10.14.1 Beta 4 (18B67a) and I'm still getting the back screen with cursor :(
-
Katie commented
@rostow Your right I got it to work by using Peter's method I'm on mac mini late 2014
-
Peter P commented
@rostow I'm guessing it's a temporary fix, and that after a reboot/hibernate the kext cache screws up in some way. But I've been using my Macbook without issue for a couple of days now.
-
Peter P commented
@Antonio Esnaurrizar I didn't have to navigate anywhere in terminal - just execute from where you are.
-
rostow commented
I confirm that I have just implemented the method described by @Peter P below and it WORKS PERFECTLY. I'm on a MacbookAir Mid-2013 on Mojave 10.14.
Thank you @Peter P for such a simple and wonderful solution. As described by him, you simply need to type "sudo kextcache -i /" in the terminal (from any folder) and when the process is finished, you can see an error message indicating some authorization problem due to a system policy. Go to System Preferences > Security and Privacy, and in the bottom of the "General" tab you will see a message asking you to allow DisplayLink software. Click on "Allow" and after a restart the displays will be working just fine. I don't know whether this is a permanent fix or the grey screen bug will happen again, but so far is working well (I just got it working a few hours ago).
-
Peter commented
So I've installed the v4.3.1 release for my DIsplayLink 0x4300, which was released on Oct.9th, 2018, and still no luck with my monitors.
From my previous post:
"I have 2 Display Link USB 3.0 to DVI Adapters (Product ID 0x4300 Version 36.07) connected to my Mac Pro Mid 2012 (via the native USB front ports), I have just updated from Sierra to High Sierra 10.13.6 and I cannot get the displays to function.
I have installed latest appropriate driver v4.3, and have also gone to the Security Preferences and "allowed the App to control my computer" under the Privacy tab, and have also added exemptions for the DisplayLink User Agent, the DisplayLink Manager in the FIrewall, all as recommended in the FAQ.
I have an ATI Radeon HD5770 video card installed that supports up to 8 monitors and am currently using their Web Driver as opposed to the Default macOS Graphics Driver.
Before updating the OS everything was working perfectly fine."
-
Antonio Esnaurrizar commented
@Peter P: Did you just open the terminal and run this command?"sudo kextcache -i /. Or did you navigate into the DisplayLink Folder and then ran it?
Thanks. -
Antonio Esnaurrizar commented
@Peter P: I forgot to mention I'm having this problem on a MBP 2018. I will give that a shot. Thanks.
@Keegan: Have you tried Peter's method on your 2018 MBP? -
Peter P commented
@Antonio Esnaurrizar Yes, I was able to get my displays showing (after a month of a black and grey screen) on a Macbook Air 2017 with Mojave 10.14 (18A389) and driver 5.0.1 using the method I posted below
-
Antonio Esnaurrizar commented
@keegan: Thanks for replying. I can't believe they haven't been able to fix this. This is ridiculous.
-
Keegan commented
Sorry I mean (10.14.1)
-
Keegan commented
@Antonio Esnaurrizar yes I have (10.4.1 beta 3). No love on my 2018 MBP. In fact it was causing kernel panics.
-
Antonio Esnaurrizar commented
Has anyone tried the last 2 drivers (5 and 5.0.1) with the latest mojave beta (10.14.1)?