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
-
Anonymous commented
Is Apple trying to enforce specific vendors devices going to leverage on `dominant position` if so.. let us open a class action.
As far as I understood many 3rd parties devices have been affected. What about Apple certified devices (if any) ?
-
Lorenzo commented
How can we believe that the issue has the highest priority given that it was reported in January on beta versions of MacOS 10.13.4 ? You guys ignored it for months, and NOW it is a high priority? Or maybe the issue cannot be fixed on your end and you are hoping that Apple resolves it for you? Goodluck with that.
Do I need to buy a different product and ditch DisplayLink forever? This is completely unacceptable. -
Anonymous commented
Discussion in a room not so far from this board:
"Hey guys! We destroyed our product as we didn't manage to test the drivers with the BETA OS.
Don't worry though! We can solve it! Go to the place were our PAID customers are complaining and blame there Apple! No need to work if you blam someone else for your mistakes ;)"Aaaaaand done.
-
Jai6476 commented
@Felicia When 10.13.4 was released as beta a long time before being released to the public one would think testing with current products would be done.
-
Anonymous commented
Like many of you, I also posted on the Apple Support Forums. I was told to post this on DisplayLink as we would probably get better results and feedback here. https://discussions.apple.com/thread/8343936
That said, I've been cruising around the Apple Forums and this has been posted MANY times, so hopefully it will be resolved soon.
As a work around and suggestion, I'm using an HDMI to thunderbolt 3 adapter from monitor directly to my MacBook and then using DisplayLink latest Beta driver to mirror my MacBook screen. This at least gives me dual monitors for now. Here's the link for the Thunderbolt cord I'm currently using until Apple and DisplayLink are both friendly again: https://www.amazon.com/CHOETECH-Braided-Thunderbolt-compatible-ChromeBook/dp/B077VPDNL7/ref=dp_ob_title_ce
PS: I'm NOT trying to promote anything or sell, just trying to help with suggestions. Hope this is helpful.
-Brian
-
Leif Hanson commented
Day 4, can has monitor?
Update would be great admins. kk bye.
-
Felicia commented
So funny, all the iDiots blaming DisplayLink because of a feature that APPLE broke! Apple screws you, yet you whine like bitches about DisplayLink. Suck it up, snowflakes...
-
Jon Coley commented
Ok so I did what others said and posted this in the Apple Forum but new to posting in any communities and not sure how to get what I posted enough traffic for Apple to notice? Here is what I posted in Apple's community. Any suggested edits would be greatly appreciated
-
Sam Gregory commented
You can do this DisplayLink! I believe in you!
-
David Wimsey commented
You didn't test in the beta version of the OS update or the public betas of the update didn't have this problem?
-
Anonymous commented
Can you guys know the ETA for it?
-
Scripting Guy commented
DisplayLink devs: I wish I could buy you a beer. As a developer and admin myself who has to deal with "It's impossible this has anything to do with Apple" hordes on a daily basis I know how shitty this situation is.
I sincerely hope you'll catch a break the next few days. Godspeed my friends.
-
Jon Humphrey commented
For those of us with multiple monitors that have an hdmi connection, I highly recommend connecting directly to the hdmi port on your computer AS WELL as the usb port to the DisplayLink! This has temporarily resolved some of my issues while we're waiting!
-
MAGJ commented
I would add a few word in support of DisplayLink now.
1) Why is this Displaylink's issue to own? The Displaylink system was validated on 10.13.3. Anyone choosing to update to a new version of the OS was updating into an unvalidated configuration. In my world, we don't do that and expect all functionality to be preserved. In any mission-critical environment, one shouldn't update without testing. I'm glad they're working on a fix to ensure that their product line remains relevant for future OS releases, but no-one can say that the DisplayLink solutions do not do exactly what they were bought to do.
2) Why is this not Apple's issue to own? Why should an OS developer push a software update that causes such problems with 3rd party devices, without a warning that substantial changes are being made that may cause 3rd party solutions to lose compatibility? Why does Apple not provide a rollback mechanism for exactly these type of situations? The change that broke DisplayLink was not DisplayLink's, but Apple's. The conclusion has to be that Apple products become unsuitable for mission-critical applications.
Yours in ongoing multimonitor joy thanks to a realistic approach to managing OS updates...
-
Sheldon commented
“For those with an Apple developer ID, DisplayLink suggests reporting the issue to Apple, referencing existing bug ID #37385102 to help raise the priority of the issue:
https://developer.apple.com/bug-reporting/” -
AriesLian commented
To the last anonymous: I paid for that, is this enough?
-
Anonymous commented
Hey user below...
A stereotypical Apple user here...
Is there any case that you work for DisplayLink?
Because in my organization we did already bought otehr adaptors and they do work like charm.
So either you are a stereotypical anonymous displaylink employee or as an Admin you have no idea what's your tasks.Kind regards,
Stereotypical Apple user who cares to work. -
Anonymous commented
I`gonna be fully relieved if you provide an ETA appropriately.
We users can do nothing but trust you. We don't know whether you hard work or not for fix indeed. -
Anonymous commented
As an admin in an organization that's massively affected by this issue. I can say with confidence we're impacted as much (and much likely much, much more) than any other poster here. I came here to see if there were any updates. With that being said....
The commenters on this thread are the most whiny, entitled, stereotypical apple users imaginable. What the h3ll is wrong with you people? Are you taking crazy pills?
Apple broke stuff. Stuff that has worked for ***years***! No warning of any sort from them about massive changes in a "minor" os update.
Do just a little bit of research and you'll find that basically every other alternative display product that worked on mac is now broken. Duetdisplay, external thunderbolt graphics on older macs, and everything like that. It all used to work, and now doesn't with the new OS update. And this is Displaylinks fault?!
Blaming Displaylink is ridiculous. They've been open about this issue in the beta thread for months. I sincerely (desperately!) hope they can find a workaround, but for the time being if everyone here shouting at Displaylink to fix things would go and post on the Apple forums to demand that whatever was broken with this update get fixed, we might actually make some progress.
-
Anonymous commented
How I can flag as inappropriate the DisplayLink answer and behavior in this topic? This is the biggest joke ever, 5 days (and some weeks of beta os before...) and you cannot deliver even an Alpha version to make this work.
5 days and you are not giving an ETA.
5 days of NOTHING!You are the biggest joke in history! Our company is having serious productivity issues with your lack of knowledge of solving problems and your unbelievable statements that suggests people and especially developers to stay in an older OS version when the newest one solves critical security issues!
Jokers!