Displaylink ceases to work in 10.13.4

[sheafoley]

Just updated to 10.13.4 (beta) and my display link has ceased to work.

I have uninstalled and re-installed the latest version.

It seems that my monitor recognizes a signal (as it doesn't go to sleep) but it is not getting picture nor does it show in the 'arrangement' tab for my display preferences.

If anyone has any insight, it would be greatly appreciated.

Thanks,

[rd123]

Same problem here. Also tried un and re-installing without luck. :(

[dizash]

Same problem here. Also tried un and re-installing without luck. :(

Same problem here too. Interestingly enough, if I take a screen shot (cmd+shift+4) the screen shot of the displylink connected monitor shows the screen as it's supposed to. I only see that in the screen shot. Otherwise the. screen is solid lime green - a new problem, not like any I've had before. Also none of the tricks that have previously worked helped (like force quitting displaylink user agent or displaylink manager in activity monitor, etc).

[Carlo]

Hi we see both issues: yellowish screen with mouse pointer and screen not added to the layout. We also see a number of problems on the internal screen, alt mode screens and Thunderbolt screens.

We are investigating, if you can please do share details of your Mac model and screen configuration.

Carlo

[mmoney13]

I am having the same Yellow Screens issue with 10.13.4 Beta.

My machine is a MacBook Pro 13” 2017
3.5GHz Intel Core i7
16GB Ram
Intel Iris Plus Graphics 650 1536MB

2 Monitors are LG 43” 4K

Using the USB-c Targus Dual 4K Port Replicator

[GaryK]

Hi,

I've got the same problem on 10.13.4 beta. I initially had a yellow screen and cursor. Now there's just nothing - that second screen isn't being recognised.

Please help!

[RGloverii]

Hi. Same issue for me with 10.13.4 beta.

I have a 2016 MacBook with two Asus MB168B+ monitors. After upgrading to the Mac OS beta, the monitors are completely not recognized by the Mac. They do not show up under Displays, and they do not power themselves on when the Mac is connected to them.

I deinstalled the Displaylink driver and reinstalled, with no change.

Please let me know if any logs are needed to help diagnose the root cause.

Thanks!

2016 MacBook
1.2 GHz M5
8GB RAM
Dell WD15 USB-C docking station
2x Asus MB168B+ monitors

[Alanant]

Its also affecting me. My two external monitors are showing yellow screens with the mouse cursor. The inbuilt display works with or without the Display Link device connected, however it is having its own issues including application flickering and ghosting.

10.13.4 Beta (17E139j)
Macbook Pro 13 inch 2017
Intel Iris Plus Graphics 640 1536 MB

Update - I can confirm that after uninstalling Displaylink the inbuilt display no longer flickers.

[anderslu]

No external screens visible in macOs here as well.

Using a MacBook Pro 15-inch, 2017
2.8 GHz i7
16GB RAM
Intel HD 630 / AMD Radeon Pro 555
Targus DOCK177USZ
2x Lenovo T2334pA monitors

[slvrscoobie]

same here, one displayport monitor working fine, displaylink is all yellow, but i do see the mouse cursor.

[Buschermoehle]

10.13.4 Beta (17E139j)
MacBook Pro (Retina, 13', Mitte 2014)
i-Tec USB 3.0 Dual Docking Station

hope there will be a fix soon

[SimpleWillie]

Mac Pro, 10.13.4, USBc-HDMI works, but USB3DOCKH2DP display link nor HDMI on the unit does not.

[AAJ64]

Received my MB 168B today. Running 10.13.1. After over an hour in chat with ASUS support installing and uninstalling the driver I decided to look here.

I'm glad the problem isn't isolated to my new install.

MacBook Air
Intel Core i5
1.8 GHz
8 GB

[dizash]

Hi we see both issues: yellowish screen with mouse pointer and screen not added to the layout. We also see a number of problems on the internal screen, alt mode screens and Thunderbolt screens.

We are investigating, if you can please do share details of your Mac model and screen configuration.

Carlo

Oops forgot to give you the detials:

MacBookAir5,2 (mid-2012)
MacOS 10.13.4 (17E139j)
Intel Core i7 - 2GHz
8GB DDR3 - 1600MHz
Diamond USB3 to DVI
External Displays:
I run 2 external displays in clamshell mode (1 via the Thunderbolt/Display Port and 1 via the Displaylink adapter mentioned above)
The problem is duplicated when I switch connections to the displays - so the same problem no matter which display is connected to the DisplayLink Unit - Connected with DVI or DVI to HDMI adapter.
Monitors
Acer K272HL - 27"
Asus VP279 - 27"
Both set to 1920 x 1080 @ 60 Hz

No previous problems this significant with these monitors or the other 2 Samsung 24" (different models) at my office. Usually the worst case was looking here to find there was a beta or force quitting Display Link Manager and/or User Agent in Activity Monitor. Thanks

[rterblanche]

Having the same issues on a Macbook Pro.

Had to uninstall Displaylink drivers to not go insane.

Would love to maybe get access to the beta displaylink drivers or I will have to roll back. Going to be a bit of a pain because I don't have a time machine backup

[njoerd]

Having the same issues on a Macbook Pro.

Had to uninstall Displaylink drivers to not go insane.

Would love to maybe get access to the beta displaylink drivers or I will have to roll back. Going to be a bit of a pain because I don't have a time machine backup

Same here on Macbook Pro 13" 2017, 3,5GhZ 256GB, 16GBRAM

[bhlc]

I also saw a yellow screen on the monitor connected through a du3200 after installing 10.13.4 beta. It was also affecting my MacBook pro's built in monitor. I tried reinstalling the DL driver, which fixed the issue with the built-in display, but now the external monitor isn't seeing a signal.

MacOS 10.13.4 Beta (17E139j)
MacBook Pro (Retina, 15-inch, Late 2013)
2.3 GHz Intel Core i7
16 GB 1600 MHz DDR3

[M. Holkamp]

After installing the 10.13.4 beta i saw the screens, than it turned yellow.
I removed the driver and installed the latest version.
Now i don't see the extrenal monitors.

I have attached the result of the DisplayLink info tool.

[anthony.gelibert]

On my side, kernel panic at each startup.
I had to boot in "safe mode" to be able to access to my system.

MacBook Pro 15" (end 2013).

[Alanant]

DisplayLink team, would you have an update on this issue? I understand that Apple have caused the problem, which is likely related to eGPU support, and that it is a beta after all but it would be good to know if you guys are on top of it and are planning to release a version of your software that takes into account the changes. Thanks!

[russjr08]

On my side, kernel panic at each startup.
I had to boot in "safe mode" to be able to access to my system.

MacBook Pro 15" (end 2013).

I am having the exact same issue MBP 15" Mid-2012. Stacktrace didn't point toward a display link kext though, just the default Apple graphics one.

[toastido]

I too have this issue. The lemon screen. After 10.13.4b1.

I've tried:
1) rebooting
2) manually pulling the kext (that didn't end well)
3) uninstall the driver/reinstall the driver
4) uninstall the 4.1 driver, install 4.0 driver (didn't even see the adapter anymore)
5) uninstall 4.0, reinstall 4.1 (back to lemon-lime monitor)

It's annoying AF, and needs to be resolved soon.

Mac specs:
2012 13" MacBook Pro w/i7 2.9ghz, 16gb ram, 1TB ssd


See attachments for what it looks like.

[toastido]

Hi we see both issues: yellowish screen with mouse pointer and screen not added to the layout. We also see a number of problems on the internal screen, alt mode screens and Thunderbolt screens.

We are investigating, if you can please do share details of your Mac model and screen configuration.

Carlo

Carlo,

Have you been able to make any headway in getting this issue fixed? I submitted my DisplayLink Info via the submission tool, but if you need it somewhere else I can submit it there, too.

[WhatsUpInTheSky37]

I have a iMac 27. The two monitors to my left and right are being handled by the two thunderbolt ports on the back and a Apple piece of hardware. My USB Displaylink adapter is not working like everyone else's. I figured I would give the stats incase it helps.

Hardware Overview:

Model Name: iMac
Model Identifier: iMac17,1
Processor Name: Intel Core i7
Processor Speed: 4 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 32 GB
Boot ROM Version: IM171.0148.B00
SMC Version (system): 2.34f2

-Display Tab

Chipset Model: AMD Radeon R9 M395X
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Dynamic, Max): 4096 MB
Vendor: AMD (0x1002)
Device ID: 0x6920
Revision ID: 0x0000
ROM Revision: 113-C905AA-799
VBIOS Version: 113-C905A0-007
EFI Driver Version: 01.00.799
Metal: Supported, feature set macOS GPUFamily1 v3

Displays:
iMac:
Display Type: Built-In Retina LCD
Resolution: 5120 x 2880 Retina
Framebuffer Depth: 30-Bit Color (ARGB2101010)
Main Display: Yes
Mirror: Off
Online: Yes
Automatically Adjust Brightness: No

EM32TS:
Resolution: 1366 x 768 (WSGA - Wide eXtended Graphics Array)
UI Looks like: 1366 x 768 @ 60 Hz
Framebuffer Depth: 30-Bit Color (ARGB2101010)
Display Serial Number: 10EE230100001
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No

DX-40L261A12:
Resolution: 1920 x 1080 (1080p FHD - Full High Definition)
UI Looks like: 1920 x 1080 (1080p FHD - Full High Definition)
Framebuffer Depth: 30-Bit Color (ARGB2101010)
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Television: Yes

--- Here is the DisplayLink being seen by the USB..

Targus USB3 SV2K HDMI Adapter:

Product ID: 0x4361
Vendor ID: 0x17e9 (DisplayLink (UK) Ltd.)
Version: 31.08
Serial Number: 15003288
Speed: Up to 5 Gb/sec
Manufacturer: DisplayLink
Location ID: 0x14700000 / 4
Current Available (mA): 900
Current Required (mA): 504
Extra Operating Current (mA): 0

[LawrenceShipman]

Just updated to 10.13.4 (beta) and my display link has ceased to work.

I have uninstalled and re-installed the latest version.

It seems that my monitor recognizes a signal (as it doesn't go to sleep) but it is not getting picture nor does it show in the 'arrangement' tab for my display preferences.

If anyone has any insight, it would be greatly appreciated.

Thanks,

Did you fix this, I have had the same issue and this fixed it for me...


Download 4.1.11 driver, install as normal
Reboot MAC and log back in, screens are still not working
Go to System Preferences > Security & Privacy
At the bottom of the General screen, it will say something like, certain apps were stopped from installing or loading, I can't quite remember exact message :)
Click message and then select the DisplayLink Corp option and it will ask to reboot again.
Reboot MAC and then all should be fine :)


Hope this helps someone!

[tpurdue]

Those instructions may work if you didn't have a DisplayLink driver installed when you upgraded to High Sierra. For those who already had the drive installed, the authorization doesn't show when you uninstall/reinstall.

I can also confirm the issue still exists with Beta 2 of 10.13.4.

[LawrenceShipman]

Those instructions may work if you didn't have a DisplayLink driver installed when you upgraded to High Sierra. For those who already had the drive installed, the authorization doesn't show when you uninstall/reinstall.

I can also confirm the issue still exists with Beta 2 of 10.13.4.

Yes, it was a clean install, don't know why it can't be fixed, such a shame as I haven't used my dock for two months until today.

[dizash]

Those instructions may work if you didn't have a DisplayLink driver installed when you upgraded to High Sierra. For those who already had the drive installed, the authorization doesn't show when you uninstall/reinstall.

I can also confirm the issue still exists with Beta 2 of 10.13.4.

Same here. Beta 2 - no change to DisplayLink. Lemon colored screen. There’s irony somewhere in there.

[Alanant]

Same. Beta 2 and its still broken.

[User112]

Broken here too

[Carlo]

Hi All,

Quick update. We (think we) have found out where everything breaks. It's a pretty fundamental change, probably linked to the eGPU hot plug functionality.

Now we "just" have to find a way to overcome the issue. How hard can it be!

Regards,
Carlo

[tpurdue]

Hi All,

Quick update. We (think we) have found out where everything breaks. It's a pretty fundamental change, probably linked to the eGPU hot plug functionality.

Now we "just" have to find a way to overcome the issue. How hard can it be!

Regards,
Carlo

Thanks Carlo! We are all cheering for you!

Can confirm I still get yellow screen in the new "g" version of Beta 2.

[toastido]

Hi All,

Quick update. We (think we) have found out where everything breaks. It's a pretty fundamental change, probably linked to the eGPU hot plug functionality.

Now we "just" have to find a way to overcome the issue. How hard can it be!

Regards,
Carlo


Thank you for the update, Carlo. It's much nicer to see an update every little bit even if a solution hasn't been found, just for the comfort of knowing you guys are working on it.

Thanks again, and good luck to you and your team!

[sean++]

I also had my DisplayLink stop working with the last 10.13.4 Beta, which was a bit of an annoyance, but I was pleased to find that I wasn't the only one.

I'm happy to report that with the latest 10.13.4 Beta (17E150g) update the problem seems to be resolved. It came out in the last 12 hours.

I'm using a USB-DVI on an older Mac mini, and I'm very pleased to have back the use of the second monitor.

https://i.imgur.com/WNqRVdA.png

[kirkb]

