Displaylink ceases to work in 10.13.4

[Alanant]

Just reporting that 10.13.5 Beta 4 does not restore original functionality. Workaround is effective though.

[Wozzy]

Originally Posted by Alanant

Just reporting that 10.13.5 Beta 4 does not restore original functionality. Workaround is effective though.

It won't. Apple purposely closed off the way DL was working as it was considered a security risk that could also be exploited in a negative way so they are not going to roll back the change.

[Poly]

Originally Posted by Wozzy

It won't. Apple purposely closed off the way DL was working as it was considered a security risk that could also be exploited in a negative way so they are not going to roll back the change.

That's interesting. Can you please elaborate further or provide a source?

[Wozzy]

Originally Posted by Poly

That's interesting. Can you please elaborate further or provide a source?

Not really, NDA. Thats about all I can say.

[paulgee31]

One downside of an Airplay solution is the likes of Netflix won't play on any monitor due to HDCP protection using Safari, so you make have to switch to Chrome.

[Poly]

Originally Posted by paulgee31

One downside of an Airplay solution is the likes of Netflix won't play on any monitor due to HDCP protection using Safari, so you make have to switch to Chrome.

That has always been an issue. HDCP never worked with DisplayLink, as far as I remember. Perhaps, some DisplayLink officials can give us some hope?

[DLguy]

Its really unfortunate I have a $200 USB hub and ethernet jack. If Apple did find a loop hole in the way DL works, there are ways to patch it. The easy way is to just terminate the support,

[vsun]

with great hope, I downloaded 4.3 beta 3 on my 2011 MacBook pro yesterday.

Tried to follow the instruction, but no popup window to ask for airPlay security. I managed to manually add the DisplayLinkUserAgent to the Accessibility, still, no airPlay icon, my hp 22cwa is not detected, invisible in System Preferences > Displays...

With 4.1, at least I can do mirroring... there seem to be other 2011 MacBook pro complaints regarding 4.3 beta, wondering if this version has some incompatibility issues?

DisplayLink dev, is there anything I can provide to help you debug this scenario? Or anybody has any suggestion on how to fix/workaround this?

----------------

[update] Problem Resolved!

Turns out my non-detection problem is related to a faulty USB hub plug. All is well now. Good job DisplayLink!

[alex-swiftify]

Anybody knows how to set the 1366x768 default resolution on the MB168B monitor using the latest drivers?
Using the latest 4.3 Beta 3 on macOS 10.13.4.
When holding down the Option key to see all resolutions the closest I can get (without scaling) is 1024x768.

[foxfire]

Hi - I've got my MacBook Pro, using 10.13.4 hooked up to a DisplayLink hub so that I can use my Dell 34" curved WQHD (3440x1440) monitor for the detailed Photoshop and graphics work I do as a freelancer. The workaround is max 1080p and looks very blurry on this monitor and I can't work like this.

Am I holding out for something that's never going to happen if Apple has closed off certain parts of the code that allowed DisplayLink to work properly? I'm not sure what my plan B is going to be, but I can't do this for much longer.

I don't have the time to downgrade my MacOS and ensure all my years of finessing settings, profiles, scripts, tweaks aren't going to get lost in the process (yes I have proper backups, but that doesn't mean much when downgrading).

I'm sure the DisplayLink dev team is on it but is there a remote chance this problem can be fixed?