Displaylink ceases to work in 10.13.4

[Wozzy]

JULY


Have you notice DisplayLink its now July. Your last beta was May.

When will we see a final release?

[stfm]

This is entirely on Apple. Pulling this shit on a point release is idiotic, since we won't be able to get the security updates without the damaging code. This happens all the time. Suddenly your printer or Wacom board doesn't work, and the makers refuse to rewrite the drivers for old hardware. I feel bad for the companies that suffer from Apples' poor programming ethics. A point release should never break anything, unless it's addressing a serious bug.

Apple has become much worse than Microsoft in this regard. Especially killing API:s for no apparent reason. In their mind you're on your own if you don't run all-Apple. Microsoft mostly kill their own products, which seems fairer.

[MC Ren]

Originally Posted by stfm

This is entirely on Apple. Pulling this shit on a point release is idiotic, since we won't be able to get the security updates without the damaging code. This happens all the time. Suddenly your printer or Wacom board doesn't work, and the makers refuse to rewrite the drivers for old hardware. I feel bad for the companies that suffer from Apples' poor programming ethics. A point release should never break anything, unless it's addressing a serious bug.

Apple has become much worse than Microsoft in this regard. Especially killing API:s for no apparent reason. In their mind you're on your own if you don't run all-Apple. Microsoft mostly kill their own products, which seems fairer.

Never had a problem with any accessory, etc with 5 macs I've owned, except with this BS display link issue. I'd hardly say this happens with Apple all the time. Maybe you are better off with sticking with microsoft products...

[Neo.aka.Darkman]

There is still no source code for 10.13.4. That's why DisplayLink can't move forward (I assume).

In 10.13.4 Apple made native support for external Videocards. But with this move they closed opportunity to use virtual Videoadapters such as DisplayLink.
So we all must wait till Apple releases source code for 10.13.4.

All we need is patience!

P.S. I do not work for DisplayLink

[stfm]

Originally Posted by MC Ren

Never had a problem with any accessory, etc with 5 macs I've owned, except with this BS display link issue. I'd hardly say this happens with Apple all the time. Maybe you are better off with sticking with microsoft products...

Well, that depends on what accessories you have of course. I have had to get rid of a Canon scanner, two printers and a Wacom tablet. This happens on Windows also, but not on a small automatically installed release. I've had macs since the early-mid 90's, only briefly owning Windows computers, and it's a fairly recent development. Windows blows in most other respects, and updates can certainly destroy your computer, but it's often possible to recover.

[AlbanRampon]

Update: July 4th

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 two 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.
The third developer preview of 10.14 has changed behaviour, as already exposed here. Displays using DisplayLink technology will be present in System Preferences - Display. The displays can be activated, and the mouse is visible, but otherwise the displays are black. Should you have already installed that OS version, simply use DisplayLink driver v4.3 beta 6 to force the AirPlay interim whilst the work continues.
We do not recommend using that OS version for extended desktop changes as it brings no benefit compared to previous versions. It also adds an undesired audio switch at reboot to be addressed.
When a new version brings value, we will obviously notify you.

Our team continues to progress towards a solution which would both restore full extended display support for multiple DisplayLink displays in a future release of macOS and defend that functionality in the future. As daily users of the technology ourselves, we truly understand how disruptive this loss of functionality affecting the full ecosystem can be. Despite getting closer to tell more about roll out, we stay unable to provide a time-frame or a date for release of this solution.
We will keep providing updates to this message.

Thank you for your extended patience. We appreciate your feedback and support.

[Poly]

Ok, the fix will eventually be released in Autumn/Winter...

While you are working on the "ultimate fix" could you please also address the annoying HDCP problem?

[AlbanRampon]

Originally Posted by Poly

While you are working on the "ultimate fix" could you please also address the annoying HDCP problem?

Hello Poly,
To implement HDCP properly on Windows 10 for indirect displays, this took the collaboration of Microsoft, Intel, DisplayLink and software player vendors (CyberLink for PowerDVD, Netflix and Amazon are just a few).
The manufacturer must be member of the DCP to have HDCP keys in the device. It's not enough that DisplayLink is.
Then you have to see which HDCP version as they have different DRM requirements...
HDCP 1.x is usually what is needed for 1080p playback, but on Windows 10, it required a GPU supporting HDCP 2.2.
It is in the roadmap, but building good foundations seems to be the right priority today.
Kind regards,
Alban

[slvrscoobie]

Originally Posted by AlbanRampon

Update: July 4th

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 two 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.
The third developer preview of 10.14 has changed behaviour, as already exposed here. Displays using DisplayLink technology will be present in System Preferences - Display. The displays can be activated, and the mouse is visible, but otherwise the displays are black. Should you have already installed that OS version, simply use DisplayLink driver v4.3 beta 6 to force the AirPlay interim whilst the work continues.
We do not recommend using that OS version for extended desktop changes as it brings no benefit compared to previous versions. It also adds an undesired audio switch at reboot to be addressed.
When a new version brings value, we will obviously notify you.

Our team continues to progress towards a solution which would both restore full extended display support for multiple DisplayLink displays in a future release of macOS and defend that functionality in the future. As daily users of the technology ourselves, we truly understand how disruptive this loss of functionality affecting the full ecosystem can be. Despite getting closer to tell more about roll out, we stay unable to provide a time-frame or a date for release of this solution.
We will keep providing updates to this message.

Thank you for your extended patience. We appreciate your feedback and support.

Glad I read this! I just upgraded to Mojave after seeing it was working. (edit) Im on the 1st public beta, (10.14 Beta (18A314k)) and it works just like it did in 10.13.

Only issue is the "displaysleep 20 (display sleep prevented by AirPlayUIAgent)"

Just turned off auto update to prevent further issues until this is squared up

Edit - well Auto updates WERE turned off but it Still auto updated to public beta 2 (10.14 Beta (18A326h)) while I went out to run my dogs. setting is back on now that its back. and I installed beta 6, but all I get is mirroring. Hmmm

Edit 2 - now it SEEs the displaylink - seperate display, but its struggling to get it to actually be separate.

edit 3: got it after unistall/reinstall

[donluca]

Alban, do you know which kernel extensions the displaylink drivers depend on?

I'm having an idea of rolling back some kexts to try and get the displaylink working as it was running on 10.13.3, to avoid having to format the mac and start anew.