Perhaps, not the right answer. But, I was facing the same issue, just downgraded to Sierra and got all the three monitors working. I would suggest the same, till DisplayLink and Apple figure it out, not using the monitors are never the solution.

Are you serious? If I get you right, this sounds like a bad joke to me: "Don't update if you want to keep your system usable" - Seems to be pretty bad choice for a dev who might be interested in testing his software against the current OS version - Not to speak of those who just want to keep systems up to date for security's sake.

This is a major problem and that hacky solution with Airplays ist just a bad joke - the product was sold as a Triple Display Docking Station to my company and was considered to be the best one-cable-solution since it had full Mac OS X compatibility - however, the product just got broken - it's insane to advice somebody to not update his OS just because of some faulty drivers - you had one job - and failed.

I'd consider filing a lawsuit as well - product stopped working, no solution -> useless product to me.

You are 100% correct, this is an absolute joke!

FIX THE ISSUE ALREADY! You've had months now, maybe you should find some new developers if the ones you currently have are incapable.

I see, thanks for the replies.

Can you provide a "safe" way to roll back to High Sierra 10.13.3?
I don't have a Time Machine backup and, honestly, I don't want to re-install everything from scratch.

I've read something about downloading the 10.3.3 combo update and installing that, can anyone elaborate on this?

Ridiculous waste of money
 

+1 to everyone that has previously posted to this forum about the High Sierra issue. Downgrading to Sierra is not an option for me as my company will not allow us to use anything other than High Sierra due to security reasons. So the $200 I spent on my Targus dock has resulted in pretty much zero value to me. And Targus refuses to give me a refund since it was purchased via a dealer and not direct.

So...I have a very nice, completely useless $200 brick sitting on my desk. And to make things worse, I had to spend another $100 on dongles in order to use my displays. Which was exactly why I purchased the dock in the first place.

Get this issue fixed ASAP please....this is completely ridiculous.

Combo updates don't work I have tried. The only downloadable install I could find was Sierra, so I reverted to that. I am still exploring on how to install 10.13.3 over it; will drop in a message if I figure it out. The issue is that when-ever you try to upgrade to High Sierra, it downloads and install 10.13.5, which clearly defeats the purpose.

Now that, Mojave Beta 2 is released perhaps it's fixed or maybe not; I am hoping someone who has Mojave Beta can drop a line.

Hmm. I am still look at possible solutions to just upgrade back to 10.13.3 and we can perhaps keep it that for the time being at-the-least.


+1 for that. What surprises me is why Display Link and the developers don't have an exact time line or perhaps something that says 'Okay. The fix is in Mojave'. But, all we are hearing is vague stuff.

Display Link developers, please update us!

Update: June 20th
Dear DisplayLink macOS users,

Installing macOS 10.13.4, or newer, will cause DisplayLink connected displays to go blank after the OS update when using DisplayLink driver v4.1. Extended displays continue to work as expected in macOS 10.13.3 and below.
Functionality such as Ethernet and audio, where implemented, is unaffected.

DisplayLink driver v4.3 beta 5 currently provides an interim solution with one extended USB display (720p or 1080p) on macOS 10.13.4, 10.13.5 and the first two 10.14 developer previews, using Apple AirPlay® on machines with that feature. All additional DisplayLink screens will be cloning the primary display.
An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode.

Our team have made further progress towards finding a solution which would restore full extended display support for multiple DisplayLink displays in a future release of macOS. As daily users of the technology ourselves, we truly understand how disruptive this loss of functionality affecting the ecosystem can be.
We have had positive developments on being able to communicate a roll out plan for this long term fix, but for the time being remain unable to provide a time-frame or a date for release of this solution.
Resolving this issue remains the highest priority for us and we will continue to provide regular updates as we move towards this.

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

Kind regards,
Alban

Eeeeasy folks, threatening people isn't going to get the issue solved any faster.

