Rog

My feedback

  1. 2,429 votes
    vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1485 comments  ·  DisplayLink Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

      Update: June 20th
      Dear DisplayLink macOS users,

      Installing macOS 10.13.4, or newer, will cause DisplayLink connected displays to go blank after the OS update when using DisplayLink driver v4.1. Extended displays continue to work as expected in macOS 10.13.3 and below.
      Functionality such as Ethernet and audio, where implemented, is unaffected.

      DisplayLink driver v4.3 beta 5 currently provides an interim solution with one extended USB display (720p or 1080p) on macOS 10.13.4, 10.13.5 and 10.14 first developer previews, using Apple AirPlay® on machines with that feature. All additional DisplayLink screens will be cloning the primary display.
      An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode: https://support.displaylink.com/knowledgebase/articles/1854724
      DisplayLink driver v4.3 beta 5 is available from http://www.displaylink.com/downloads/file?id=1169

      Our team have made further progress towards finding a solution which would restore full extended display support for multiple DisplayLink displays in a future release of macOS. As…

      Rog commented  · 

      I had the problem where airplay could not connect to display link running 10.13.4.
      It was solved by turning off the firewall and restarting (you have to leave the firewall off).
      Unacceptable that you have to compromise the security like this to get it to work but as the thunderbolt ports on my iMac are fried it’s my only option.
      I hope this helps some people

      Rog commented  · 

      I have been having the issue that the monitor will only mirror and the "airplay could not connect to device" error message.
      This is partially fixed by turning off the firewall and restarting.
      Running macOS 10.13.4.

      Hope this helps some of you.
      Still unacceptable that this work around is required.

    Feedback and Knowledge Base