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
-
Jason commented
Here is an alternative. A little bit pricey, but it is plug and play no drivers to worry about, or future issues. https://www.amazon.com/StarTech-com-Thunderbolt-Dock-Delivery-Windows/dp/B078PLPSTV/ref=sr_1_1?ie=UTF8&qid=1523292608&sr=8-1&keywords=Thunderbolt+3+Dual-4K+Docking+Station+for+Laptops+-+Mac+and+Windows+-+85W+Power+Delivery
-
Parker Bradshaw commented
Need this functionality.
-
Kumar commented
My USB dock is completely useless until I get this functionality working.
-
Anonymous commented
keep me posted please
-
Anonymous commented
Keep me updated. Thanks
-
Ben Compton commented
Well I had to restore my box from a time machine backup... That cost me a whole day in productivity... Oh yeah and since my Windows VM was a bootcamp partition; it too is now gone... Luckily I had a backup of that as well... However, this is unacceptable... Everyone knows Apple releases updates to application devs way ahead of their releases... When is displaylink going to grow up and be a big boy company and sync their release cadences like the rest of the world?
-
Ryan commented
keep me updated
-
L commented
Keep me updated as well please
-
Formerly Productive commented
ugh productivity killer
-
Sander Hoogendoorn commented
Keep me posted please
-
Anonymous commented
Please inform me of any fix
-
Vj commented
@Eamon S +1.
Read people..
Unfortunately, at this stage, we are unable to give a dates for either a workaround or a complete solution. We will, however, update you on this thread as soon as we have further information to share. If you have left your email address accessible to us with your feedback (ticket, forum, suggestion), this email address will be added to a list dedicated to this issue.
-
Fran Gutierrez commented
any updates?
-
Anonymous commented
Please let me know once you've found a solution...
-
Anonymous commented
Please update driver asap! I do not have an option to restore my iMac to an earlier date.
-
LVS1008 commented
Please let me know once the fix is ready!
-
Anonymous commented
@Eric, that doesn't remove the responsibility of DisplayLink to find a solution. They new it for months and they just hoped that Apple will listen to them.
Once Ford said, if I was expecting from people to tell me what they want, I wouldn't build cards but faster horses...
Still Apple has an ecosystem we like it or not and if you want to ask 100-200&300 dollars from your clients to give solutions for that environment then you know how it works.
DisplayLink for me is 100% responsible for this chaos. 100%, not a single less. We do have a company with 75_ developers when 40 of them are with Macs and from today especially everyone was forced to update AND ALL of them now are unable to work. DL provided a joke for solution to clone a monitor instead.... Unbelievable things!!
We are now in a situation were we have to buy new docking stations but based on this experience we have to update ALL the docking stations, not only for developers because we don't trust any more anything that has to do with DisplayLink.
They knew it and they had to had find a reason to inform their PAID customers. Our IT department got 0 updates from this company on that matter before the release of the latest MacOS and this is a proof of luck of professionalism.
Never again DisplayLink.
-
Muhsin KOCAK commented
Process: Microsoft Word [1173]
Path: /Applications/Microsoft Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: 16.13 (16.13.18040408)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Microsoft Word [1173]
User ID: 501Date/Time: 2018-04-09 11:18:37.367 +0200
OS Version: Mac OS X 10.13.4 (17E199)
Report Version: 12
Anonymous UUID: AB8B64E6-1548-B91A-B23B-8362A9634941Time Awake Since Boot: 5000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFYTermination Reason: DYLD, [0x5] Code Signature
Application Specific Information:
dyld: launch, loading dependent librariesDyld Error Message:
Library not loaded: @rpath/COMBase.framework/Versions/A/COMBase
Referenced from: /Applications/Microsoft Word.app/Contents/MacOS/Microsoft Word
Reason: no suitable image found. Did find:
/Applications/Microsoft Word.app/Contents/MacOS/../Frameworks/COMBase.framework/Versions/A/COMBase: code signature invalid for '/Applications/Microsoft Word.app/Contents/MacOS/../Frameworks/COMBase.framework/Versions/A/COMBase'/Applications/Microsoft Word.app/Contents/MacOS/../Frameworks/COMBase.framework/Versions/A/COMBase: stat() failed with errno=1
Binary Images:
0x1044d7000 - 0x106404fff +com.microsoft.Word (16.13 - 16.13.18040408) <6904B328-DFDF-3CF4-8E35-612A973EDAF2> /Applications/Microsoft Word.app/Contents/MacOS/Microsoft Word
0x11078b000 - 0x1107d59df dyld (551.3) <AFAB4EFA-7020-34B1-BBEF-0F26C6D3CA36> /usr/lib/dyld
0x7fff52269000 - 0x7fff523fcff7 libsqlite3.dylib (274.8.1) <FCAD6A57-829E-3701-B16E-1833D620E0E8> /usr/lib/libsqlite3.dylib
0x7fff52757000 - 0x7fff52769ffb libz.1.dylib (70) <48C67CFC-940D-3857-8DAD-857774605352> /usr/lib/libz.1.dylibModel: MacBookAir7,2, BootROM MBA71.0176.B00, 2 processors, Intel Core i5, 1,6 GHz, 4 GB, SMC 2.27f2
Graphics: Intel HD Graphics 6000, Intel HD Graphics 6000, Built-In
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80CE, 0x4B3445384533303445452D45474345000000
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80CE, 0x4B3445384533303445452D45474345000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.77.37.29.1a7)
Bluetooth: Version 6.0.5f3, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0128G, 121,33 GB
USB Device: USB 3.0 Bus
USB Device: Internal Memory Card Reader
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Air, Apple Inc., 27.2 -
Chris commented
Any news on a working driver for 10.13.4?
-
mrzz commented
Almost every MacOS release causes some kind of issue with DisplayLink driver. Furthermore this issue is known for quite some time (at least 2 months) and it's critical as your workaround is insufficient and screen extension to other monitor is not working. You should either come up with something what is not broken with every OS FP release or rather focus on a different business.