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.
Update: November 5th
Dear DisplayLink macOS users,
DisplayLink has worked for many months to maintain support for its users during the transition from macOS High Sierra to Mojave. While functionality such as Ethernet and audio or charging, where implemented, is unaffected on all releases, display connectivity has been limited on macOS releases 10.13.4, 10.13.5 and 10.13.6.
macOS 10.14 Mojave with DisplayLink driver v5.0.1 allows you to run up to 4 extended displays with now optional clamshell and mirror modes. Support for rotated displays is also improved.
DisplayLink driver v5.0.1 is applicable to macOS 10.14 only.
Driver v5.0.1: http://www.displaylink.com/downloads/file?id=1257
Should you experience black extended display(s) with only mouse cursor on 10.14. We recommend you use macOS 10.14.2 Beta 1 or newer. We have also left DisplayLink driver v4.3 Beta available to force an AirPlay extended display on these machines if you cannot update to 10.14.2 Beta 1 with DisplayLink driver 5.0.1.
Driver v4.3 Beta 6: http://www.displaylink.com/downloads/file?id=1184
Users on High Sierra 10.13.4-10.13.6 should install v4.3.1 for one extended USB display with multiple resolutions through an additional menu via Apple AirPlay.
An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode.
DisplayLink driver v4.3.1 is applicable to Mac OS X 10.12 and macOS 10.13.
Driver v4.3.1: http://www.displaylink.com/downloads/file?id=1251
We thank you for your extended patience, we continue to value your feedback and support.
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?
@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!
@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 :(
@rostow Your right I got it to work by using Peter's method I'm on mac mini late 2014
@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.
@Antonio Esnaurrizar I didn't have to navigate anywhere in terminal - just execute from where you are.
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).
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."
@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?
@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?
@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
@keegan: Thanks for replying. I can't believe they haven't been able to fix this. This is ridiculous.
Sorry I mean (10.14.1)
@Antonio Esnaurrizar yes I have (10.4.1 beta 3). No love on my 2018 MBP. In fact it was causing kernel panics.
Has anyone tried the last 2 drivers (5 and 5.0.1) with the latest mojave beta (10.14.1)?
@Alban Rampon; still no 2018 model fix, but I lost my patience.
I've had a MBP for months now and have not been able to properly use multiple screens once.
Our offices will switch to Elgato docks from now on.
Ok, so I might have a fix for you guys. I am on a Macbook Air 2017. I had DisplayLink working for about a week on Mojave with driver 4.3.1 then 5, but it just randomly started showing only one dark grey and one black screen even though they recognised that they were plugged in. On a whim I just tried rebuilding the kext cache from the terminal - "sudo kextcache -i /". It complained about system policy authentication failure, at which point go to System Preferences > Security & Privacy and then click the Allow button again. Restart and you might get your display back!
Joe D commented
Holy cow you guys are a DISASTER! I am sure everyone is gonna continue to point the finger at Apple but after 11 mos between each of the last two OS releases, DisplayLink has had PLENTY of time to fix this and clearly is unable! (if you understand development, you will not dispute this)
This has to turn into a class action suit at some point if it hasn't already. I mean this is #@%@#% ridiculous in my opinion! I have worked with plenty of hardware and software developers in my career and this is by far the worst I've ever seen. DisplayLink is clearly very INCAPABLE of solving this. I have to say I am officially bailing after trying to be as positive and patient as possible during this all but this dongle city that I have attached to my Mac is embarrassing and frustrating.
You should be ashamed and embarrassed of yourselves!
@Dale I recommend you promptly bail on Displaylink. It'll likely never be resolved. Back in July, after waiting since April for a resolution, I decided to buy this http://www.matrox.com/graphics/en/products/gxm/dh2go/digital_me/ I've been humming along with two peripheral monitors since. I also have a mid-2010 system for work. I just check this thread for curiosity on what I should do with my old EVGA adapter hardware. Looks like they're going to be recycled.
Who Cares commented
I have users also experiencing the same issues where the display recognizes that there is a feed that should be going to it but nothing outputs on the display. After you pretty much abandoned10.13.4 and up this is unacceptable. There was hope for months that this would be the glorious fix and now that neither solution really works, my end users are just out of luck. It would be nice if you could get this sorted since this has been an issue for a good part of this year. My users are on 2017 MacBook Airs.