I suggest you ...

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
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    TOULEMONDE shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    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

    2036 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • AriesLian commented  ·   ·  Flag as inappropriate

        so does my laptop! mirror is not a solution!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!it's nothing!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

      • AriesLian commented  ·   ·  Flag as inappropriate

        We all got the same problem, and i just bought it for 1 day!!!!!!!!!!!!!!!!!!!!!!!!!!!!

      • a user since IIci commented  ·   ·  Flag as inappropriate

        Not correct. This problem (go blank) exists from 10.13.3, and it keeps even with the 4.3 beta March 30 installed on 10.13.3 with my MacbookPro. I already reported to Apple two times. -- from a user since IIci

      • AriesLian commented  ·   ·  Flag as inappropriate

        We need an ETA on a fix!!! keep the line.!!!! 我刚买的你就给我不能用,我要退货.I'll return it back!!!!Please give us a dead line!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!花Q!!花QQQQQ!!!!

      • Anonymous commented  ·   ·  Flag as inappropriate

        At this point, this predicament is quite embarrassing. The operating power of countless businesses are being crippled.

        A tweet or even rough estimation would be infinitely more valuable than a generic response.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Unless I am missing something Clone mode only displays same screen. The whole point in adding a USB Display is to have multiple display information ie Spreadsheet on one screen
        email and another program on the other.. This needs to be fixed ASAP Unless I screwed up install ...

      • Anonymous commented  ·   ·  Flag as inappropriate

        I’ve spent ninety minutes on the phone earlier today with Apple tech support attempting to downgrade my MacBook Pro from v10.13.4 to v10.13.3 only to find out that it’s practically impossible outside of completely reimaging the machine and reloading all of my applications and data.

        Placing the blame for this problem on Apple is unacceptable.

        I respectfully but strongly request that you correct this issue immediately and that you let your users know when a resolution will be forthcoming.

      • Ryan commented  ·   ·  Flag as inappropriate

        We need to know if this is a day or two ETA or are we looking at weeks plus? We are severely hampered by this.

      • Jerome commented  ·   ·  Flag as inappropriate

        Cloning is not a viable option. This is essentially rendering this expensive machine useless. We need a fix asap...

      • juliao_i commented  ·   ·  Flag as inappropriate

        Can you please provide an update on the issue and an ETA? This is ongoing since last week and is damaging the performance and experience working with your hardware. A generic statement does not work at this moment, please provide updated information.

        Thanks

      • Anonymous commented  ·   ·  Flag as inappropriate

        i guess they're afraid to give us even a daily update...i.e. we're working on it and hope to have it in a few days....etc. We all live and die by their hardware

      • Brian C commented  ·   ·  Flag as inappropriate

        Does little good to find this out after the update is installed. Fix needed asap! It peeves me to no end to find how reliant I am on your hardware!

      • Vince commented  ·   ·  Flag as inappropriate

        Looking forward to a fix! This is pretty inconvenient. For anyone interested, I was able to change my resolution on my cloned display by using SwitchResX. It's a workaround, but let's me at least customize my seondary display.

      • Anonymous commented  ·   ·  Flag as inappropriate

        This is the kind of bug that will force me to replace your equipment and not purchase additional equipment as we onboard people if not patched quickly. This should've been resolved long before 10.13.4 was publicly released, especially since it has been known since February. We'll give you a few days and then we will be forced to move to other solutions.

      Feedback and Knowledge Base