I also had my DisplayLink stop working with the last 10.13.4 Beta, which was a bit of an annoyance, but I was pleased to find that I wasn't the only one.

I'm happy to report that with the latest 10.13.4 Beta (17E150g) update the problem seems to be resolved. It came out in the last 12 hours.

I'm using a USB-DVI on an older Mac mini, and I'm very pleased to have back the use of the second monitor.

https://i.imgur.com/WNqRVdA.png

This update didn't solve my issue unfortunately. Anyone else have any success with the latest beta?

[dizash]

This update didn't solve my issue unfortunately. Anyone else have any success with the latest beta?

No luck. Problem is exactly the same. Tried all the troubleshooting too just to be sure including unistall / reinstall. Glad to get the above update from Carlo.

[RGloverii]

No change for me either with the latest High Sierra beta.

[blb]

just to confirm: With 10.13.4 beta version 1 I did have black screen, now with 10.13.4 beta version 2 I di have yellow screen with mouse pointer visible.

Macbook pro Retina, 13", mid 2014

[aehsmu]

MacBook Pro (pre-TouchBar) - 10.13.4 Developer Beta

Driver causes main display to be extremely sluggish and jittery.

De-installing driver corrects the issue.

Am without 3rd monitor for the moment.

[toastido]

I found something that MIGHT be of importance.

I have a 13" mbp, with a SyncMaster 24" display attached to the miniDP port, and the other attached to a USB3->DVI DisplayLink adapter. I have the lemon screen issue on the 3rd monitor. Interestingly enough, MacOS *SEES* the 3rd monitor correctly, but thinks it's ALSO attached to the onboard video instead of the DisplayLink. Before, it showed the DisplayLink adapter as a separate video device with the monitor attached, now it shows this:

3424

3425


Thanks.

[roadtest]

I am new Mac user and just purchased this new MacBook Pro(2.9G I7 with 16GB DDR3 memory/dual graphics(Intel HD graphics 630 and Radeon 560). Laptop is connected to a USB3.0 dock station with two DVI ports.

After installing the latest macos update and reinstall DisplayLink driver 4.1.11. My two monitors are working fine. Then I disconnected laptop, work somewhere else for few hours, then came back, reconnect to the USB dock. Both monitors has no output. Reboot laptop doesn't make any difference. I have to uninstall the driver and reinstall it. From what I can see after driver installation, all three monitors(two external monitors and one built one) are using Intel HD graphics 630 card. After I disconnect/reconnect the USB dock, it reports Radeon 560 is being used, as a result, all output to the two external monitors. Other than reinstalling the driver, I haven't figured out way to choose graphic card.:eek:

I did try to reload the DisplayLink driver without reinstallation. The "kextunload/kextload" complains there already has one instance using the driver and doesn't allow me to unload driver from cli, which is strange behavior.

[njoerd]

I can confirm that the problem persists in Beta 2. Had to uninstall the displaylink driver completely to not go insane since my integrated screen got glitchy and flickery after installing beta2.

[toastido]

It's been what, 3 weeks now, and all I've heard is that they believe they have identified the issue and hope to have it resolved shortly.

DisplayLink guys - please let us know what's going on here. Some of us rely on your technology for our business and it's difficult to go without.

That being said, if you have a beta driver, I for one would be glad to test it for you.

Thanks!

[aehsmu]

I echo the sentiments of users frustrations.

I currently have 4 Macs that are hobbled due to the broken DisplayLink driver.

Being a developer myself, I understand the problems related to OS changes.

However, a reply to this thread from DisplayLink folks would be helpful.
--
Eric H.
--

[RGloverii]

While we are all currently impacted by this issue, I think it’s important to note that we have caused this issue ourselves by installing an Apple BETA product on presumably PRODUCTION machines. That is a risk, and we are now suffering the result of that risk.

I can not fault DisplayLink for not providing a fix yet. That is the point of developer betas. To flesh out incompatibilities and resolve before general release of the update.

[toastido]

While we are all currently impacted by this issue, I think it’s important to note that we have caused this issue ourselves by installing an Apple BETA product on presumably PRODUCTION machines. That is a risk, and we are now suffering the result of that risk.

While I can appreciate what you are saying, nobody is blaming DisplayLink for the issue. We're just pushing to get it fixed. (Besides, if apple were to release 10.13.4 to the public today, it'd still be broken.)

I can not fault DisplayLink for not providing a fix yet. That is the point of developer betas. To flesh out incompatibilities and resolve before general release of the update.

Again, we're just anxious to get the fix. I have even offered to test a "beta" fix to see if it works outside of a lab environment for them.

Another thing to note, is that most developers (like myself) keep up to date with developer/public betas so we can do just that, flesh out incompatibilities and resolve before GA. That is why we would have installed it on "production" machines.

Not blaming anyone, or even getting mad; Just requesting updates to this issue.

[RGloverii]

I think that DisplayLink tends to be more open and communicative regarding issues and status than most established vendors. And I appreciate that.

Yes, this incompatibility is inconvenient to all of us on this thread. And it goes without saying that we would like to see a fix ASAP. I simply don’t see any need to further impress upon DisplayLink that we want a fix. They are well aware of the need for a fix. Not only for us on this thread, but for ALL consumers of their products.

As for potential DisplayLink beta releases: This is something they already do. They are made public when available for testing.

I hope I don’t come across as being rude. That’s not my intent. I’m just providing my thoughts as someone who has utilized their products both personally and professionally for a long time.

[dizash]

I think that DisplayLink tends to be more open and communicative regarding issues and status than most established vendors. And I appreciate that.

Yes, this incompatibility is inconvenient to all of us on this thread. And it goes without saying that we would like to see a fix ASAP. I simply don’t see any need to further impress upon DisplayLink that we want a fix. They are well aware of the need for a fix. Not only for us on this thread, but for ALL consumers of their products.

As for potential DisplayLink beta releases: This is something they already do. They are made public when available for testing.

I hope I don’t come across as being rude. That’s not my intent. I’m just providing my thoughts as someone who has utilized their products both personally and professionally for a long time.

I too appreciate the transparency from DL. It's a rare thing and much appreciated. Since this thread seems to have received the most participation in users sharing their configs/settings and more importantly, an update from Carlo when they discovered the one or two likely causes for the issue that's universal.

Anyway, besides giving this thread a bump, I noticed that if I selectmirror displays in system prefs (something I was prepared to cause a freeze or crash), the display attached to a DL to USB 3, went from lime green, to actually displaying what appears to be my login screen. I can only guess because the system prefs/ displays for that particular display is in the middle of the screen hiding the 3 accounts displayed on my login screen. Unfortunately, that's the only time I see anything different and requires a hard restart (holding down the power button). I'm also confirming that taking a screen shot of the diplay by dragging my trackpad pointer to that display (and using the cmd+shift+3 screenshot method), leaves you with a screen shot of your display how it should be displaying. It'definitely strange as it's like the lime green screen seems like a privacy measure - even though I know that's not what it is- I ony say that knowing that underneath the green, the display functions. More specifically, I'm able to drag things over there as well as blindly get them back .

Again the work by DL finding the likely issues and letting us know really is appreciated. Solid move and it's forr that reason and access to betas in the past which is why i haven't considered any other multi-screen solution. Thanks.

[Carlo]

Hi All,

Update from us about this issue.

No solution yet. We are running a quite large number of experiments and still trying to get more info out of Apple.
I cannot share much, however we are aware of a few cases where the "yellow screen" issue can occasionally show pixels. This is one line of enquiry so if this happens to you, please let us know in which conditions.

As you can imagine this issue is higher than highest priority for us. Thank you for your comments and the useful information posted so far. Don't stop!

We have raised the 10.13.4 issue with Apple, it's ID 37385102.
We invite everyone to raise this problem with Apple. The bigger your deployment the better. Please let us know if the support team close as duplicate of an internal issue and let us know which is the internal issue.

Kind regards
Carlo

[slvrscoobie]

Hi All,

Update from us about this issue.

No solution yet. We are running a quite large number of experiments and still trying to get more info out of Apple.
I cannot share much, however we are aware of a few cases where the "yellow screen" issue can occasionally show pixels. This is one line of enquiry so if this happens to you, please let us know in which conditions.

As you can imagine this issue is higher than highest priority for us. Thank you for your comments and the useful information posted so far. Don't stop!

We have raised the 10.13.4 issue with Apple, it's ID 37385102.
We invite everyone to raise this problem with Apple. The bigger your deployment the better. Please let us know if the support team close as duplicate of an internal issue and let us know which is the internal issue.

Kind regards
Carlo

I can occasionally see the desktop 'behind the yellow' on my 13" mbp mid2012. however, its usually when swiping between desktops on the main screen it blinks for a moment. however it isnt consistent. another user happy to alpha test drivers if it can help

[toastido]

Interestingly, it seems like the eGPU stuff is causing all sorts of issues all around. Very similar issues were reported using eGPUs and High Sierra: https://forums.developer.apple.com/message/264366#264366

The most interesting part (to me), is that where I noticed it thinks the external display is using the internal video card in the profiler, and in that thread, the same -- the external GPU seems to also be reported to be using the internal card(s).

Mind you, that thread is from late last year, but based upon Apple's docs, built-in eGPU support would be being added in to high sierra during this cycle.

I may be way off track, but it's an interesting coincidence if not related.

[toastido]

Another thing of note: I saw my full desktop momentarily immediately after login. It flashed up for a full second or so. I found this line interesting in the system log during that time:

Feb 19 12:02:24 clarity DisplayLinkUserAgent[263]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] add: "No such file or directory" - 0x2


Also these:

Feb 19 12:02:34 clarity com.apple.xpc.launchd[1] (com.displaylink.useragent): This service is defined to be constantly running and is inherently inefficient.
Feb 19 12:02:34 clarity com.apple.xpc.launchd[1] (com.displaylink.useragent): Please switch away from OnDemand to KeepAlive.

Here's a link to see the full boot/login process if it helps: https://www.dropbox.com/s/2vc9z507fcjzh48/bootlog.rtf?dl=0

[toastido]

Also I noticed if I kill -HUP the pid of DisplayLinkUserAgent, my desktop on that monitor flashes up for a second before the yellow takes over again.

[toastido]

So after doing all that, I unplugged everything and closed the lid (put the machine to sleep). When I woke it up this morning and attached all the peripherals, THE DISPLAYLINK MONITOR IS WORKING PROPERLY!

I have no idea why. Ask me for whatever you'd like and if I can provide it I will.

EDIT: The displaylink useragent is no longer running. Nor is the displaylink manager, but the monitor is up and running in full resolution and fully functional.

MBP mid-2012 13" i7 10.14.2b2

[madtxema]

Hi,

On Mac Os 10.13.4 beta 3 (17E160e) still doesn't work, yellow screen in my case.

[Carlo]

So after doing all that, I unplugged everything and closed the lid (put the machine to sleep). When I woke it up this morning and attached all the peripherals, THE DISPLAYLINK MONITOR IS WORKING PROPERLY!

I have no idea why. Ask me for whatever you'd like and if I can provide it I will.

EDIT: The displaylink useragent is no longer running. Nor is the displaylink manager, but the monitor is up and running in full resolution and fully functional.

MBP mid-2012 13" i7 10.14.2b2

Thank you toastido,

Well this is all surprising it would definitely help to see your debug info in the working case. Can you please follow the instructions in https://support.displaylink.com/knowledgebase/articles/755301 and mention that the logs are for me?

Do you see any corruption on the internal screen or the screen you have connected to the built-in external port on your MBP?

Many thanks,
Carlo

[aehsmu]

I can confirm that the problem persists in Beta 2. Had to uninstall the displaylink driver completely to not go insane since my integrated screen got glitchy and flickery after installing beta2.

Installed beta 3 this morning and then re-installed DisplayLink 4.1

I now see no signal, flicker, or any sign of life on the connected monitor.
--
Eric H.
--

[Alanant]

Installed beta 3 this morning and then re-installed DisplayLink 4.1

I now see no signal, flicker, or any sign of life on the connected monitor.
--
Eric H.
--

Same experience for me on Beta 3.

[toastido]

Thank you toastido,

Well this is all surprising it would definitely help to see your debug info in the working case. Can you please follow the instructions in https://support.displaylink.com/knowledgebase/articles/755301 and mention that the logs are for me?

Do you see any corruption on the internal screen or the screen you have connected to the built-in external port on your MBP?

Many thanks,
Carlo

Well, I would be glad to, except now it's not working at all. I forgot to disable auto-updates and my machine updated to 10.13.4b3 overnight.

[Carlo]

Well, I would be glad to, except now it's not working at all. I forgot to disable auto-updates and my machine updated to 10.13.4b3 overnight.

It's OK. Our experiments so far show that the yellow screen/working pixels is a temporary situation, albeit interesting of course. We'll keep looking.

Cheers
Carlo

[slvrscoobie]

I updated to beta 3 hoping for a fix (some reason i dont get updates on this thread to me email)
I still get the yellow screen only with mouse cursor.

[slvrscoobie]

Like all on this thread I updated to High Sierra and now my AOC monitor is rendered useless. Display Link team we need YOU to get a solution. Registering a bug with Apple is not going to make anything happen. Please help.

