Displaylink ceases to work in 10.13.4

[State_from_Jake_Farm]

Originally Posted by donluca

You'd better wait for DisplayLink to come up with a properly working driver.

LOL.. good one!

[displayhero]

after having the latest updates installed and continually waiting for a solution for over 6 months now... I now have my screens back and running. I do not have airplay so I have had a screen sitting here doing nothing for that amount of time.

donluca you are a god amongst men. thanks for posting those... there is NOTHING in the new updates beyond 10.13.3 that is noticeable for me.


i am happy to remain on this until a solution comes out.. but even so i dont think ill risk updating again after what happened.

[State_from_Jake_Farm]

Originally Posted by displayhero

after having the latest updates installed and continually waiting for a solution for over 6 months now... I now have my screens back and running. I do not have airplay so I have had a screen sitting here doing nothing for that amount of time.

donluca you are a god amongst men. thanks for posting those... there is NOTHING in the new updates beyond 10.13.3 that is noticeable for me.


i am happy to remain on this until a solution comes out.. but even so i dont think ill risk updating again after what happened.

Not updating eh? That's not very smart. Here's some of the security updates you will be missing out on..........


AMD

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to determine kernel memory layout

Description: An information disclosure issue was addressed by removing the vulnerable code.

CVE-2018-4289: shrek_wzw of Qihoo 360 Nirvan Team

APFS

Available for: macOS High Sierra 10.13.5

Impact: An application may be able to execute arbitrary code with kernel privileges

Description: A memory corruption issue was addressed with improved memory handling.

CVE-2018-4268: Mac working with Trend Micro's Zero Day Initiative

ATS

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to gain root privileges

Description: A type confusion issue was addressed with improved memory handling.

CVE-2018-4285: Mohamed Ghannam (@_simo36)

Bluetooth

Available for: MacBook Pro (15-inch, 2018) and MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports)
Other Mac models were addressed with macOS High Sierra 10.13.5.

Impact: An attacker in a privileged network position may be able to intercept Bluetooth traffic

Description: An input validation issue existed in Bluetooth. This issue was addressed with improved input validation.

CVE-2018-5383: Lior Neumann and Eli Biham

Entry added July 23, 2018

CFNetwork

Available for: macOS High Sierra 10.13.5

Impact: Cookies may unexpectedly persist in Safari

Description: A cookie management issue was addressed with improved checks.

CVE-2018-4293: an anonymous researcher

CoreCrypto

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6

Impact: A malicious application may be able to break out of its sandbox

Description: A memory corruption issue was addressed with improved input validation.

CVE-2018-4269: Abraham Masri (@cheesecakeufo)

DesktopServices

Available for: macOS Sierra 10.12.6

Impact: A local user may be able to view sensitive user information

Description: A permissions issue existed in which execute permission was incorrectly granted. This issue was addressed with improved permission validation.

CVE-2018-4178: Arjen Hendrikse

IOGraphics

Available for: macOS High Sierra 10.13.5

Impact: A local user may be able to read kernel memory

Description: An out-of-bounds read issue existed that led to the disclosure of kernel memory. This was addressed with improved input validation.

CVE-2018-4283: @panicaII working with Trend Micro's Zero Day Initiative

Kernel

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6, macOS High Sierra 10.13.5

Impact: Systems using Intel® Core-based microprocessors may potentially allow a local process to infer data utilizing Lazy FP state restore from another process through a speculative execution side channel

Description: Lazy FP state restore instead of eager save and restore of the state upon a context switch. Lazy restored states are potentially vulnerable to exploits where one process may infer register values of other processes through a speculative execution side channel that infers their value.

An information disclosure issue was addressed with FP/SIMD register state sanitization.

CVE-2018-3665: Julian Stecklina of Amazon Germany, Thomas Prescher of Cyberus Technology GmbH (cyberus-technology.de), Zdenek Sojka of SYSGO AG (sysgo.com), and Colin Percival

libxpc

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6, macOS High Sierra 10.13.5

Impact: An application may be able to gain elevated privileges

Description: A memory corruption issue was addressed with improved memory handling.

CVE-2018-4280: Brandon Azad

libxpc

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to read restricted memory

