macOS High Sierra 10.13.4
The driver (DisplayLink Installer 4.1.11) doesn't work anymore withe macOS High Sierra bêta 10.13.4 (17E139)
TOULEMONDE
shared this idea
AdminWim
(Product Manager, DisplayLink)
responded
We are aware that installing macOS release Version 10.13.4 will cause DisplayLink connected displays to go blank after the OS upgrade, with the current DisplayLink driver [4.1] installed. Functionality such as Ethernet and audio, where implemented, is unaffected. We have alerted Apple to this issue and are working hard to find a resolution. These features continue to work as expected in 10.13.3.
In the meantime, we are releasing a new driver [4.3] that will enable clone mode, but not mirror or extended mode displays in 10.13.4. If you require mirror or extended mode displays, we recommend that you stay on macOS 10.13.3 at this time.
We understand that this loss of functionality on OS upgrade is potentially disruptive for our users and customers. Please be assured that this issue has the highest business priority in DisplayLink. We thank you for your patience and will provide an update on this situation, as soon as we have further information to share.
97 comments
-
fred.laxton
commented
Displaylink, you've known about a problem with 10.13.4 and blank Displaylink displays for about two months. I see reports of problems with 10.13.4 beta in the support forums from early February. Why didn't you alert everyone BEFORE they upgraded to 10.13.4? It would be a huge hassle and disruptive to my business to go back to 10.13.3, so now I'm forced to lose my third monitor until you get this sorted out. Very poor support practice. You should have proactively notified everyone in advance of the 10.13.4 release!
-
Josh P
commented
10.13 has been out for awhile, driverless docks work fine.
Can you stop blaming Apple and solve your 3rd party driver?
Can’t you just disable your chipset and allow the dock to function as passthru?
This is costing us thousands of dollars a day.
Ps: at least you fixed aero bug on the win beta
-
Anonymous
commented
I too wish I had known about this before I updated....the clones is useless as I got DisplayLink and Landing Zone for my Mac Air to work on multiple monitors. Please hurry!
-
Anonymous
commented
I wish I had known about this BEFORE i updated to 10.13.4....now in clone mode which is awful to work with. Hopefully you can get this fixed very very soon...like Monday of next week.
-
Iain W.
commented
I know it's risky to promise dates for releases but this has devastated my productivity. Could you perhaps let us know if the update to allow extend mode is forthcoming in a matter of days (or weeks or months). If it's the latter, it would be good to know so we can move on to other solutions. I'm sure many people are anyway so if it's a matter of days or weeks some of us might consider waiting. Since this was a known issue in beta hopefully you planned accordingly and are just a little late getting the updated drivers out?
-
Sam
commented
Any ETA on the ressurection of my now blank monitor?
-
silberman1
commented
Fix macOS V 10.13.4 DisplayLink 'only clone' issue
-
fred.laxton
commented
Displaylink, you've known about a problem with 10.13.4 and blank Displaylink displays for about two months. I see reports of problems with 10.13.4 beta in the support forums from early February. Why didn't you alert everyone BEFORE they upgraded to 10.13.4? It would be a huge hassle and disruptive to my business to go back to 10.13.3, so now I'm forced to lose my third monitor until you get this sorted out. Very poor support practice. You should have proactively notified everyone in advance of the 10.13.4 release!
-
An angry developer
commented
This renders machines potentially insecure while we wait for an alpha build? Ya had a year to get the beta right. Sorry excuse for a hardware company, even sorrier on the software end. Worst cost cut ever was choosing your junk over real products with talented devs.
-
Bassfly
commented
I got the same Problem after the official Update to 10.13.4.
Any solution is welcome, or do we have to wait for the next driver update? -
Aaron W
commented
10.13.3 work intermittently, at best, for me. Is an update scheduled anytime soon? DisplayLink has been money for me over the last couple of years, I'd hate to have to find a new solution.
-
Tony Williams
commented
I also noticed that the kernel extension has a team ID of "3YQY62QM3" - which is nine characters. Every other KEXT in my list has a 10 character team ID.
I'm wondering if this is an error in a programmer's cut and paste?
It may be causing a problem in 10.13.4 as the kernel signing system is tighter.
-
EricT
commented
The plist under /Library/LaunchAgents/com.displaylink.useragent.plist have a key value pair of Program: /Library/PrivilegedHelperTools/DisplayLink/DisplayLinkUserAgent.bundle/Contents/MacOS/DisplayLinkUserAgent
But the DisplayLinkUserAgent.bundle is not there so its failing (throwing a status code of 78 if you do a launchctl list.) I'm not sure if this has anything to do with 10.13.4 or not but I figured it was at least a start.
-
EricT
commented
On 10.13.4, this breaks for me. I had intermittent issues with 10.13.3, but now it just won't work at all. (Also tried re-installing drivers.)
-
James R Maxeiner
commented
Not quite my experience, but close. It works for a while, then several times closes out and reopens, and then closes altogether. This seems more common when using Internet.
-
Juan
commented
is there any solution to this? how can we fix this so we can use the dual monitors again??
-
Tony Williams
commented
This indeed correct. It breaks when you upgrade from 10.13.3 and an uninstall and install of the latest drivers makes no difference.