The DisplayLink team, as well as every developer on the planet, cannot control how Apple changes their operating system. If the DL team built their software and drivers using some components of the OS that Apple removed or changed, it may be difficult or impossible to update the DL software and drivers as-is. The next version of the OS is still in beta, which means that there are a great deal of things that are still changing, and any updates the team makes now are an attempt to hit a moving target. They may get the BETA drivers working on a BETA OS, but the next version of the beta may break things again, so giving a hard release date might be impossible with the software in its current state, and the DL team may need to wait until certain parts of the OS are more stable before they can start building new drivers.

Quite often, Apple makes changes that affect developers and software functionality. A point release may suddenly affect a piece of software you use without warning, because Apple made a change the developer did not anticipate. The DL team may need to rewrite the drivers completely from the ground up, or they may be in a holding pattern until things stabilize.

Either way, yelling louder will not fix this problem faster. I think it sucks, too, and I'm upset that I have a product that doesn't do all the things I want it to, but the DL team has a great track record of making progress, even when facing really difficult challenges. Give them a little bit, I'm sure they'll be able to get this one fixed, too.

Support for High Sierra 10.13.x
 

You say "in a future release of macOS". I am very concerned that the full fix might only work with macOS Mojave. I'd like to point out that – as usual – not all 3rd party applications will be fully macOS Mojave compatible at its release. It is healthy to postpone a major OS update and check application compatibility for a private user, but it is always the case in enterprise environments. Mojave is a very special case! It will phase-out 32 bit support. A lot of users/businesses won't be updating immediately to Mojave because many (business critical) applications are still not 64 bit ready.

It would be highly inconvenient if the fix worked only with macOS Mojave! Please provide a full fix – not a workaround – for the latest HighSierra as well.

DL wre informed of this change well in advance by Apple, possibly upto 12 months but still failed to fix. So I think they have had long enough. This isn't just the odd user complaint here larger corps like IBM use Mac's and DisplayLink, think how much it is can be effecting productivity, think how much money has been spent on DL devices that are currently next to useless.

Again we see the post about 4.3 beta 5, so ok progress but its BETA. Places like IBM can't allow beta software to be used on mass, it need to be final before allowing staff to install.

*affecting

So the update on progress is the same update on progress from months ago.

1. Positive progress made. Statement no facts supporting it.
2. Can not tell you about the progress made. Obviously not enough to get to even a beta stage.
3. A future update of the OS is involved. An open ended statement which provides no target leaving possibilities endless on date.

All things point to nothing being available in any point in the near to medium term future.

You forgot appreciating our patience, lol.

Seriously, this is ridiculous.

Thanks once again for keeping us updated.

Please let us know as soon as possible when you have reached a point where full functionality has been restored, even if it's in Mojave's beta. I can obtain the OS update and willing to risk running it if it means I'll finally have my DisplayPort dongle fully working again.

Right now I have to plug and unplug monitors whenever I need to do photo post-processing as I have a professional monitor dedicated only to this.

All the best.

"restore full extended display support for multiple DisplayLink displays in a future release of macOS"

Hanging out for this!

As much as people are bagging out DisplayLink I think Apple are just as much to blame, they release laptops with bugger all ports. I had to buy my dock because their USB-C to HDMI dongles always got stuck in a loop trying to connect my monitors.

Apple could have worked with DisplayLink on a solution rather than treating their users like garbage (again!), I don't think this would have happened a decade ago. Their operating system has fallen so far behind Windows that a desktop theme opens their keynote, dark days for Apple.

My 10 year old Windows laptop runs multiple monitors far better than my brand new MacBook Pro ever has.

I agree. If Apple didn't disable Displayport 1.2 MST (a decade old technology), I wouldn't even need a DisplayLink dock. If I boot to Windows on the same Mac I can simply daisy chain my two external monitors via a single cable, and it's just Displayport via USB-C, not Thunderbolt 3. Hardware supports it natively.

We have 2018 but Apple tech is now as inconvenient as back in the early 90s. Less and less compatibility with open standards. Apple's OpenGL drivers haven't been updated in years. They're dropping OpenGL and OpenCL as well. :mad: No Vulcan support, no CUDA on internal GPUs (because it's AMD). Devs don't care much about Metal2 and it's been buggy as hell. The iMac Pro is basically unserviceable. And a 480p front camera in a 2017 MacBook model, really? It's innovation backwards and getting worse...

