Skip to content
FORUM DRIVERS

I suggest you ...

← DisplayLink Feature Suggestions

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.

2,747 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
TOULEMONDE shared this idea  ·   ·  Report…  ·  Admin →
completed  ·  AdminAlban Rampon (Senior Product Manager, DisplayLink) responded  · 

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

Show previous admin responses (17)

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • stephen parrish commented  ·   ·  Report

    DisplayLink driver v4.3 beta 4 followed directions. Not working. No option in accessibility.

  • Eamon commented  ·   ·  Report

    Bottom line is DL built their drivers to work with what was normal at the time. DL isn't part of Apple so do not know their roadmap. Just because an OS releases a beta, 2 months in advance mean anything to your development cycle. Remember, it's in beta and not the fully released final version, so why would you digress on your own development cycle for something which isn't final. 3 blind mice comes to mind. So yes I totally agree with @Nobody. Like I have said previously, a bit of understanding of the development world will help you through this issue. You notice the pain less because you understand the numerous decisions that would have had to occur for us all to be at this moment in time. Also, Apple are the ones who changed the game. Not DL. Like I have previously said there is no fix. There will never be a fix. This Airplay thing is a joke and you all think it's a step forward. I could have gone on amazon or ebay and got an airplay dongle for less that £5 which did the exact same thing. So the direction of travel would make anyone who understands the situation that there will not be a fix to this.

    Apple wants you all to buy new macs with mac external peripherals. That's the truth behind this move. Also bear in mind, Final Cut pro doesn't work on the new OS either and that's an Apple Product. So calm down on DL, they're going to have to pull more than a rabbit out of the hat.

  • Eamon commented  ·   ·  Report

    totally agree with @Nobody

  • Anonymous commented  ·   ·  Report

    It is May 16 already. Its been so long since I waited for an update. I regret buying Pluggable USB-C. The purpose as to why I bought this product is so that I could easily have one chord that allows me to charge my MacBook Pro and to simultaneously use multiple monitors. Now, this functionality is no longer viable with the new update. Please let me return my product.....

  • Anonymous commented  ·   ·  Report

    I have an HDMI Samsung monitor that no longer works due to this debacle.
    I am going to get a
    3-in1-Thunderbolt-Mini-DP-Display-port-to-HDMI-DVI-VGA-Adapter-Cable-for-MacBook
    I cant see why it won't work, has anyone tried this? Email steve.brine01@gmail.com

  • Nobody commented  ·   ·  Report

    Anonymous, I don't work for DisplayLink far from it. I simply know how such a device works as I'm a kernel developer. Those laying the blame at DL's door are being disingenuous. The point about not installing kernel drivers for this type of functionality is flawed at best. If it were userland functionality then the lag would be unusable due to kernel context switching. The API that DL uses isn't exported to userland so you can't use it but it is a supported Apple API. An API they broke in 10.13.4.

  • Tom Delos Reyes commented  ·   ·  Report

    Everytime I unplug and plug the USB displaylink, I need to uninstall and reinstall because it goes back to clone mode. If I need to unplug my computer, what is the steps so I don't have to uninstall and reinstall the driver. Thanks.

  • Anonymous commented  ·   ·  Report

    The new AirPlay option via DisplayLink driver v4.3 beta 3 isn't working for me. Have additional users been reporting the same concern?

  • I hate this commented  ·   ·  Report

    Today I missed out on a good investment opt because I have 15 blank monitors. Full moon is coming up and I need to be able to have my 16 screens on so I can trade effectively. You've already cost me $10M and my girlfriends are starting to notice. Better fix this by next full moon effect or as soon as I get back from my trip to the Maldives I'll have my lawyer call your people. Geez

  • Markus commented  ·   ·  Report

    It is quite clear now that DisplayLink had been using macOS interfaces in a way they were never intended to be used by Apple. To make things worse, they either didn't care to inform their customers when they knew that 10.13.4 would break their products, or didn't test against the betas in the first place.
    So even if they manage to pull another hacky working solution out of a hat, it's just a matter of time before that breaks again.

  • Anonymous commented  ·   ·  Report

    The Air Display does NOT Work.
    I have 3 Monitors external on the dock. 3 of them are Dell U2717 and Dock worked fine on 13.3 but not on 13.4. So Not Monitor issue. AirDisplay Beta thing Will not work. It works for HDMI connection. The two Display Port ports will only mirror the main laptop display. Plugging in and unplugging does not work and i did follow the steps in the linked document. So this is still not work around nor working version.

  • Anonymous commented  ·   ·  Report

    pretty sure that the user @nobody works at displaylink and is trying to throw apple under the bus. This is bad on both parts.

    @DisplayLink - please update us on the progress. We know everything is broken and you're working on. What we don't know is if you are still working on a workaround, testing a workaround, working on the next apple update instead... etc.. Posting your progress would be much appreciated, thanks!

  • andrew commented  ·   ·  Report

    Will, I take it you haven't been waiting since April 1st for a fix! Technically Apple's upgrade broke the functionality, but they do give 3rd parties like DisplayLink several months to test OS upgrades and report issues before it goes live! #ABallWasDropped

  • Joe D commented  ·   ·  Report

    @grundle Interesting observations and comments there. I have to agree with the comment about removing the ports. This is causing everyone to have "dongle city" just to use a "mobile" solution. My opinion is that removing all these ports has, for now, kinda ruined the whole mobile capability because we all want a condensed and simply environment to work and not a bunch of dongles hanging out when we are sitting at a table in Starbucks trying to work. It's embarrassing to be honest.

    I somewhat agree with the API portion. Again, Apple did break the API, or simply put, changed it but these companies are supposed to be testing with Betas etc so they had the time to identify and fix it. My thought is that they didnt even bother with 10.13.4 because they clearly cannot fix it which proves they never even tested with the beta OS and I know that it doesn't work on 10.13.5 because I have it installed and it still is broke so God knows how long we are all stuck using 2-3 dongles just to get our monitors to work.

  • grundle commented  ·   ·  Report

    Okay, have to add my two cense to the conversation. First off, Apple is to blame for removing all of the other display standard plugs from their laptop. They should have at least left a display port and not forced us all to deal with everything over USB. Sure USB C is great and all, but we've lost the "it just works" expectation with Apple products. But I'll also blame DisplayLink in engineering a product that relies on installing 3rd party drivers instead of using the built-in driver support and features of USB-C. It's the difference in mentality between Mac and PC. PC world, it's not uncommon to install a driver first, in Mac world, you didn't (past tense) typically worry about drivers. And DisplayLink isn't the only vendor dealing with issues around the changes that Apple made to their graphics libraries... Shoot, even the iPad display extension apps are having the same issue... and are currently using the "AirPlay Workaround". It's going to take work from both entities to make it work.

  • Nobody commented  ·   ·  Report

    Anonymous, the one and only way to offer the DL functionality is to use the broken API. But it’s broken so Apple needs to fix it. The ISP analogy is more than adequate here.

  • Joe D commented  ·   ·  Report

    @nobody, that question doesn't make any sense, you are now grapsing at straws. If your ISP cuts you off then you've either not paid the bill or doing something against the user agreement. "A+' for effort. Look, we clearly are at odds over this so we don't need to sarcastically bash each other (mostly my rude behavior here) but you gotta see that after 2 months, the blame has to be on DL to want their product to work with an OS. Point being, if you want to offer your product to a group of people, there are guidelines (APIs) you must adhere to and DL has not changed their API for this particular issue even if apple has "broken" the API as stated by your previous post? Again, that was a more civil question and not to be taken as sarcastic or condescending.

  • Nobody commented  ·   ·  Report

    Anonymous, if your web browser stops working because your ISP cuts you off then do you blame the browser developer for not getting web pages to load? This is the exact same siruation you’re blaming DL for.

  • Joe D commented  ·   ·  Report

    @nobody. Blame Apple all you want. There is a reason OSes have betas. It's so companies like DisplayLink have time to make sure their stuff works when the OS goes live. So you can say it 's Apple all you want but at the end of the day, DL has had almost 2 months (and more if you include beta testing) to fix this issue so the blame is now 100% on DL and not Apple but you get an 'A' for effort!

    What is your excuse for the confirmation by me that this is STILL an issue in 10.13.5? crickets....

  • Joe D commented  ·   ·  Report

    Not to spoil the party but I just tried this routine with the beta 3 driver for displaylink in the upcoming Mac OS currently in beta 10.13.5 beta 4 and I confirmed that this process DOES NOT WORK as a workaround so I sure hope they have a solution when the next OS comes out!

1 2 … 46 48 50 … 104 105

DisplayLink Feature Suggestions

Categories

Feedback and Knowledge Base

(thinking…)