Then roll back your OS to the last STABLE version. We all run Betas knowing there could be issues. this is one of them. Dont get feisty with DisplayLink because your running beta software they got the same time you did, and things arent working properly. If this is a major issue, use the Stable release where Displaylink works properly. These are designed for DEVELOPER machines, you know like the ones at Displaylinks office.

[toastido]

Thank you toastido,

Well this is all surprising it would definitely help to see your debug info in the working case. Can you please follow the instructions in https://support.displaylink.com/knowledgebase/articles/755301 and mention that the logs are for me?

Do you see any corruption on the internal screen or the screen you have connected to the built-in external port on your MBP?

Many thanks,
Carlo

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Attached is the output from the information tool you requested as well.

[Carlo]

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Attached is the output from the information tool you requested as well.

Thank you we're looking at the logs, we'll have a new series of experiments to run.

Cheers,
Carlo

[tpurdue]

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Attached is the output from the information tool you requested as well.


This worked for me as well. Second screen up and running. There is definitely lag and some rendering issues (white boxes over menu items, etc.) but it's mostly useful.

[dizash]

[QUOTE=toastido;85374]Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Hi,
Can you please specify what exactly to enter in the commond line? Is it only the 2nd two lines each beginning with the $ sign and if so, it appears there are more brackets in your summary than I'm used to working with in Terminal.
Thanks very much.

[toastido]

[QUOTE=toastido;85374]Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Hi,
Can you please specify what exactly to enter in the commond line? Is it only the 2nd two lines each beginning with the $ sign and if so, it appears there are more brackets in your summary than I'm used to working with in Terminal.
Thanks very much.

Oh, sure. I'm using ZSH with some customizations, so that's why my command line looks like that. the actual command is:
launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist

[dizash]

[QUOTE=dizash;85386]

Oh, sure. I'm using ZSH with some customizations, so that's why my command line looks like that. the actual command is:
launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist

Thanks Toastido - especially for the quick reply. Much appreciated!!!!

UPDATE: Immediately after utilizing the command, my DL Connected Monitor also SPRANG TO LIFE:

THANKS AGAIN TOASTIDO - this is huge for me!!!

[toastido]

[QUOTE=toastido;85387]

Thanks Toastido - especially for the quick reply. Much appreciated!!!!

UPDATE: Immediately after utilizing the command, my DL Connected Monitor also SPRANG TO LIFE:

THANKS AGAIN TOASTIDO - this is huge for me!!!

NP. This will at least work until DisplayLink gets a real fix in place. It's more of a bandaid since it's a little laggy and whatnot, but at least it's a workaround for the time being.

[Alanant]

This workaround doesn't work for me. Maybe it's hardware specific? I'm using an older Kensington SD3500v I believe. I can confirm the model if display link need it.

[aehsmu]

This workaround doesn't work for me. Maybe it's hardware specific? I'm using an older Kensington SD3500v I believe. I can confirm the model if display link need it.

Same here. The monitor indicates it's receiving a signal, but the screen stays black.
--
Eric H.
--
NEC AccuSync LCD 72VX monitor

[slvrscoobie]

13.4.4 beta doesnt help - now the screen is just black instead of yellow.
and the 'work around' doesnt help either

[Alanant]

I can confirm, there is no change with 10.13.4 beta 4.

[slvrscoobie]

im forgetting how to use a 2nd monitor lol

[DLguy]

Hi all,
I installed the new version of the DisplayLink 4.1.11 on my 2012 MacBook Pro. I'm currently running MacOS HighSierra (version 10.13.4 (17E170c). I have the Dell D3100 port replicator/Dock. I ran the unload patch but still does not work. Its connected to my Mac though usb 3.0. The audio, network and USB ports work with no issues. The video is the only issue.
I tested the port replictor / dock with my Dell XPS laptop and it works like a charm. I think its an Apple related issue.

Any help is greatly appreciated, thank you in advance.

[mlukaszek]

13.4.4 beta doesnt help - now the screen is just black instead of yellow.
and the 'work around' doesnt help either

Hi All,

Another update from us. Unfortunately the workaround is not working anymore, as you noticed. There have been more changes in the new beta for eGPU which the team is investigating further. Keep your fingers crossed!

Thanks,

Michal

[slvrscoobie]

Hi All,

Another update from us. Unfortunately the workaround is not working anymore, as you noticed. There have been more changes in the new beta for eGPU which the team is investigating further. Keep your fingers crossed!

Thanks,

Michal

Thanks for keeping us updated! obviously 13.4 seems to have a big change in how it handles the eGPU. Any idea why this change was made or what benefits it might have long term?

[Alanant]

Supporting an external graphics card would have many benefits for graphics intensive applications including games.

I imagine the biggest benefit to Macbook Display Link users would be support for clamshell mode (just guessing though).

[dizash]

This workaround doesn't work for me. Maybe it's hardware specific? I'm using an older Kensington SD3500v I believe. I can confirm the model if display link need it.

+1

Thanks for keeping us updated! obviously 13.4 seems to have a big change in how it handles the eGPU. Any idea why this change was made or what benefits it might have long term?

+1. The updates really are appreciated and says a lot about you guys. Thanks!

[sean++]

I also had my DisplayLink stop working with the last 10.13.4 Beta, which was a bit of an annoyance, but I was pleased to find that I wasn't the only one.

I'm happy to report that with the latest 10.13.4 Beta (17E150g) update the problem seems to be resolved. It came out in the last 12 hours.

I'm using a USB-DVI on an older Mac mini, and I'm very pleased to have back the use of the second monitor.

https://i.imgur.com/WNqRVdA.png

Just to follow up to my own post, what Beta giveth, Beta taketh away. I'm on the 17E170c build and alas I'm back to using a single monitor.

[Alanant]

Still broken in 10.13.4 Beta 5.

[pacmanbneNL]

Still broken in 10.13.4 Beta 5.

Yep still broke here after the applied update in fact I have lost network connectivity also just have keyboard as the only working function :(

[Poly]

Dear DisplayLink developers, if you have to rewrite the drivers anyway for the the 13.4 update, would it be possible to enable HDCP support, so that we can eventually watch iTunes movies on DisplayLink displays?

[kvd51]

Did you fix this, I have had the same issue and this fixed it for me...


Download 4.1.11 driver, install as normal
Reboot MAC and log back in, screens are still not working
Go to System Preferences > Security & Privacy
At the bottom of the General screen, it will say something like, certain apps were stopped from installing or loading, I can't quite remember exact message :)
Click message and then select the DisplayLink Corp option and it will ask to reboot again.
Reboot MAC and then all should be fine :)


Hope this helps someone!

Hey Lawrence- your suggestion worked for me! Big time thanks. I just bought the AOC monitor and could not get it to work at all. Running 10.13.3 before installing the DisplayLink driver. Have not installed to 10.13.4

[slvrscoobie]

Hey Lawrence- your suggestion worked for me! Big time thanks. I just bought the AOC monitor and could not get it to work at all. Running 10.13.3 before installing the DisplayLink driver. Have not installed to 10.13.4

Damn, thought this was for 13.4, didnt do anything on Beta 5

[Alanant]

No difference in Beta 6 either.

Just guessing, but it seems to me like Apple are not going to fix this. As part of their upcoming eGPU support, they probably killed some legacy process that the likes of DisplayLink was using.

DisplayLink, do you have new software in the works to address this? Not long to go now until 10.13.4 is publicly available (10.13.3 and 10.13.2 both had 6 betas).

[Poly]

No difference in Beta 6 either.
[...] As part of their upcoming eGPU support, they probably killed some legacy process that the likes of DisplayLink was using.

Apparently, Thunderbolt 3 docks are the only option now. :(

[slvrscoobie]

https://9to5mac.com/2018/03/20/apple-leaks-official-release-notes-for-macos-10-13-4-in-french-update-includes-imessage-business-chat-and-egpu-support/amp/
"The release notes indicate that iMessage Business Chat will be available on macOS, as well as formally supporting external GPU (eGPU) systems. "
Looks like the formal eGPU support will be ready shortly - meaning DisplayLink might not need to support it any longer if they conform to the eGPU standards Mac needs??

[Alanant]

From my albeit limited research, eGPUs have been working without the need for drivers, from 10.13.4 Beta 1. This makes it seem like Apple are now adhering to eGPU standards which in turn implies that Display Link hardware works in a proprietary manner.

Somewhat related, the upcoming eGPU support will only work with Thunderbolt 3 Macs i.e. a 2016 or newer MacBook Pro. Applications need to be modified to leverage the eGPU as well.

[DLguy]

So basically, whoever has Display Link devices for any apple computer pre 2016 is no longer supported?

:confused::confused:

:(

[Alanant]

So basically, whoever has Display Link devices for any apple computer pre 2016 is no longer supported?

:confused::confused:

:(

No, I don't think that's the case. I'm sure somebody will correct me if I'm wrong but DisplayLink is not classified as an eGPU. The DisplayLink software is a proprietary Virtual Graphics Card which communicates with their Hardware Rendering Engine which is in the docks we are all using from a bunch of different manufacturers. DisplayLink need to update their VGC software.

[Alanant]

There is an Apple event on the 27th of this month. I think there is a good chance they will announce the availability of 10.13.4 (and break every DisplayLink device hooked up to a Mac).

[DLguy]

We are in the hands of Display Link. Basically if they decide to move forward and make it compatible we are ok, if not we all have to invest another $200 for a dock/hub.
All we can do is hope for support. We are counting on the DisplayLink team!!! :)

[slvrscoobie]

We are in the hands of Display Link. Basically if they decide to move forward and make it compatible we are ok, if not we all have to invest another $200 for a dock/hub.
All we can do is hope for support. We are counting on the DisplayLink team!!! :)

Go DisplayLink Team! Go!
Go DisplayLink Team! Go!

[Poly]

We are in the hands of Display Link. Basically if they decide to move forward and make it compatible we are ok, if not we all have to invest another $200 for a dock/hub.
All we can do is hope for support. We are counting on the DisplayLink team!!! :)

I hope you're right. But I also think that Apple needs to cooperate. If both parties can't negotiate a solution, our dock stations become useless bricks as soon as we update to 10.13.4. :(

[DLguy]

In my honest opinion, Apple will not comply. They will say this is our new standard and this is it. Take it or leave it.
I guess we can use these DisplayLink devices for windows PC's. It works like a charm on my Dell XPS, but no video on my Mac.

To Display Link Team >>>>
Are there any tests we can do to help speed up the process to get these docks to work. Its a win win situation. We get to test, you get to make corrections and your product works, and so does ours :)

[Poly]

I guess we can use these DisplayLink devices for windows PC's. It works like a charm on my Dell XPS, but no video on my Mac.


Yes, the HDCP problem has never been solved. No iTunes or Netflix videos (in Safari) work, and afaik DisplayLink said Apple is to blame.

But what other options are there if you're on a MacBook with a single USB-C port and still want to use two external monitors? DisplayLink was the only working solution so far. Apple doesn't even support multi stream transport (MST) via Display Port. However, MST works like a charm on the same machine when I boot to Windows 10.

[slvrscoobie]

Any chance we could drop in the 13.3 gpu drivers onto the 13.4 via kext edit? I do this with the BT as the continuity wont work on the older laptops unless you trick it into using it with the old drivers. I know its not a long term solution but at least till we figure this out which is days away from being a 2 month issue.

[DLguy]

I have a MacBook Pro with 2 thunderbolt ports and 2 USB 3.0 ports. Anyone have recommendations for alternate dock/hub (with Video/USB/Ethernet/Audio)?

[Alanant]

Still broken in 10.13.4 Beta 7.

[slvrscoobie]

Still broken in 10.13.4 Beta 7.

confirmed here too.

[karlg]

Sames here as well. Two black screens.

[Alanant]

Its been three weeks since DisplayLink shared an update on this. Would love an update from @mlukaszek.

[slvrscoobie]

Its been three weeks since DisplayLink shared an update on this. Would love an update from @mlukaszek.

At least something. any news on progress. Starting to look at other solutions at this point. its been 2 months since this happened, and while I understand there would be some delay since Apple doesnt tell Devs what its doing, at least some kinda update or Alpha testers would be promising, but weve gotten nothing in weeks.

[pmontelo]