Just sharing that the problem is not resolved in Mojave 10.14 beta 1.

Is that the new public beta? I've read today that they released the beta in public, maybe it's a new build?

Sounds to me like you need to stick with windows and all their forward thinking...

Yes, its the public beta, which in turn is the second developer beta.

Does the 'beta' still work? I dont imagine Apple GARA about 'fixing it'- its entirely on DL to find a work around or redevelop the framework. was thinking of trying it out, but dont want to lose the 'working' beta 5 I have now.

I also am running beta 2 of Mojave and the working beta from display link still functions.

That being said I have had stability issues with the Apples Airplay agent from time to time it seems to crash and the only way I have found to get it restarted is by rebooting my laptop

thanks, might give it a go this weekend then on my 13". Still trying to see if the continuity activation hack from 10.11 will work on it too with my 17" mbp - havent gotten confirmation thats ok yet either.

next release is not until september... in for a long wait

JULY


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

When will we see a final release?

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

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

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

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

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

All we need is patience!

P.S. I do not work for DisplayLink

Yes, how hard can it be?

Such a long time with no results shown. If I'd put away $25 per week since that post I'd be able to buy a really nice eGPU solution by now.

On Mojave Beta 3 driver is not working anymore. No Airplay. I see monitor in System Preferencies - Display. Monitor becomes active when Itake mouse cursor over there, but it is always black screen. (on this black screen I can see mouse cursor)

Thanks Neo,

I had logged in to see if anyone had tried the third Beta of macOS 10.14

Sad to see no progress.

This issue needs to be made more public so Apple is forced to respond.

MC Ren you obviously didn't try apples dodgy USB-C to HDMI dongles before buying your displaylink product, they were absolute garbage that caused an endless loop of discovering the first monitor, refreshing, discovering the second monitor and losing the first monitor, refreshing, then discovering the first monitor and losing the second monitor ... and so on.

As I've already said above: it's all about external graphic adapters. In 10.13.4 Apple began to provide native support for external GPUs. They have rewritten large parts of IOGraphicsFamily.kext, what brings us to the point, that all virtual graphic adapters are now unusable.
DisplayLink has reached some progress using AirPlay Technology, but since Mojave beta 3 it's broken.

You are testing beta software on a developer release and you expect it to work :D

DL need to get a final driver out for HS first. Enterprises that use DL are not going to want to distribute beta software.

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

Update: July 4th

Dear DisplayLink macOS users,

Installing macOS 10.13.4, or newer, will cause DisplayLink connected displays to go blank after the OS update when using DisplayLink driver v4.1. Extended displays continue to work as expected in macOS 10.13.3 and below.
Functionality such as Ethernet and audio, where implemented, is unaffected.

DisplayLink driver v4.3 beta 5 currently provides an interim solution with one extended USB display (720p or 1080p) on macOS 10.13.4, 10.13.5 and 10.14 first two developer previews, using Apple AirPlay® on machines with that feature. All additional DisplayLink screens will be cloning the primary display.
An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode.
The third developer preview of 10.14 has changed behaviour, as already exposed here. Displays using DisplayLink technology will be present in System Preferences - Display. The displays can be activated, and the mouse is visible, but otherwise the displays are black. Should you have already installed that OS version, simply use DisplayLink driver v4.3 beta 6 to force the AirPlay interim whilst the work continues.
We do not recommend using that OS version for extended desktop changes as it brings no benefit compared to previous versions. It also adds an undesired audio switch at reboot to be addressed.
When a new version brings value, we will obviously notify you.

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

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

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

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

https://i.imgur.com/YYm65Nx.jpg

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

Wait, so if I put that kernel extension from a 10.13.3 installation over to my actual 10.13.5 displaylink will work again as intended?

I remember I did the same with an audio extension to get Integer Playback again, maybe it could be a nice workaround without re-installing everything from scratch?

Please let me know if anyone has tried this.

Yeah this might be worth exploring, on a hackintosh. Anyone got time for it?