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.
Fix macOS V 10.13.4 DisplayLink 'only clone' issue
Displaylink, you've known about a problem with 10.13.4 and blank Displaylink displays for about two months. I see reports of problems with 10.13.4 beta in the support forums from early February. Why didn't you alert everyone BEFORE they upgraded to 10.13.4? It would be a huge hassle and disruptive to my business to go back to 10.13.3, so now I'm forced to lose my third monitor until you get this sorted out. Very poor support practice. You should have proactively notified everyone in advance of the 10.13.4 release!
An angry developer commented
This renders machines potentially insecure while we wait for an alpha build? Ya had a year to get the beta right. Sorry excuse for a hardware company, even sorrier on the software end. Worst cost cut ever was choosing your junk over real products with talented devs.
I got the same Problem after the official Update to 10.13.4.
Any solution is welcome, or do we have to wait for the next driver update?
are you going to fix this or what ? not being able to put your computer to sleep is bullshit, fix your hardware
Aaron W commented
10.13.3 work intermittently, at best, for me. Is an update scheduled anytime soon? DisplayLink has been money for me over the last couple of years, I'd hate to have to find a new solution.
Tony Williams commented
I also noticed that the kernel extension has a team ID of "3YQY62QM3" - which is nine characters. Every other KEXT in my list has a 10 character team ID.
I'm wondering if this is an error in a programmer's cut and paste?
It may be causing a problem in 10.13.4 as the kernel signing system is tighter.
fix it make it better less glitchy for mac os
The plist under /Library/LaunchAgents/com.displaylink.useragent.plist have a key value pair of Program: /Library/PrivilegedHelperTools/DisplayLink/DisplayLinkUserAgent.bundle/Contents/MacOS/DisplayLinkUserAgent
But the DisplayLinkUserAgent.bundle is not there so its failing (throwing a status code of 78 if you do a launchctl list.) I'm not sure if this has anything to do with 10.13.4 or not but I figured it was at least a start.
On 10.13.4, this breaks for me. I had intermittent issues with 10.13.3, but now it just won't work at all. (Also tried re-installing drivers.)
James R Maxeiner commented
Not quite my experience, but close. It works for a while, then several times closes out and reopens, and then closes altogether. This seems more common when using Internet.
is there any solution to this? how can we fix this so we can use the dual monitors again??
Tony Williams commented
This indeed correct. It breaks when you upgrade from 10.13.3 and an uninstall and install of the latest drivers makes no difference.
Pavel Katunin commented
Fix issues with Mac OS Sierra drivers
This is a major issue I've been fighting to fix. Please get a new driver to resolve the display issues in 10.12.4.
I am facing another but perhaps related issue which is a gigantic spike in CPU usage, when a MBA goes to sleep with the DisplayLink connected Display only showing a "Quartz" screen during screen saver mode.
Stephen Goddard commented
Would love to see this issue resolved.
Chris Duncan commented
Yes please SOLVE this issue