Description: An out-of-bounds read was addressed with improved input validation.

CVE-2018-4248: Brandon Azad

LinkPresentation

Available for: macOS High Sierra 10.13.5

Impact: Visiting a malicious website may lead to address bar spoofing

Description: A spoofing issue existed in the handling of URLs. This issue was addressed with improved input validation.

CVE-2018-4277: xisigr of Tencent's Xuanwu Lab (tencent.com)

[donluca]

Keeping your OS updated is crucial, especially if you do any kind of buying/selling/online banking.

If you just fool around with social networks and read news it's alright (almost) to lag behind updates, but if you do any serious work you're putting yourself at a huge risk.

I do critical work with my Macs and I *must* stay on the latest patches, this is why I hope DL will get a solution out soon.

[MC Ren]

Originally Posted by donluca

Keeping your OS updated is crucial, especially if you do any kind of buying/selling/online banking.

If you just fool around with social networks and read news it's alright (almost) to lag behind updates, but if you do any serious work you're putting yourself at a huge risk.

I do critical work with my Macs and I *must* stay on the latest patches, this is why I hope DL will get a solution out soon.

It's been 7 months, there is zero chance DL is releasing a fix soon, if at all.

[donluca]

Yeah, I'm starting to give my hopes up.

Luckily I've bought my DL device used and only payed like 20€*for it, but my issue now is that I need an alternative for it and can't really find any, as I have a 2011 27" iMac with two Thunderbolt 1/Displayport ports and AFAIK there's not way to get more Thunderbolt or video out ports for additional displays.

[russjr08]

Unfortunately this seems to be something that Apple really needs to work with DisplayLink on, it's not DL's fault that Apple heavily changed the graphics subsystem and doesn't have a way for DL to work around. For now, I'm just using the Airplay mirroring trick to have it mirror my MBP's internal display, and have the display mostly closed. It means I can't really use the internal screen as a work display, but I generally don't anyways.

Thank you for posting the downgrade image, I'll download it in case I really need to go back.

[AlbanRampon]

Update: July 30th
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.

Developers/users with access to Apple's fifth developer preview of 10.14 Mojave, released on 30th July, will see full support has now been restored for multiple extended DisplayLink displays where DisplayLink driver v4.3 beta 5 is installed. We are doing wide scale testing of v4.3 beta against this preview and will release a new driver upon general availability of 10.14.

Users of 10.13.4-10.13.6 should also use v4.3 beta 5 as it contains a workaround to enable one extended USB display (720p or 1080p). An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode.

Users on macOS 10.13.3 and earlier should remain for the time being with DisplayLink driver 4.1 to maintain full extended display functionality.

We thank you for your extended patience, we continue to value your feedback and support.

Kind regards,
Alban

[donluca]

Oh gosh... to update to the beta or not to update... does anyone know when Mojave will be officially released?

[pacmanbneNL]

Originally Posted by AlbanRampon

Update: July 30th
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.

Developers/users with access to Apple's fifth developer preview of 10.14 Mojave, released on 30th July, will see full support has now been restored for multiple extended DisplayLink displays where DisplayLink driver v4.3 beta 5 is installed. We are doing wide scale testing of v4.3 beta against this preview and will release a new driver upon general availability of 10.14.

Users of 10.13.4-10.13.6 should also use v4.3 beta 5 as it contains a workaround to enable one extended USB display (720p or 1080p). An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode.

Users on macOS 10.13.3 and earlier should remain for the time being with DisplayLink driver 4.1 to maintain full extended display functionality.

We thank you for your extended patience, we continue to value your feedback and support.

Kind regards,
Alban

I have the latest Beta of Mojave and uninstalled the DisplayLink beta6 and reinstalled the beta5 suggested in your comments and I still have the same problems. I have 2 monitors attached via my dell docking station and it only sees 1 monitor along with my laptop monitor instead of 2 dell monitors with a laptop monitor so my 2 dell monitors are mirrored

So unless I am missing something I don't see this a a workable solution

UPDATE: Turns out some Helpdesk monkey in our office changed a couple of docking stations to DELL WD15 which DisplayLink is not supported. When using the original Dell 1000 it functions as stated by DisplayLink Support I have full access again to my displays