Mac-Mini 2012, DisplayLink display is blank after 10.13.4 "upgrade" :(

[slvrscoobie]

https://www.macrumors.com/2018/03/29/apple-releases-macos-high-sierra-10-13-4/

10.13.4 is offical.
Prepare for a bunch of new users to find out dispalylink still doesnt work.

[Alanant]

Also confirming that our DisplayLink docks remain nonfunctional in the official 10.13.4 official release. The DisplayLink software was removed, Mac rebooted, display link software reinstalled, rebooted.

I feel sorry for the folks manning the helpdesks at every DisplayLink licensee. It's going to be rough.

[vanhoosr]

DisplayLink dead, black screen

MacBook Air (13-inch, Early 2015), just upgraded to Mac OS 10.13.4


Steve

[Poly]

Some official information from DisplayLink would be great. Perhaps even a warning on the driver's front page for macOS users?

Shall the Mac users postpone the 10.13.4 update, wait for a driver update or is it safe to say that DisplayLink support via USB on macOS is over ?

Is DisplayLink hardware past 10.13.4 just an expensive doorstopper?

[Alanant]

The only licensee with a mention of this issue is Plugable. They updated an older blog post after 10.13.4 was released and advise not to upgrade.

[Wim]

Dear all

As you have found, the released 10.13.4 update does not change the issues seen with the betas. It causes 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 have been 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.

Wim

[dsjdsj]

Thank you for the update. I notice from previous posts that this has been going on for a while. Do you have any idea about the time frame for this to be resolved?

[dizash]

Just to confirm a couple of things you guys already probably know:

1. The workaround that another user posted a few betas ago and stopped working after one of the updates (Beta 4 or Beta 5): launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
THIS CONTINUES NOT TO WORK BUT WAS A GOOD SOURCE OF HOPE DURING EARLIER BETAS.

2. Again, sorry if redundant - the DisplayLink Hardware still shows up in the USB Section of System Information (accessible via "About This Mac").

The OS definitely responds to the device but sadly just to display a constant blank screen.

I wish I could remember the last time I checked "Displays" under system preferences, but it's been at least 2 Betas or so. Under this Pref Pane I used to see the Arrange Tab and the option to gather all screens. It's weird (at least to my level of knowledge) that the above are not present in this pref pane but I guess it makes sense to an extent as I can no longer move the pointer with the trackpad off either the built in display or the one attached via TB. I wish I could remember when this behavior started. I can't say for certain, but it was one of the last Betas (maybe 6?). Prior to that, I could move my pointer to the blacked out screen and take a screen shot which when opened showed the display as it usually looked as if it was hidden behind a black screen sized rectangle.

Thanks to everyone who's been sharing - at least I've had the consolation from my fellow users that their DL hardware is not functioning either.

Hope to see some news soon.....thnx.

[uncplayer23]

I just got this from the manufacturer of my dock:

Thank you for being a Plugable Triple Display Docking Station user.

If this product is being used with a Mac, we have important news about macOS 10.13.4. This new macOS release only supports displays which are directly provided by a GPU or via AirPlay.

For this dock, this means versions of Apple macOS after 10.13.3 will only support the single 4K HDMI port on the dock which uses DisplayPort Over USB-C technology (which is directly GPU connected). The second and third displays on the dock -- the DVI and 2K HDMI ports using DisplayLink technology -- will no longer function. Windows and Chromebook computers are not affected, and will continue to work as usual.

TAKE ACTION

To continue to use all dock functions with your Mac, macOS updates must be disabled to remain on 10.13.3. To do so, uncheck the two highlighted boxes in the screenshot below. The boxes to uncheck (disable) are "Download updates in background" and "Install macOS updates" These are found in the "App Store" portion of "System Preferences" within macOS.

[Poly]

This new macOS release only supports displays which are directly provided by a GPU or via AirPlay.

For this dock, this means versions of Apple macOS after 10.13.3 will only support the single 4K HDMI port on the dock which uses DisplayPort Over USB-C technology (which is directly GPU connected). The second and third displays on the dock -- the DVI and 2K HDMI ports using DisplayLink technology -- will no longer function

Wow, this is huge! Did Apple just close the door for any DisplayLink technology for good? :(




1. DisplayLink software installs and acts like a normal display on the host. It detects monitors connected through a DisplayLink device and presents them to the operating system (for example Windows) as if they were normally attached monitors.

2. The OS then creates frame buffers for each display and the OS puts the display content there. <- Is that the part where 10.13.4 breaks the driver, since it's not a Thunderbolt 3 device?


3. The DisplayLink driver then picks up the pixels in the frame-buffer, encodes them and send them to the DisplayLink device.

4. The DisplayLink device then decodes these frame buffers and presents them to standard video interfaces like VGA, HDMI or DisplayPort. An on-board frame buffer means the DisplayLink driver only needs to send changes to the screen content. It can also adapt the compression so that the link is shared equitably with other services while maintaining high quality.

[Alanant]

Just a heads up. I needed to reboot the DisplayLink device for my external monitors to show up after installing the 4.3 beta.

[dolphinman]

Dear all

As you have found, the released 10.13.4 update does not change the issues seen with the betas. It causes 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 have been 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.

Wim
---------------------------
Please forgive the redundant question:
(Re: ASUS MB169B+ DisplayLink drivers for High Sierra 10.13.4 update).

How soon will you have this resolved (a week, a month)?
This is ultra urgent for me, as it is for others. Please let me know something.
Thank you so much!

[tommiy]

Reading between the lines given that the issue has existed throughout the beta's and has not been solved I think that you may say it could be a very long time before displaylink is functional again.

I tried to post a issue in the Apple forums related to this problem and it was removed because 'i ranted' over the poor quality of apple bug fix releases that break existing used functionality and is not disclosed in release notes.



---------------------------
Please forgive the redundant question:
(Re: ASUS MB169B+ DisplayLink drivers for High Sierra 10.13.4 update).

How soon will you have this resolved (a week, a month)?
This is ultra urgent for me, as it is for others. Please let me know something.
Thank you so much!

[pmontelo]

I'm going to give this a try, I hope this helps someone else out:

https://support.apple.com/kb/PH25593?locale=en_US

[dolphinman]

Thanks for the advice. I was hoping to stick it out for at least a week. I may just have to revert back to 10.13.3 and wipe all my data just so this puppy will work.
OR...I guess I'm shipping back and exchanging my ASUS MB169B+ (which was working beautifully with my MB Pro (mid-2015, retina) until the 10.13.4 update. Thanks.

[dolphinman]

Thanks for the advice. I was hoping to stick it out for at least a week. I am now wiping all my data and reverting back to Sierra...all just so this monitor will work.
(ASUS MB169B+ MB Pro (mid-2015, retina).

Looking forward to the Display Link fix on OSX High Sierra 10.13.4! This is crazy.

[Poly]

How can I figure out the chipset my docking station is using, e.g. DL-3000 or DL-5000? I pulled this from the sys info:

HP Elite USB-C Docking Station:

Product ID: 0x4354
Vendor ID: 0x17e9 (DisplayLink (UK) Ltd.)
Version: 31.18

[Noodles]

Looks like it is not just displaylink thats broken. Duet displays have something very similar on there website

https://help.duetdisplay.com/faq/305404-macos-10-13-4-support

Think apple have changed something in 10.13.4 that is affecting extra displays and it is not just a displaylink problem

N

[clayq]

I just bought a Startech Triple-dock approx 1 week ago, was working great then upgraded to MacOS 10.13.4 yesterday. Had a WTF moment, did some googling and found this thread. I am coming up for a new laptop purchase soon, if Apple do not fix this issue I will be seriously considering purchasing something else!

[Wozzy]

So this is a mess.

We have spent thousands of $'s on DisplayLink hubs for a single cable solution on our desks.

Hoping this is to be addressed by Apple/DL in a supplemental update and is not a permanent decision by Apple as that would be ludicrous.

[DLguy]

Still doesn't work with todays update
Even though it says it added support for external graphics processors eGPU

[Kabrown]

Real simple question, how long till this is fixed? At present, you have a lot of users with money poured down a rathole until this is working again A time frame for solution would be good and would go miles from having this escalated to the FTC.

[Wozzy]

Real simple question, how long till this is fixed? At present, you have a lot of users with money poured down a rathole until this is working again A time frame for solution would be good and would go miles from having this escalated to the FTC.

But is this Apples or DisplayLinks issue....or both.

[DLguy]

Both, apple ruined it for DL and DL needs to work on making updates to be compatible with the new OS

[bernie]

Both, apple ruined it for DL and DL needs to work on making updates to be compatible with the new OS

It may not be possible for DisplayLink to do anything if the problem is at the OS API level.

What if DisplayLink and the other affected companies simply have no ability to restore extended display support? What if only Apple can restore it to work as it did in 10.13.3?

[tommiy]

It may not be possible for DisplayLink to do anything if the problem is at the OS API level.

What if DisplayLink and the other affected companies simply have no ability to restore extended display support? What if only Apple can restore it to work as it did in 10.13.3?


Entirely possible and after 3 months of trying to get it to work with beta's and the requests from DisplayLink to log fault on the 10.13.4 release I would say that its in a position where only Apple can assist if they want to. If not then the use of MACs on this technology is history by the looks. I would have expected if it was possible after 3 months it would have already been done.

Time will tell but I guess that it depends on how generous Apple is wanting to be. I, myself, logged a fault and rolled back to 10.13.3.

[Alanant]

Unfortunately, this debacle is another example of the Apple Tax/Fanboy Fee. Our office is keeping pre-2017 Macs on 10.13.3 (spending hours reinstalling 10.13.3 on the ones that have already upgraded). For thunderbolt three capable Macs we are looking at purchasing non-DisplayLink docks for several hundred dollars apiece. Not sure what we will do with the pre-2017 10.13.3 Macs when the next security-related vulnerability hits...

[Alanant]

Entirely possible and after 3 months of trying to get it to work with beta's and the requests from DisplayLink to log fault on the 10.13.4 release I would say that its in a position where only Apple can assist if they want to. If not then the use of MACs on this technology is history by the looks. I would have expected if it was possible after 3 months it would have already been done.

Time will tell but I guess that it depends on how generous Apple is wanting to be. I, myself, logged a fault and rolled back to 10.13.3.

I agree, Apple are not going to fix this.

[Teledatageek]

Unfortunately, this debacle is another example of the Apple Tax/Fanboy Fee. Our office is keeping pre-2017 Macs on 10.13.3 (spending hours reinstalling 10.13.3 on the ones that have already upgraded). For thunderbolt three capable Macs we are looking at purchasing non-DisplayLink docks for several hundred dollars apiece. Not sure what we will do with the pre-2017 10.13.3 Macs when the next security-related vulnerability hits...

Having just purchased a couple of USB-C docks from Startech, this makes me very unhappy.

Two questions:

1. What non-DisplayLink docks are you looking at? I need to drive two monitors and haven't found a non-DisplayLink dock that does that.

2. This is an opinion question - but if Apple doesn't ever fix this or it drags on like it already has - should the dock manufacutuers provide a refund since the product is not performing as advertised? Personally, I think so. Sure, they can blame Apple, DisplayLink, etc. but in the end they sold a product that relied on that technology...

Thanks!

[chops]

Unfortunately, this debacle is another example of the Apple Tax/Fanboy Fee. Our office is keeping pre-2017 Macs on 10.13.3 (spending hours reinstalling 10.13.3 on the ones that have already upgraded). For thunderbolt three capable Macs we are looking at purchasing non-DisplayLink docks for several hundred dollars apiece. Not sure what we will do with the pre-2017 10.13.3 Macs when the next security-related vulnerability hits...

May I ask how you rolled back? I spent hours and ended up going back to 10.12.6 since I couldn’t find a way to install only 10.13.3. I do not have Time Machine backups.

[Alanant]

May I ask how you rolled back? I spent hours and ended up going back to 10.12.6 since I couldn’t find a way to install only 10.13.3. I do not have Time Machine backups.

You can only easily reinstall the version that your Mac came with (I guess 10.12.6 in your case).

We have the 10.13 5.2 GB DMG file from when it first came out. You might be able to find it on the internet. Once it was installed, I installed the 10.13.3 Combo update which is still hosted by Apple.

[flaxton]

As someone else mentioned, Duet Display also ceased to work with 10.13.4 :confused:

However, they have issued a beta driver that is working for me, and they indicate a stable driver is expected in a few weeks.

So I'm back up and running, extending my MacBook Pro 13" display onto my iPad Pro 12.9" with Duet Display.

An interesting thing I had not noticed before - they seem to be using AirPlay to do this. I don't think that was the case before.

While connected, the Displays icon shows in the menu bar and is blue - clicking it shows an active AirPlay connection.

I don't know if Displaylink could do something similar or not.

I've attached screenshots of the menu bar, Displays arrangement, and iPad Displays screen.

[slvrscoobie]

wow - sounds like this was a big ol mess! Ive also been looking at other options (monitors with Displayport Out, ect) but apparently that is Also not supported by OSX.
So other than buying a Thunderbolt Display, are we out of options for 2nd monitors?
Seems like apple is screwing a fairly large section of 3rd party accessories

[Alanant]

I've been reviewing options so I thought I'd share them with everyone. If you have any other suggestions, please share.

For the 2017 and newer Macs, a Thunderbolt 3 to Dual HDMI 2.0 Adapter for about $90. You could leave the display link hardware connected for the Ethernet, USB etc.

For the 2017 and newer Macs, the CalDigit TS3 Plus can drive two 4k monitors with the use of a Thunderbolt 3 to Dual HDMI 2.0 Adapter. This combo would replace the display link hardware at a cost of about $390.

For the 2017 and newer Macs, a Sonnet Radeon RX 570 eGFX Breakaway Puck would add an eGPU and the ability to connect to four monitors. $600. They have a 560 for about half the price but it's not on Apples supported hardware list.

For the 2017 and newer Macs, you can build your own breakout box. Boxes start at $200 and you can choose your own graphics card from a supported list. Probably looking at $700 on the low end all up.

Our display link hardware was very reasonable in comparison!

[tommiy]

I also looked at MST with Displayport. Seems that the chipset works to produce multiple displays but OSX does not support it. I read some one else with boot camp could boot into windows with MST running with dual displays but return to OSX and extension no longer functions. Guess its apple all the way around. You should only work with a single monitor.[

QUOTE=slvrscoobie;85647]wow - sounds like this was a big ol mess! Ive also been looking at other options (monitors with Displayport Out, ect) but apparently that is Also not supported by OSX.
So other than buying a Thunderbolt Display, are we out of options for 2nd monitors?
Seems like apple is screwing a fairly large section of 3rd party accessories[/QUOTE]

[Poly]

I also looked at MST with Displayport. Seems that the chipset works to produce multiple displays but OSX does not support it. I read some one else with boot camp could boot into windows with MST running with dual displays but return to OSX and extension no longer functions. Guess its apple all the way around. You should only work with a single monitor.

That person could have been me. I have an MST Display Port splitter as well.

https://www.i-tec-europe.eu/index.php?t=3&v=492

You can connect two monitors and extend your desktop on both. Works like a charm in Windows 10 via Bootcamp on my MacBook 12-inch. But unfortunately Apple never enabled MST support in macOS for Intel GPUs or via USB-C, however the built-in hardware supports it. Running USB-C in alt-mode gives you direct Display Port access. The MST standard has been around since 2009 – came with Display Port 1.2 standard. It's just Apple...

If you're a lucky owner of a Mac with a Thunderbolt 3 port (which I am not :( ), then you can run two displays from a single port. Not sure if uses MST or something else though.

It seems Apple is pushing aggressively Thunderbolt 3 as the only option for any accessories. But that reminds me of the sad story with Thunderbolt 1 and 2. The docks were expensive, hard to get, and with the 10.13.4 update eGPU solutions were rendered obsolete. :)

If you ran an eGPU from your TB1/2 port you ended up with a blank screen as well last Friday.

[DLguy]

So no solutions for people that have thunderbolt 2 and usb 3.0 on a MacBook Pro?

[tommiy]

That person could have been me. I have an MST Display Port splitter as well.

https://www.i-tec-europe.eu/index.php?t=3&v=492

You can connect two monitors and extend your desktop on both. Works like a charm in Windows 10 via Bootcamp on my MacBook 12-inch. But unfortunately Apple never enabled MST support in macOS for Intel GPUs or via USB-C, however the built-in hardware supports it. Running USB-C in alt-mode gives you direct Display Port access. The MST standard has been around since 2009 – came with Display Port 1.2 standard. It's just Apple...

If you're a lucky owner of a Mac with a Thunderbolt 3 port (which I am not :( ), then you can run two displays from a single port. Not sure if uses MST or something else though.

It seems Apple is pushing aggressively Thunderbolt 3 as the only option for any accessories. But that reminds me of the sad story with Thunderbolt 1 and 2. The docks were expensive, hard to get, and with the 10.13.4 update eGPU solutions were rendered obsolete. :)

If you ran an eGPU from your TB1/2 port you ended up with a blank screen as well last Friday.



Geez its getting worse at every corner.

How do you get USB-C to run 2 monitors in extended mode? Without MST they are simply clones with display port. With windows they work extended.

[Bob Johnston]

I just installed the DisplayLink v4.3 driver (mirror only) and it's at least working for me. Any news on how the "extended display" driver update is coming? and when it might be released?

Thank you,

[phrogg]

Here is what I have done to get something working for myself again. I run 2 40" 4K monitors off my 2015 Macbook.

The first display is off the HDMI port from the AV adapter. The second display I was able to get back up and running by moving to the 4.3 Beta driver that only supports mirror mode. I then opened up the clamshell (which I usually keep closed) and load up SwitchResX. Now I can mirror the clamshell display which I can now set to run at 4K. So I have 3 displays (sorta) running on my macbook 2015 while I ignore the TEENY tiny fonts on the clamshell display itself.

[slvrscoobie]

Its not perfect, but why i hadnt thought about it before. Least I have 2 monitors again
Apple TV + HDMI = 2 monitors!
https://i.imgur.com/7GaGLNZ.png

[mdiorio]

Such a pain. I switched to the Dell WD-15 dock as that doesn't use DisplayLink. It gets me one external monitor, but not two, even though it has the capability to run two monitors in Windows. It seems that Apple limits it to a single external display on a thunderbolt port for some reason. The only solution I've been able to come up with is buying two Thunderbolt (USB-C) to Display Port adapters and I will have to plug in 3 cables when I dock.

[tommiy]

Such a pain. I switched to the Dell WD-15 dock as that doesn't use DisplayLink. It gets me one external monitor, but not two, even though it has the capability to run two monitors in Windows. It seems that Apple limits it to a single external display on a thunderbolt port for some reason. The only solution I've been able to come up with is buying two Thunderbolt (USB-C) to Display Port adapters and I will have to plug in 3 cables when I dock.

Yes Apple, unlike Microsoft, does not support MST through TB. Its an OSX limitation. This means you get mirrored monitors on TB but not extended.

[Poly]

Yes Apple, unlike Microsoft, does not support MST through TB. Its an OSX limitation. This means you get mirrored monitors on TB but not extended.

According to this product, macOS does only support dual monitors on a single cable via TB3. I'm not sure if it's MST. But see for yourself: https://www.i-tec-europe.eu/index.php?t=3&v=480

I get cloned screens when I connect an MST adapter via USB-C (USB 3.0 Gen 1) on my MacBook ( not Pro). The pro models have Thunderbolt 3 ports so it should work as pictured on that site.

However, using a MacBook 12-inch – which only has one USB-C port – a DisplayLink docking station was the only solution to connect two external monitors via a single cable. It was the perfect single cable solution until Apple broke it. :(

[phrogg]

So I'm using the 4.3 beta driver on my 10.13.4 system and had clone mode working fine for a day. Then I put the computer to sleep and woke it up and now it wants to clone the wrong monitor. Its cloning my external display and not my built-in display. Anyone know where/how to change that and choose which one is cloned by DisplayLink software?

[phrogg]

Just an FYI that a reboot switched which monitor it was cloning...but when I go to sleep it swaps to the other one. So there must be a setting somewhere I can access. Still hope to hear the answer.

[Alanant]

No change in 10.13.5 Beta 1.

[tommiy]

No change in 10.13.5 Beta 1.

A week into this and no news from displaylink as to what is happening. As its been months since the beta and it eas not fixed I think we all now know that the answer to this is probably the end of displaylink boxes. Looks like time to search for some thing else to use instead of display link or ditch the mac for windows instead.

[DLguy]

its Apple and displayLink that need to work together. Apple doesn't really care about other products that are compatible or not with their products. I think we all need to look for alternate solutions. DisplayLink made their money from us and now its time to move on.

[azink]

its Apple and displayLink that need to work together. Apple doesn't really care about other products that are compatible or not with their products. I think we all need to look for alternate solutions. DisplayLink made their money from us and now its time to move on.

Does anyone know any alternate products for USB video? I don't think this will be resolved quickly (if ever) but all USB external monitor solutions seem to be using DisplayLink...

[tommiy]

Does anyone know any alternate products for USB video? I don't think this will be resolved quickly (if ever) but all USB external monitor solutions seem to be using DisplayLink...

Think your going to need to go with thunderbolt as apple obviously see's USB is only for things like data transfer i suppose.

Its a shame but the lack of any response from DisplayLink on any progress at all probably means there is none.

[tommiy]

Think your going to need to go with thunderbolt as apple obviously see's USB is only for things like data transfer i suppose.

Its a shame but the lack of any response from DisplayLink on any progress at all probably means there is none.

Someone earlier asked about solutions that do not use DisplayLink. Plugable have published their solution for Macs now at the link below. As you guess no displaylink in any of these options. Seems time to move on. I'm off to try and buy one of these and ditch my current dock.

https://plugable.com/2018/04/04/alternative-video-output-solutions-macos-10-13-4-systems-ud-ultcdl-ud-ultc4k-docks/

[AlbanRampon]

Dear DisplayLink Mac Users,

Finding a solution to this issue remains the highest business priority within DisplayLink.
Our teams are investigating several potential workarounds that could enable some level of extended desktop functionality to be restored in 10.13.4. In parallel, we are continuing to explore with Apple routes to a permanent and complete solution.

In the meantime, we have today released a second beta of our 4.3 driver. Installing this driver will enable cloning of the native display on DisplayLink connected screens.
4.3 Beta 2 (http://www.displaylink.com/downloads/file?id=1131) improves the current workaround by preserving the primary display aspect ratio and allowing to select which screen is cloned in a multiple display setup.
We do not regard this as a long term solution and will continue to work hard on finding a path to restore extended display support on macOS.

Unfortunately, we are still unable to give dates for either a workaround or a complete solution. We will, however, update you on this thread as soon as we have further information to share.

We thank you for your patience as we work this problem.

Kind regards,
Alban

[tommiy]

Dear DisplayLink Mac Users,

Finding a solution to this issue remains the highest business priority within DisplayLink.
Our teams are investigating several potential workarounds that could enable some level of extended desktop functionality to be restored in 10.13.4. In parallel, we are continuing to explore with Apple routes to a permanent and complete solution.

In the meantime, we have today released a second beta of our 4.3 driver. Installing this driver will enable cloning of the native display on DisplayLink connected screens.
4.3 Beta 2 (http://www.displaylink.com/downloads/file?id=1131) improves the current workaround by preserving the primary display aspect ratio and allowing to select which screen is cloned in a multiple display setup.
We do not regard this as a long term solution and will continue to work hard on finding a path to restore extended display support on macOS.

Unfortunately, we are still unable to give dates for either a workaround or a complete solution. We will, however, update you on this thread as soon as we have further information to share.

We thank you for your patience as we work this problem.

Kind regards,
Alban



Ok that sounds like a commitment that the original capabilities will not be returned even when if a new driver is delivered. Guess it really is time to find the alternative.

[DevNull]

Dear DisplayLink Mac Users,

Finding a solution to this issue remains the highest business priority within DisplayLink.
Our teams are investigating several potential workarounds that could enable some level of extended desktop functionality to be restored in 10.13.4. In parallel, we are continuing to explore with Apple routes to a permanent and complete solution.

In the meantime, we have today released a second beta of our 4.3 driver. Installing this driver will enable cloning of the native display on DisplayLink connected screens.
4.3 Beta 2 (http://www.displaylink.com/downloads/file?id=1131) improves the current workaround by preserving the primary display aspect ratio and allowing to select which screen is cloned in a multiple display setup.
We do not regard this as a long term solution and will continue to work hard on finding a path to restore extended display support on macOS.

Unfortunately, we are still unable to give dates for either a workaround or a complete solution. We will, however, update you on this thread as soon as we have further information to share.

We thank you for your patience as we work this problem.

Kind regards,
Alban

Thank you for the update and your perseverance on this issue. We appreciate that it can be difficult to work with Apple on this given how closed they are so fingers crossed that a solution is forthcoming. I'm sticking with 10.13.3 until then as DisplayLink is a great product.

[Poly]

Dear DisplayLink Mac Users,
Finding a solution to this issue remains the highest business priority within DisplayLink.
Our teams are investigating several potential workarounds that could enable some level of extended desktop functionality to be restored in 10.13.4. In parallel, we are continuing to explore with Apple routes to a permanent and complete solution.


Big thanks to the DisplayLink team for not giving up. I hope DisplayLink docks will be back to normal soon. Although you compress video data for USB and decompress on chip, have you explored this "hack" yet?

https://forums.macrumors.com/threads/4k-at-60hz-on-12-rmb-hack-monitors-cables-adapters-that-work.1974167/

What if you trick the macOS into "display port alt-mode" and transmit video data via the extra lanes? The DisplayLink SoC may needs a reprogramming for accepting data via Display Port than USB directly. The hack in the link above perhaps also requires macOS to allow support for MST – if you want to run two extended monitors, which it never did on Intel GPUs.

The downside is that USB 3 ports will drop to USB 2.0 due to lack of bandwidth.

I'm trying to give you ideas, although I might be wrong.


Ok that sounds like a commitment that the original capabilities will not be returned even when if a new driver is delivered. Guess it really is time to find the alternative.

There are no alternatives. DisplayLink's business model (unique selling point) is solely based on their proprietary compression technology, allowing them to squeeze a broad bandwidth video signal through a tight USB cable.

It seems Apple has fundamentally changed how frame buffers are passed on to external displays. As far as I understand the DisplayLink driver was sort of a Man-in-the-Middle hack – hijacking the frame buffers and compressing them for the USB's bandwidth bottleneck. Apparently, that trick doesn't work anymore. Now, if that's the case it does take more effort than just a few new lines of code.

We just have to be patient, stick with 10.13.3 for now, and hope everything will be fine again soon.

[torimorris1]

Has this issue been resolved for you? I am experiencing the same problem and am wondering if you've found a solution.

[torimorris1]

I am operating High Sierra 10.13 and my display is stuck in sleep mode. Have uninstalled and reinstalled the driver several times to no avail.

Please help me find a solution!

[phrogg]

Dear DisplayLink Mac Users,
In the meantime, we have today released a second beta of our 4.3 driver. Installing this driver will enable cloning of the native display on DisplayLink connected screens.
4.3 Beta 2 (http://www.displaylink.com/downloads/file?id=1131) improves the current workaround by preserving the primary display aspect ratio and allowing to select which screen is cloned in a multiple display setup.

Since this is a new solution, how about some quick documentation of how to choose and set which monitor is cloned? I'm not seeing a place to make that choice right now.

[anotherandrew]

Does anyone know any alternate products for USB video? I don't think this will be resolved quickly (if ever) but all USB external monitor solutions seem to be using DisplayLink...

MCT makes similar but inferior products. I have one (within a J5Create USB dock) but I do not recommend them. Since upgrading to High Sierra their driver has consumed high amounts of CPU and neither J5Create nor MCT seem willing to give the matter serious attention. Even when it was working prior to High Sierra it was a rather poor solution.

I have numerous DisplayLink adapters (USB2 and USB3) and they're all working very well on this 2012 11" Air (running 10.13.3) and I'm confident that DisplayLink will have this resolved as quickly as possible.

[aehsmu]

Didn't think it would matter, but first beta of 10.3.5 does not change the DisplayLink problem.
--
Eric H.
--

[challgren]

I did happen to find a alternative solution, Matrox DualHead2Go Digital ME works with macOS 10.13.4 its a bit more expensive than a DisplayLink adapter but it works in 10.13.4. Basically splits the display in 2. The dock and title bar end up split between the screens but it works

[Okibi]

Thank you! Please keep the pressure on Apple.

Is there anywhere Mac users can register their annoyance / frustration to help convince Apple to fix this bug asap?

I initially bought a pair of the apple USB-C to HDMI adapters, these were absolutely junk, each time I woke my brand new power mac it would hunt for monitors, connect them, then disconnect them, connect them again and get stuck in a loop requiring me to disconnect the monitors and add them back on, one by one.

I bought a nice plugable dock to overcome Apples useless dongles making my MacBookPro usable once more.

Apples latest update has me stuck using their crappy dongles again. There was a time when Apple prided themselves on their easy of use and quality of products (especially when using their own peripherals), these days they're bloody useless.

[Poly]

Is there anywhere Mac users can register their annoyance / frustration to help convince Apple to fix this bug asap?


Since not everybody has an Apple's Developer ID, the only other way I could think of is via www.change.org

Alternatively, you can also vandalize (https://www.dailymotion.com/video/x4vdnry) in an Apple Store to express your frustration. :D

[slvrscoobie]

Does anyone know if you can clone the native display while its closed in Clamshell mode? I use mine thusly, so installing beta 2 would allow me to use 2 monitors (one displayport and the 'cloned native display') effectively. however if since the native display is off, and it wont work, doesnt help me much.

[Alanant]

It seems that Apple retail employees are aware of this issue. I needed to drop some hardware off for repair at my local Apple store. One of the hardware repairers, who also does time on the Genius Bar, acknowledge the DisplayLink issue and confirmed that the hardware can come back with 10.13.3 installed (as per my request).

[strim]

Just want to share my temporary workaround to continue normal life with 10.13.4 with 3 monitors connected to MacBookPro 2015.

I used one DisplayLink adapter, so 3 monitors were connected over: DisplayPort, HDMI, DisplayLink. All had worked fine with clam-shell closed. After upgrade to 10.13.4 I installed the latest DisplayLink driver 4.3 beta 2, opened the laptop screen and set it to be cloned to the monitor connected over DisplayLink. DisplayLink driver clones the "main" monitor, i.e. the monitor that has menu bar in "Displays / Arrangement" system preferences. If your built-in display in not the "main" one, just drag menu bar to it in display arrangement settings.

To fix wrong resolution of the cloned screen I used DisableMonitor v1.92 utility, https://github.com/Eun/DisableMonitor. It allows to set any resolution to any connected monitor. My monitor wired over DisplayLink was just 1920x1080, so I enforced the resolution using the utility instead of original retina resolution of the built-in display.

[sla3k]

So after trying and trying and trying, and 2 sleepless nights I managed to revert my Mac to MacOS Sierra 10.12.6 and finally managed to get my 2 external displays to work.

MacBook Air (13-inch, Early 2015)
1.6 GHz Intel Core i5
4 GB 1600 Mhz DDR3 RAM
Intel HD Graphics 6000 1536 MB

This is as far as close I could get to MacOS High Sierra 10.13.3

For any poor soul like myself (just before now) who is still trying to get their Macs working with display link adapters and trying to downgrade, this might be helpful.

Steps:
1. Install the OS that came pre-installed with your Macbook (pro, Air etc. etc.). If you are at 10.12.4 or higher (which I am guessing you are, otherwise you won't be looking at this post), there is a nifty feature that you can use to revert your mac back to factory defaults.

PS. ALL YOUR DATA WILL BE LOST, SO MAKE SURE TO BACK IT UP BEFORE ATTEMPTING.

Restart your macbook, press and hold: SHIFT + OPTION + COMMAND + R keys (you would need both hands, I tried to use one but could not, maybe you get lucky, lol).

2. Once the rotating globe appears, you can let go of the keys and it will download just a bunch of bootable files to kick off the installation.

3. In the new window that appears, click on Disk Utility and Erase/format your main disk (format with Mac OS extended).

4. Quit the Disk Utility and click on Recover Mac OSX (in my case it is OSX Yosemite, 10.10.5 with which my Mac was shipped). Let it do the rest, once the installation is complete, you can follow the on-screen instructions and get into the OS.

5. Next part comes from App Store. From this link, https://support.apple.com/en-us/HT208202, click on "Get macOS Sierra." in the middle of page somewhere (it will be in blue highlighted text) which will opn App Store. Click on "Get".

6. From here, follow the onscreen steps once the download completes. It might take a lot of time depending on your internet connection, download is about 5.6 GB.

7. Once all is set, you can download DisplayLink drivers version 4.1 and it will work.

I have tested it with my Mac and it worked like a charm.

I downgraded from High Sierra to Sierra but at least I got my two external screens working.

Any comments/corrections are welcome.

Thanks.

[DLguy]

Installed the new beta driver and it mirrors. Works as noted, however my screen resolution is not adjustable. I have a black bar on each side of my external monitor as there is no place for adjustments.

[Wozzy]

Installed the new beta driver and it mirrors. Works as noted, however my screen resolution is not adjustable. I have a black bar on each side of my external monitor as there is no place for adjustments.

You need to go back read the advice.

The mode in the beta driver is not mirror mode its clone mode, therefore the resolution and the aspect ratio cant be changed. The software is doing exactly what DisplayLink say.

in 4.3 beta 2 there is no mirror and no extended desktop just clone mode.

[strim]

The resolution of cloned monitor can be changed, please read my post above. The utility DisableMonitor, https://github.com/Eun/DisableMonitor does the work.

[phrogg]

The resolution of cloned monitor can be changed, please read my post above. The utility DisableMonitor, https://github.com/Eun/DisableMonitor does the work.

And I was able to change my resolution through SwitchResX (http://www.madrau.com/). When I plug in my DL device, it automatically changes to 4K resolution (which is unreadable on my laptop) and clones it perfectly to the connected monitor.

[Teledatageek]

Returning the USB-C docks and have Thunderbolt 3 docks on the way. Two monitors vs. three, but at least more than one!

[gpsutter]

It works for me.

[gpsutter]

It works for me.

Sorry, my comment got separated. I was referring to clamshell mode, which works for me. At least I don't have to stare at a dead monitor.

[tommiy]

If I am not mistaken its been 12 days since any official word from DisplayLink on this matter. Its really beginning to look like these are now toast. Even over in the apple support thread the focus is on finding different solutions rather than holding out that Apple will assist to fix this. I don't think anyone thinks that Apple even wants to try to support those that created a separate industry that assisted in use of its devices in cross platform environments. Anyway, I've had to jettison my DisplayLink dock and go to an elgato due to the fact there is no known date when this will be fixed and no comms from DisplayLink on any kind of progress.

[Alanant]

10.13.5 Beta 2 does not fix the issue.

[paulgee31]

If I am not mistaken its been 12 days since any official word from DisplayLink on this matter. Its really beginning to look like these are now toast. Even over in the apple support thread the focus is on finding different solutions rather than holding out that Apple will assist to fix this. I don't think anyone thinks that Apple even wants to try to support those that created a separate industry that assisted in use of its devices in cross platform environments. Anyway, I've had to jettison my DisplayLink dock and go to an elgato due to the fact there is no known date when this will be fixed and no comms from DisplayLink on any kind of progress.

We've been here many times before. It takes time, often weeks before a set of drivers are released that offer a fix or partial fix but considering I've been using the same DisplayLink device since 2011 I can't complain about the support.

[strim]

I agree, DisplayLink is trying their best. They created 4.3 beta to clone displays pretty quickly. With adjusted screen resolution that provides workaround for me. Likely the proper solution depends on Apple side, while Apple seems to care not too much of the issue.

[tommiy]

Yes agree they may try their best but its now 3 months since the start of this thread and in that time there has been minimal information from DisplayLink on any progress. Thats a quarter of a year. If they can not manage to get any prospect that are worth informing people about in 12 weeks then I can not hold my breath for another 12 weeks to return to having multiple dislays. I had to purchase something else. It was my choice I agree but the lack of support engagement drove me there.

[Poly]

If they can not manage to get any prospect that are worth informing people about in 12 weeks then I can not hold my breath for another 12 weeks to return to having multiple dislays. I had to purchase something else. It was my choice I agree but the lack of support engagement drove me there.

You're getting a bit overemotional here, but it's totally understandable. As a private person at home you have more options to choose from, in enterprise environments you have to stick with the approved hardware a while longer, which is even more frustrating.

My guess is that without Apple support there is no easy way to fix this. Hopefully, with the final release of 10.13.5 both parties i.e. DisplayLink and Apple, will have sorted it out. I'm still on 10.13.3

There is one positive thing I noticed with the latest beta driver. It seems audio is now being directly delivered via HDMI, no need to plug in AUX jack separately. :) If only HDCP would have also worked eventually... But you still can't watch any HDCP protected movies via DisplayLink. *gasp*

[tommiy]

Actually I think I understand how I feel and I am not getting over emotional. I was over emotional when this became an enterprise issue and the company I worked for decided that this was the straw that broke the camels back and now no longer supports Macs within the environment at all. You see there was nothing publised in release notes by Apple that upgrading would break anything and so the extra work to rollback alot of Macs resulted in getting given a windows machine instead. They waited a couple of weeks and then decided that they could not continue on without support of knowing it would be corrected and the easiest, fastest, and cheapest solution was to get rid of Macs.

So, its at home now, becoming less of a work horse into a home use only paradigm. This seems to be what apple wants.

So not over emotional at all. I now have a windows machine for work that functions with DisplayLink even after microsoft push out updates. It also has USB-C ports so my Apples accessories function with it. My only loss is needing to use windows during a working day.


You're getting a bit overemotional here, but it's totally understandable. As a private person at home you have more options to choose from, in enterprise environments you have to stick with the approved hardware a while longer, which is even more frustrating.

My guess is that without Apple support there is no easy way to fix this. Hopefully, with the final release of 10.13.5 both parties i.e. DisplayLink and Apple, will have sorted it out. I'm still on 10.13.3

There is one positive thing I noticed with the latest beta driver. It seems audio is now being directly delivered via HDMI, no need to plug in AUX jack separately. :) If only HDCP would have also worked eventually... But you still can't watch any HDCP protected movies via DisplayLink. *gasp*

[slvrscoobie]

You see there was nothing publised in release notes by Apple that upgrading would break anything

so you expect apple to release notes how EVERY third party driver and plug in will function after the update?

[Poly]

I was over emotional when this became an enterprise issue and the company I worked for decided that this was the straw that broke the camels back and now no longer supports Macs within the environment at all. You see there was nothing publised in release notes by Apple that upgrading would break anything and so the extra work to rollback alot of Macs resulted in getting given a windows machine instead. They waited a couple of weeks and then decided that they could not continue on without support of knowing it would be corrected and the easiest, fastest, and cheapest solution was to get rid of Macs.


The only thing I can criticize is the poor information management from Apple and DisplayLink! There was no warning ahead of the new update.

DisplayLink posted a warning on their download site way too late. Although, this topic existed for months already. A few people even thanked me at Macrumors forums for pointing out this severe bug. I guess, too many people updated carelessly and ended up with a useless DisplayLink device.

Most enterprise IT departments are hostile towards Macs. It has always been like that, because Macs are a niche product and expensive compared to cheap Dell/ HP laptops which you buy in bulk anyway. However, Windows is not always an option. Some software doesn't run on Windows e.g. design tools like Sketch, Flinto, and Xcode.

so you expect apple to release notes how EVERY third party driver and plug in will function after the update?
DisplayLink technology is being used across many major vendors. It's not some small 3rd party chop shop piece of hardware. So yes, Apple's QA failed here big.

[tommiy]

Apple has not respect for the ecosystem that their products are part of except when those products are apples. It has resulted in the decline in Macs over the years and its going to continue to be the decline of Macs. If Microsoft can perform major upgrades without crippling everything that is integrated their OS then only reason that Apple can not is because they do not wish to.



The only thing I can criticize is the poor information management from Apple and DisplayLink! There was no warning ahead of the new update.

DisplayLink posted a warning on their download site way too late. Although, this topic existed for months already. A few people even thanked me at Macrumors forums for pointing out this severe bug. I guess, too many people updated carelessly and ended up with a useless DisplayLink device.

Most enterprise IT departments are hostile towards Macs. It has always been like that, because Macs are a niche product and expensive compared to cheap Dell/ HP laptops which you buy in bulk anyway. However, Windows is not always an option. Some software doesn't run on Windows e.g. design tools like Sketch, Flinto, and Xcode.


DisplayLink technology is being used across many major vendors. It's not some small 3rd party chop shop piece of hardware. So yes, Apple's QA failed here big.

[paulgee31]

Apple has not respect for the ecosystem that their products are part of except when those products are apples. It has resulted in the decline in Macs over the years and its going to continue to be the decline of Macs. If Microsoft can perform major upgrades without crippling everything that is integrated their OS then only reason that Apple can not is because they do not wish to.

Unfortunately Microsoft can't perform an update without crippling entire machines. Just do a Google for "Windows 10 Creators or Fall Update won't boot" and you'll see a host of unhappy users rebuilding their machines or performing PC voodoo to resurrect their computer.

However I agree it is a great pity that Apple steamrollers architectural changes without working more with 3rd parties.

[pattie]

I came here with the same issue. But it sounds like there is a beta version of the driver that may work? Unfortunately displaylink.com seems to be down at the moment.

[Wozzy]

Apple have released Security Update 2018-001

https://support.apple.com/kb/DL1963?viewlocale=en_US&locale=en_US

is DL fixed?

[slvrscoobie]

Apple have released Security Update 2018-001

https://support.apple.com/kb/DL1963?viewlocale=en_US&locale=en_US

is DL fixed?

https://support.apple.com/en-us/HT208742
"Security Update 2018-001
Released April 24, 2018

Crash Reporter

Available for: macOS High Sierra 10.13.4

Impact: An application may be able to gain elevated privileges

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

CVE-2018-4206: Ian Beer of Google Project Zero

LinkPresentation

Available for: macOS High Sierra 10.13.4

Impact: Processing a maliciously crafted text message may lead to UI spoofing

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

CVE-2018-4187: Zhiyang Zeng (@Wester) of Tencent Security Platform Department, Roman Mueller (@faker_)"

[Wozzy]

https://support.apple.com/en-us/HT208742
"Security Update 2018-001
Released April 24, 2018

Crash Reporter

Available for: macOS High Sierra 10.13.4

Impact: An application may be able to gain elevated privileges

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

CVE-2018-4206: Ian Beer of Google Project Zero

LinkPresentation

Available for: macOS High Sierra 10.13.4

Impact: Processing a maliciously crafted text message may lead to UI spoofing

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

CVE-2018-4187: Zhiyang Zeng (@Wester) of Tencent Security Platform Department, Roman Mueller (@faker_)"

Don't expect Apple put anything in there release notes about it being fixed.

[tommiy]

Don't expect Apple put anything in there release notes about it being fixed.

Not even going to attempt to try it on my now home Mac to even find out. I don;t trust Apple and whatever else they may have packaged in here that will result in me loosing hours. I'll wait to see someone else offer up whats broken in forums.

[pattie]

Steps I tried:

Downloaded update
Confirmed did not work with restart (still showing cloned desktop)
Uninstalled DisplayLink beta driver
Restarted
Confirmed did not work (black screen)
Installed current latest release of display link driver
Restarted
Confirmed did not work (black screen)

[pasaporte]

Steps I tried:

Downloaded update
Confirmed did not work with restart (still showing cloned desktop)
Uninstalled DisplayLink beta driver
Restarted
Confirmed did not work (black screen)
Installed current latest release of display link driver
Restarted
Confirmed did not work (black screen)


Hello,

I can confirm that:

- After removing the beta drivers and reboot
- Download Apple Security update 2018-001
- Install DisplayLink 4.1 Drivers (not beta ones)
- Reboot

Thats was working for me.

[AlbanRampon]

Dear DisplayLink macOS users,

As we previously advised, we are aware that installing macOS version 10.13.4 will cause DisplayLink connected displays to go blank after the OS update, with the latest DisplayLink driver release 4.1 installed.

Extended displays continue to work as expected in macOS 10.13.3 - this is why we recommend remaining on macOS 10.13.3 or earlier at this time. Functionality such as Ethernet and audio, where implemented, is unaffected on macOS update.

DisplayLink has committed significant resources to finding a way to restore extended mode display support in a future release of macOS.
We have made solid progress towards identifying a solution, however our team needs to complete more work before we can communicate a release plan for a driver that will restore extended mode displays.

In the meantime, DisplayLink driver 4.3 Beta 2 (http://www.displaylink.com/downloads/file?id=1131) enables clone mode, but not extended mode, displays in 10.13.4. Users who have already updated to 10.13.4 should install that driver.

We will update you on this thread as soon as we have further details to share.
Thank you for your continued patience and we appreciate your feedback and support.

Kind regards,
Alban

[Carlow202]

Hello,

I can confirm that:

- After removing the beta drivers and reboot
- Download Apple Security update 2018-001
- Install DisplayLink 4.1 Drivers (not beta ones)
- Reboot

Thats was working for me.

This did not work for me...

[slvrscoobie]

Dear DisplayLink macOS users,

As we previously advised, we are aware that installing macOS version 10.13.4 will cause DisplayLink connected displays to go blank after the OS update, with the latest DisplayLink driver release 4.1 installed.

Extended displays continue to work as expected in macOS 10.13.3 - this is why we recommend remaining on macOS 10.13.3 or earlier at this time. Functionality such as Ethernet and audio, where implemented, is unaffected on macOS update.

DisplayLink has committed significant resources to finding a way to restore extended mode display support in a future release of macOS.
We have made solid progress towards identifying a solution, however our team needs to complete more work before we can communicate a release plan for a driver that will restore extended mode displays.

In the meantime, DisplayLink driver 4.3 Beta 2 (http://www.displaylink.com/downloads/file?id=1131) enables clone mode, but not extended mode, displays in 10.13.4. Users who have already updated to 10.13.4 should install that driver.

We will update you on this thread as soon as we have further details to share.
Thank you for your continued patience and we appreciate your feedback and support.

Kind regards,
Alban

Hi Alban,
Thanks for the update.
I think MANY of us would be willing to work with DL as even Alpha testers if it helps you know more about what works, what doesn't, and what needs to be addressed as you work out a solution. Many hands make light work.

[pattie]

Hello,

I can confirm that:

- After removing the beta drivers and reboot
- Download Apple Security update 2018-001
- Install DisplayLink 4.1 Drivers (not beta ones)
- Reboot

Thats was working for me.

Was it working in extended mode?

I appreciate DisplayLink is working on this! Unfortunately I did not realize there was an issue until I had applied Apple's update, and I don't see an easy way to revert the update without wiping the data from my computer (which is a non-starter).

[smp999]

Hello,

I can confirm that:

- After removing the beta drivers and reboot
- Download Apple Security update 2018-001
- Install DisplayLink 4.1 Drivers (not beta ones)
- Reboot

Thats was working for me.

Did not work for me.

FYI - I registered with this forum just to say thanks to DisplayLink for your attention to this matter. I was going to downgrade my MacOS based on the instructions a few pages back, but the communication from DIsplayLink, I think I will wait a bit longer.

[pasaporte]

Did not work for me.

FYI - I registered with this forum just to say thanks to DisplayLink for your attention to this matter. I was going to downgrade my MacOS based on the instructions a few pages back, but the communication from DIsplayLink, I think I will wait a bit longer.

It work for me just try it with HDMI-HDMI CABLE and yes got extend mode.

[pasaporte]

This did not work for me...

Did you tried with HDMI-HDMI cable. That’s was tested in 2 different laptops and was work.

[Poly]

DisplayLink has committed significant resources to finding a way to restore extended mode display support in a future release of macOS.

Thank you for your latest update. Since you wrote "in a future release of macOS", I suppose it will be the 10.13.5 version or a later version?

[pacmanbneNL]

Thank you for your latest update. Since you wrote "in a future release of macOS", I suppose it will be the 10.13.5 version or a later version?

I am running 10.13.5 V2 Beta (17F45c) and its not fixed there

[Amarriner]

Hello,

I can confirm that:

- After removing the beta drivers and reboot
- Download Apple Security update 2018-001
- Install DisplayLink 4.1 Drivers (not beta ones)
- Reboot

Thats was working for me.

I tried this and now my second screen is still a clone of my mac screen but showing half the size.

[J.Cornelius]

First, let me say that I love Satechi products and have purchased several.

I can not work without two monitors and it now has been several weeks since my monitors stopped working. I had to purchase a couple of dongles to fix the problem but at $69 bucks each, I keep returning them before the return window closes. Enough just fix the problem already!

This is not the first time this has occurred with a MacOS update but hopefully the last. I realize you all are working hard to correct the issue but in the meantime your customers, well at least this one, is running out of patience!

Let's get it done people!

[pasaporte]

I tried this and now my second screen is still a clone of my mac screen but showing half the size.
If its cloned you need to remove the beta driver, and this way just work with HDMI-HDMI Cable.

Regards,

[make dsplyLink gr8t again]

To the good folks at DisplayLink,

I realize there's nothing new to be said here until you fix this issue. I also realize Apple broke it. However, Apple broke this connection in the 10.13.4 beta, so you've known about this for a while. Also, controlling external displays is literally all your product does, and now it doesn't do that, so it's not even really a product anymore, it's just a piece of expensive plastic.

I rely heavily on the "extended screen" feature to do my work and without it, I'm pretty screwed. It's been 3 months since the first post (just on this forum). I know it's complicated, otherwise I assume you or the internet gnomes would have sorted it out by now. I have followed the latest news on this forum daily, in hopes of any good news, however all I have read is DisplayLink placating the concerned citizens of this forum.

As a long time DisplayLink user, it saddens me to ask the other members of this forum, but here it goes: good folks of the extended display world, do you know of any other display extension products out there that can use (1) USB or (2) "Mini DisplayPort output with support for DVI, VGA, and dual-link DVI" ports? -thanks

Needing solution ASAP

[tommiy]

Ahh yes continue to live with the security risks that 10.13.4 identified that existed in 10.13.3 and now even the security patches that have come in 10.13.4 for probably the next x number of months. My security team is no happy with that solution in the enterprise. But hey, if some thing is exploited because your still on 10.13.3 then whose problem is it? Obviously your because you made the decision to stay on 10.13.3 and follow a recommendation.

Its no where near a preferred outcome to remain on 10.13.3 for many months and ignore security updates. This day and age that is simply dangerous.

[Okibi]

G'day Alban,

Thanks for giving an update (more than Apple bother to do although we spend thousands on their PCs).

Happy to buy your devs a coffee if it helps them find a solution faster.

[pattie]

No news in the last week? :/

[MC Ren]

Yeah, would be really nice to get an update. I travel all the time for business, so do my co-workers and we all rely heavily on having dual monitors. We are a bit annoyed on the time it's taking to address the issue.

[AlbanRampon]

Dear DisplayLink macOS users,

We are aware that installing macOS version 10.13.4 will cause DisplayLink connected displays to go blank after the OS upgrade, with the latest DisplayLink driver release 4.1 installed. Extended displays continue to work as expected in macOS 10.13.3, and we recommend that you stay on macOS 10.13.3 or earlier if you require this feature, and have not already upgraded. Functionality such as Ethernet and audio, where implemented, is unaffected.

Our team has made some solid progress towards finding a solution which would restore extended display support in a future release of macOS. We are still unable to provide a timeframe or a date for release of this solution.
Meanwhile, we have been developing a partial workaround solution which would add one extended USB display (up to 1080p) on macOS 10.13.4. We are aiming to release a preview version of this driver in around 7 to 10 days. The precise date depends on how the solution performs under deeper and wider testing, and how long it takes to resolve remaining issues. We expect the driver to enable one extended 1080p screen, and one cloned screen connected to a DisplayLink device. There may be some other functional limitations.
The new alpha driver will be posted online as soon as possible.

Until then, DisplayLink driver 4.3 Beta 2 (http://www.displaylink.com/downloads/file?id=1131) enables clone mode, but not extended mode displays in 10.13.4.

We will update this thread as soon as we have further details to share.
Thank you for your continued patience and we appreciate your feedback and support.

[slvrscoobie]

[B]Meanwhile, we have been developing a partial workaround solution which would add one extended USB display (up to 1080p) on macOS 10.13.4.

Thats all I need! Please hurry! :D

[smp999]

yep - all I need is one extra monitor

[paulgee31]

That will do me just fine.

[Poly]

We expect the driver to enable one extended 1080p screen, and one cloned screen connected to a DisplayLink device. There may be some other functional limitations.


Thanks for the update! At least some progress, but up to 1080p? One extended screen? That doesn't sound very exciting, yet. The beauty of using a DisplayLink docking station was having two extended screens running via a single cable.

I hope the team will be able to restore full functionality soon.

The longer we wait the more likely 10.13.5 will be released and some users, like me, will only be able to update straight to .5 – skipping the .4 version entirely. Please consider that when testing new drivers.

[aehsmu]

Looking forward to the workaround. In my case, that's all that's needed!

Thanks!

[make dsplyLink gr8t again]

Dear DisplayLink macOS users,

We are aware that installing macOS version 10.13.4 will cause DisplayLink connected displays to go blank after the OS upgrade, with the latest DisplayLink driver release 4.1 installed. Extended displays continue to work as expected in macOS 10.13.3, and we recommend that you stay on macOS 10.13.3 or earlier if you require this feature, and have not already upgraded. Functionality such as Ethernet and audio, where implemented, is unaffected.

Our team has made some solid progress towards finding a solution which would restore extended display support in a future release of macOS. We are still unable to provide a timeframe or a date for release of this solution.
Meanwhile, we have been developing a partial workaround solution which would add one extended USB display (up to 1080p) on macOS 10.13.4. We are aiming to release a preview version of this driver in around 7 to 10 days. The precise date depends on how the solution performs under deeper and wider testing, and how long it takes to resolve remaining issues. We expect the driver to enable one extended 1080p screen, and one cloned screen connected to a DisplayLink device. There may be some other functional limitations.
The new alpha driver will be posted online as soon as possible.

Until then, DisplayLink driver 4.3 Beta 2 (http://www.displaylink.com/downloads/file?id=1131) enables clone mode, but not extended mode displays in 10.13.4.

We will update this thread as soon as we have further details to share.
Thank you for your continued patience and we appreciate your feedback and support.

Thank you DisplayLink. One extended USB display would be great.

[J.Cornelius]

That is complete and utter horse sh$t! Seriously, you may have a solution with a future MacOS update? Really? Maybe one extended monitor? Terrible....

[smp999]

That is complete and utter horse sh$t! Seriously, you may have a solution with a future MacOS update? Really? Maybe one extended monitor? Terrible....

Yeah - until you know more about the details as to why this happened, I wouldn't be casting blame at DisplayLink.

[Alanant]

No change in 10.13.5 Beta 3.

[MC Ren]

That is complete and utter horse sh$t! Seriously, you may have a solution with a future MacOS update? Really? Maybe one extended monitor? Terrible....

I'm with you. They may have a solution in 7-10 days, that is total BS. Fix the issue already, it's gone on long enough.

[Poly]

I'm with you. They may have a solution in 7-10 days, that is total BS. Fix the issue already, it's gone on long enough.

I guess we all agree. Just four weeks away from the 10.13.5 release – possibly during the WWDC or shortly after – and there is still no solid fix. :(

Dear DisplayLink devs, hopefully, you'll be at WWDC and address this mess directly to Craig Federighi and Tim Cook. :p

[jizquierdo]

That is complete and utter horse sh$t! Seriously, you may have a solution with a future MacOS update? Really? Maybe one extended monitor? Terrible....

Please, DisplayLink guys, let's finish this torture. I have my three Dell 27" screens claiming for a solution. mirror them or extend one of them means nothing and of course doesn't help

[aehsmu]

Developer beta installed.

Anything for us to try?

[State_from_Jake_Farm]

So..https://i.imgflip.com/29nb4o.jpg

[pattie]

... and buy a new monitor to replace the monitor I bought less than 3 months ago 😡

[Poly]

https://media.giphy.com/media/1z1OvWrH7lYkg/giphy.gif

Smash your external monitors, problem fixed! :D

[State_from_Jake_Farm]

https://media.giphy.com/media/1z1OvWrH7lYkg/giphy.gif

Smash your external monitors, problem fixed! :D

It worked! Thank you

[wadib]

Waiting for new display
Thanks

[John Williams]

Seriously the fanboi is strong on this thread.

According to most people here, Apple has no accountability for its changes, it can do what it wants and then we can rant at other software houses at any breaking changes. Sorry guys that's not how software development works unless your a maverick.

Displaylink compatibility is not a feature, its a core expectation of users including me. We are not comparing DisplayLink to a breaking change in a computer game. The footprint of DisplayLink across enterprise and small shops is massive. What the heck is Apple's testing procedure? Absolutely nothing beyond their own blinkered view of the world.

Yes DisplayLink have had 30 days preview of this and they should have been quicker to the draw explaining there are some serious breaking changes here, but what do we get from Apple, nothing, no response, a nonchalant shrug of the shoulders.

Sadly I have to use Apple for some development work but these guys treat their customers like dirt, problem is people seem to enjoy it.

To the DisplayLink devs keep up the work, I know what its like working on something in a pressure cooker environment, especially when you are supposed to magic a solution from a problem that didn't exist. Apple do not play a team game, history shows that.

[paulgee31]

Totally agree, I've seen too many comments that make the assumption this is some minor issue that DisplayLink have been dragging their heels on.

This is clearly a breaking change, which has a fundamental impact at an architectural level. DisplayLink are not alone in their products no longer working:

In an email to Air Display users, Avatron wrote:

"We’re sorry to say that the Air Display Host software does not yet work on macOS 10.13.4. This new version of macOS has made some bold changes to its WindowServer and Metal frameworks, and unfortunately has broken the Air Display Host, as well as all of our competitors. The breakage is severe; it causes an inelegant system crash when you try to connect to any unaccelerated display or USB monitor. We have reported the bug to Apple and are hoping for a fix in macOS 10.13.5.

Until Apple issues a fix, we do not advise updating to macOS 10.13.4. Of course Air Display continues to work fine on 10.13.3."

Hopefully with enough pressure from the industry and the continued efforts of DisplayLink we will have a permanent solution.


Seriously the fanboi is strong on this thread.

According to most people here, Apple has no accountability for its changes, it can do what it wants and then we can rant at other software houses at any breaking changes. Sorry guys that's not how software development works unless your a maverick.

Displaylink compatibility is not a feature, its a core expectation of users including me. We are not comparing DisplayLink to a breaking change in a computer game. The footprint of DisplayLink across enterprise and small shops is massive. What the heck is Apple's testing procedure? Absolutely nothing beyond their own blinkered view of the world.

Yes DisplayLink have had 30 days preview of this and they should have been quicker to the draw explaining there are some serious breaking changes here, but what do we get from Apple, nothing, no response, a nonchalant shrug of the shoulders.

Sadly I have to use Apple for some development work but these guys treat their customers like dirt, problem is people seem to enjoy it.

To the DisplayLink devs keep up the work, I know what its like working on something in a pressure cooker environment, especially when you are supposed to magic a solution from a problem that didn't exist. Apple do not play a team game, history shows that.

[slvrscoobie]

Totally agree, I've seen too many comments that make the assumption this is some minor issue that DisplayLink have been dragging their heels on.

This is clearly a breaking change, which has a fundamental impact at an architectural level. DisplayLink are not alone in their products no longer working:

In an email to Air Display users, Avatron wrote:

"We’re sorry to say that the Air Display Host software does not yet work on macOS 10.13.4. This new version of macOS has made some bold changes to its WindowServer and Metal frameworks, and unfortunately has broken the Air Display Host, as well as all of our competitors. The breakage is severe; it causes an inelegant system crash when you try to connect to any unaccelerated display or USB monitor. We have reported the bug to Apple and are hoping for a fix in macOS 10.13.5.

Until Apple issues a fix, we do not advise updating to macOS 10.13.4. Of course Air Display continues to work fine on 10.13.3."

Hopefully with enough pressure from the industry and the continued efforts of DisplayLink we will have a permanent solution.

Same over at Duet, they still recommend sticking to 13.3 for now.
"*We recommend staying on macOS 10.13.3*



Installing macOS release Version 10.13.4 will cause Duet Display stop functioning after the OS upgrade. 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.


We would strongly recommend contacting Apple though their bug reporting (https://developer.apple.com/bug-reporting/). It will help have the bug prioritized if Apple is aware how many people are affected by this issue.



We are actively looking into workarounds so that duet is not affected by the macOS bug, and will keep you informed. Please e-mail us if you have any questions. Thank you for using duet."

[AlbanRampon]

Dear DisplayLink macOS users,

We are aware that installing macOS version 10.13.4 will cause DisplayLink connected displays to go blank after the OS upgrade, with the latest DisplayLink driver release 4.1 installed. Extended displays continue to work as expected in macOS 10.13.3, and we recommend that you stay on macOS 10.13.3 or earlier if you require this feature, and have not already upgraded. Functionality such as Ethernet and audio, where implemented, is unaffected.

Our team has made some solid progress towards finding a solution which would restore extended display support for multiple DisplayLink displays, in a future release of macOS, but we are unable to provide a timeframe or a date for release of this solution at this time.

Meanwhile, we have an interim solution which enables one extended USB display (up to 1080p) on macOS 10.13.4, using AirPlay®. Additional DisplayLink screens will be in cloned mode. DisplayLink driver v4.3 beta 3 is available to download from our website today (http://www.displaylink.com/downloads/file?d=167).

Please see the FAQ here on how to enable the DisplayLink AirPlay display for extend or mirror mode (http://support.displaylink.com/knowledgebase/articles/1854724).

Thank you for your continued patience and we appreciate your feedback and support.

[toastido]

Dear DisplayLink macOS users,

We are aware that installing macOS version 10.13.4 will cause DisplayLink connected displays to go blank after the OS upgrade, with the latest DisplayLink driver release 4.1 installed. Extended displays continue to work as expected in macOS 10.13.3, and we recommend that you stay on macOS 10.13.3 or earlier if you require this feature, and have not already upgraded. Functionality such as Ethernet and audio, where implemented, is unaffected.

Our team has made some solid progress towards finding a solution which would restore extended display support for multiple DisplayLink displays, in a future release of macOS, but we are unable to provide a timeframe or a date for release of this solution at this time.

Meanwhile, we have an interim solution which enables one extended USB display (up to 1080p) on macOS 10.13.4, using AirPlay®. Additional DisplayLink screens will be in cloned mode. DisplayLink driver v4.3 beta 3 is available to download from our website today (http://www.displaylink.com/downloads/file?d=167).

Please see the FAQ here on how to enable the DisplayLink AirPlay display for extend or mirror mode (http://support.displaylink.com/knowledgebase/articles/1854724).

Thank you for your continued patience and we appreciate your feedback and support.


Can confirm this works in latest 10.3.5 beta as well. GG guys, great workaround! I can use my 3rd monitor again!

Now to wait for the permanent fix that doesn't have to use airport. :)

[strim]

Good day,

I tried 4.3 beta 3 and confirm it works for me. I don't need anymore to keep my clam-shell open to mirror it to the monitor connected over DisplayLink. My 3rd monitor is 1920x1080, it works over DisplayLink AirPlay as described by the team. Thank you for the next step toward the solution.

[runningdad]

This works for me- any chance can rotate the airdisplay?

[slvrscoobie]

Nice! I was using my apple TV via airplay for a bit but couldn't get over the lag. I hope this is better than a Ethernet connected apple TV airplay option
Great work and that is for keeping to the timeline you promised a week ago

[aehsmu]

Followed the instructions with anticipation.

You should mention that WiFi needs to be enabled or the AirPlay option doesn't appear.

I see a number of AppleTVs listed (on a college campus), but not the DisplayLink option.

So close!

Thanks for moving this forward.
--
Eric H.
--

[strim]

Finally I had to switch back to 4.3 beta 2. Yes, the latest 4.3 beta 3 works as described, however, during a work day I need to connect/disconnect my MacBookPro 2015 from the monitors multiple times (going to the work meetings and back). Each time I disconnect the laptop and want to use built-in display only, my open windows are left invisible and inaccessible on the virtual DisplayLink screen not shown anywhere and not reachable. When connecting back to the monitors, the screen is mapped back to the real monitor wired over DisplayLink adapter.

Shortly saying, the laptop is hardly usable when disconnected from monitors. I have to go to System Preferences and change the settings to disable/enable DisplayLink AirPlay display, etc. Then the same hassle when connecting the monitors back.

4.3 beta 2 is much more predictable for my usage scenario. I change no settings, just plug/unplug cables and keep my clam-shell slightly open. That is much easier that to toggle the bunch of settings additionally to cable work.

[Khashoggi]

Followed the instructions with anticipation.

You should mention that WiFi needs to be enabled or the AirPlay option doesn't appear.

I see a number of AppleTVs listed (on a college campus), but not the DisplayLink option.

So close!

Thanks for moving this forward.
--
Eric H.
--

Same problem. Even uninstalled beta1, then installed beta3 no airplay option and no DisplayLinkUserAgent listed under security-accesibilty-privacy settings for auto start.

[Amarriner]

I downloaded the new driver however I am still getting clone mode only.
:confused:

[Gastronaught]

I followed the instructions to enable the airplay display, got it to work extending to the displayLink airplay display. I then unplugged it and now cannot get airplay to reactivate when it is reconnected. I have tried rebooting, unplugging, replugging, modifying settings etc. all to no avail.

This is the article I followed to enable the DisplayLink Airplay functionality:
https://support.displaylink.com/knowledgebase/articles/1854724

However I only ever see DisplayLinkStop now even when Airplay has not been activated and never just DisplayLink:

https://www.studentservices.hull.ac.uk/files/OnlyDisplayLinkStop.png

I have poked around in settings, carried out many reboots and tried changing when the DisplayLink device is connected nothing works. :(

[LarryG]

Using StarTech USB32DVIPRO.

MBA 2014
Airplay keeps searching for apple tv. Anyone else seen this.

[Wozzy]

I downloaded the new driver however I am still getting clone mode only.
:confused:

Did you follow the guide

https://support.displaylink.com/knowledgebase/articles/1854724


What use to be plug and play is now jump through hoops, not very user friendly. 1080p looks hideous on my 25" screen. Its progress DL but you have a way to go yet to get this fixed.

[paulgee31]

Probably worth noting Airplay isn't supported on iMacs before 2011, so my mid 2010 doesn't give the option to Airplay to the monitor.