My feedback

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

      Update: September 12th
      Dear DisplayLink macOS users,

      DisplayLink has worked for many months to maintain support for its users during the transition from macOS High Sierra to Mojave. While functionality such as Ethernet and audio or charging, where implemented, is unaffected on all releases, display connectivity has been limited on macOS releases from 10.13.4 through 10.13.6.

      Users with access to Apple 10.14 Mojave previews released since 30th July confirmed full support was restored for multiple extended DisplayLink displays.
      We are performing wide scale testing of v5.0 beta released today against current and upcoming previews to release v5.0 upon general availability of 10.14.
      Driver v5.0 Beta:

      Users on High Sierra 10.13.4-10.13.6 should install the newly published v4.3 as the workaround to enable one extended USB display now supports additional resolutions.
      An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode.
      DisplayLink driver v4.3 released…

      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