So what do I do if I have already downloaded 10.13.6 and when I download this combo it won't let me install?

you can't use an "update" to go backwards.You would need to back up all your documents, pictures, music, videos, etc, and then wipe your computer, install 10.13.0, then use the combo updater to go up to 10.13.3. You would then need to re-install all your applications and copy any documents, pictures, music and videos that you backed up before you started

I don't think you can go back versions with Combo only, you have to install 10.13.1 first, then run the combo to update to 10.13.3

I am not a pro but here is what I did:

1. I already had 10.12.6 (Sierra)
2. Downloaded 10.13.1 media (it's a .dmg) and double clicked it, which installed it for me (you already have 10.13.6, which means you might need to create bootable USB media for installation if the above will not work).
3. Once completed, I downloaded the combo and installed it in the same way as above.

Let us know how it'd go.

You're basically fucked, like most of us. You can't downgrade unless you want to do what others suggested you: backup all your stuff somewhere safe, format your Mac and install the base High Sierra, disable automatic update and then update to 10.13.3 using the combo updater.

My issue with this is that I've updated several apps and I'm afraid they won't work anymore if I go back to 10.13.3, which means I would have to uninstall them and install them fresh, losing all the settings and stuff in the process, which is a huge time waste and big no-no for me.

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

LOL.. good one!

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

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


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

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


AMD

Available for: macOS High Sierra 10.13.5

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

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

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

APFS

Available for: macOS High Sierra 10.13.5

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

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

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

ATS

Available for: macOS High Sierra 10.13.5

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

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

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

Bluetooth

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

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

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

CVE-2018-5383: Lior Neumann and Eli Biham

Entry added July 23, 2018

CFNetwork

Available for: macOS High Sierra 10.13.5

Impact: Cookies may unexpectedly persist in Safari

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

CVE-2018-4293: an anonymous researcher

CoreCrypto

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

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

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

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

DesktopServices

Available for: macOS Sierra 10.12.6

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

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

CVE-2018-4178: Arjen Hendrikse

IOGraphics

Available for: macOS High Sierra 10.13.5

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

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

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

Kernel

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

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

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

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

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

libxpc

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

Impact: An application may be able to gain elevated privileges

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

CVE-2018-4280: Brandon Azad

libxpc

Available for: macOS High Sierra 10.13.5

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

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

CVE-2018-4248: Brandon Azad

LinkPresentation

Available for: macOS High Sierra 10.13.5

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

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

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

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

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

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

With what I use my mac for, the updates arent crucial. My main pc is on windows

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

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

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

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

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

Update: July 30th
Dear DisplayLink macOS users,

DisplayLink has worked for many months to maintain support for its users during the transition from macOS High Sierra to Mojave. While functionality such as Ethernet and audio or charging, where implemented, is unaffected on all releases, display connectivity has been limited on macOS releases from 10.13.4 through 10.13.6.

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

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

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

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

Kind regards,
Alban

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

omg, how can I download Mojave Beta 5? Is there a way to get it without enrolling in Apple's dev program?

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

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

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

You may have to change your settings, or make sure you do have indeed the proper Mojave version.
That new OS version been confirmed as fixing the problem by multiple sources already.

Yes I do have

10.14 Beta (18A347e)

This is Beta 5

Turns out some idiot changed the docking station on our flex desk to a WD15 which was my problem when using the original dell docking station Dell D1000 I have no issue it works as stated

Well, it turns out that my mid-2011 27" iMac is not supported in Mojave.

Oh, the joys of programmed obsolescence.

Alban, is there any chance there'll be work on a solution for users with High Sierra > 10.13.4 ? Or are we getting left behind?

Damn, here i am trying, checking, going - "im up to date on the beta, why doesnt this work??' -
Oh - its the DEVELOPER beta. Not Public beta.
https://encrypted-tbn0.gstatic.com/i...p6UjkVKir6sE1L

Public Beta is out!
ok - installed the PB 18A347e - uninstalled, reinstalled, rebooted.
Wait, i unplugged and replugged in the usb device. now the screen is on! i can see a mouse. but its black like it was back on 13.4.
If I screen shot the other monitor, it shows the backround image, and menu bar, but on the display its just black.

Edit - Just Uninstalled - REBOOT - Reinstall beta 5, REboot - TA M-Fin DA!! 2 SCREENS NO AIRPLAY!!

I can confirm that it is now working. Tested on a 2017 and 2012 Macbook Pro.
Thanks Displaylink for your perseverance.

I can confirm too, it is working now. MacBook Air (13-inch, Early 2015)
Finally DisplayLink folks did it, many thanks!

2018 mbp
 

Has anyone gotten the ASUS MB169+ to work with a 2018 MacBook Pro w/ Touch Bar (The latest model). I installed the beta 5 and followed all instruction but when I plug the monitors cable into my USB-C hub, the display either blinks orange or will alternate blinking orange and white.

I can also report it working with Mojave Public Beta 4 and DisplayLink Beta 5 drivers on my 2013 13" MacBook Air.


I've seen that flashing behavior when connected to the USB-C ports. I believe it depends on the cable and/or USB-C to USB adapter you are using. apparently some cables/adapters don't supply enough power to keep the monitor powered up.

I'm about to upgrade my MacBook Air to a 2018 MacBook Pro, so I expect I will be fighting that battle soon also.

LOL!!

Too late. I just today replaced my display link dock (Dell D3100) with USB-C to DisplayPort cables and the USB hub built into the Dell monitors.

Too bad it took so many months to fix.

[EDIT] Actually, reading back through, it's only fixed on 10.14 Beta and since I have work to do I can't install beta's on this machine anyway, so glad I ditched the DL dock. If I'm honest, two USB cables is tidier than a USB-C to USB-A adapter, a dock, a power supply etc. At least this way all of my cabling is hidden away behind the monitors and very tidy.

I feel like one thing missing from this discussion of it now working with the Mac OS X 10.14 beta:

--- Its the DisplayLink Beta 5 (released 1 1/2 months ago) that is now working in 10.14 ---

That means that DisplayLink has had their side done for a while, and it required Apple to do their side to make it all work again.

It also means that Apple could backport those fixes to 10.13 and make it work as well, but they probably have no interest in it.

I totally get all of the complaining that the hardware stopped working, and the complaints about the fix being slow, but I appreciate whatever must have had to happen behind the scenes to get Apple to do their part.

Cheers,
Greg

This fix (https://support.displaylink.com/know...ys-on-mac-os-x) is still not working for me. I'm running 10.13.6 and Airplay does not automatically pop up when my monitor is plugged into my computer.

Yes, I have done Step 3 (enable Airplay to pop up in menubar) and my monitor is clearly on (but black).

Help?

Displaylink said this from Day one:

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

That meant Displaylink KNEW they would not be able to do it with the current version, and had to wait for Apple to make a change on their side.

But a lot of people were too angry to understand that.

Apple Operating systems are very limited in what they let outside developers do. Once they close a door, Developers cannot always find "another way in" to perform the same task. Many applications and hardware devices have "died" because Apple (and Microsoft too) have moved on from a technology or closed a door to the OS. Displaylink could have been one more corpse on the pile. I think we should consider ourselves lucky.

I'm honestly surprised they cared enough to go through the trouble of opening another door for a third party vendor. They must have received a good amount of complaints and pushback from the users and maybe even seen users moving away from MACs because of the issue. While there are other limited options for additional monitors on desktops, there are almost no alternatives for portable monitors for those of us who travel that do not use display link.

I will be surprised if they port the changes back to 10.13. They really have no incentive to do that. Wy waste development resources on an OS you are trying to phase out? The Mojave release is right around the corner, and they WANT you to upgrade to Mojave as soon as it comes out. and if you own a computer that is too old for Mojave, they WANT you to upgrade. WIN-WIN for them.

A HUGE amount of assumptions going on in this thread!!

Only Display Link and Apple know what has really gone on and continues to go on. The public will probably never know what has really gone on (and why should we? it's not really much of our business), even if one of the involved parties says, we'll still only ever know what they want us to know which may or may not be what has actually happened behind the scenes.

Marketing!

Same problem here. Just purchased the unit yesterday for my 2018 MacBook Pro, and it does not work with my 3 4K displays, only the primary display. Are there workarounds until this issue can be addressed properly?

Found a steal of a deal on a thunderbolt display with Displayport pass through, picking it up tomorrow (I hope) and then Ill rid myself from the need to use displaylink at all. they fixed it right as I started hunting for other options. and if it wasnt as cheap as it is, Id probably just keep the 2 screen setup I have but work is telling me a new laptop is in my future so this will be easier than working on the USB-C to A to Displaylink To.... that I have now

Apple has been way too quiet on this issue, I don't think they wanted it to get any attention. I wonder if it helped the eGPUs they were promoting?

Issues installing the Display link Beta drivers?
 

Anyone had an issue after Installing the Beta drivers on Mojave Public Beta where the machine locks up on the Apple logo and bar on reboot?

welllllllllllllllllll cruddddd

got my Thunderbolt display today. plugged it in, works great, except.. wait, where is the 2nd monitor.

oh. apparently you cant connect a thunderbolt display AND daisychain it to another Displayport display, it has to be ANOTHER thunderbolt display.
GD Apple, you really dont make this easy (or its easy but extremely costly :(
so Im back to my displaylink monitor.

Can anyone confirm the newer QHD or 4K displaylink adapters are working before I buy a newer 2560x1440 monitor and find out it wont work...

Well, everything was working great on my 2013 MacBook Air running Mojave Public Beta 5 and the latest Beta Drivers for a couple of days.

Today I got a my new 2018 MacBook Pro.

I installed the latest Mojave Beta Public Beta 6 (18A353d) and the same (latest) DisplayLink Beta drivers and My 2nd monitor is blank with only the cursor showing up.

If anyone else is running the same setup, please let me know your results.

Sucks because some of my other apps (including Skype for Business and Symantec VIP) are either buggy, or not working under Mojave yet, but I installed the Beta strictly because of the second monitor.

I had the same issue once the new PB was released. I uninstalled, rebooted, installed, rebooted, and its worked fine ever since.

Thanks, I'll try that when I get a chance and see what happens.

Unfortunately, I'ver rebooted, Uninstalled, Rebooter, tried again, rebooted some more, and gone round and round till the cows come home, and I still get a blank display with just a mouse cursor.

I'm using a 2018 MacBook Pro 15" with the i9 processor. I'm running 10.14 Beta (18A353d) and the latest DisplayLink 4.3 Beta 5 driver.

If I select "Mirror Displays" and then set "Optimize Display" to "MacBook Retina display", then It works (mirroring my display), but if I turn off the checkmark for "mirror displays", I get the blank screen again.

I've hit a brick wall for now. It's most annoying because it *should* be working.

Any suggestions are welcome.

My work PC was recently changed over from a Windows 10 machine to a 2017 MacBook Pro. Working at home I use a Plugable UD-3900 dock, which I have been able to get one dispaly wokring with the beta 5 driver form July. This works well, but I really like 2 full size displays.

As a workaround, my IT group gave me a thunderbolt 3 adapter that has 1 hdmi port, and 3 usb 3.0 ports. This has enabled me to use my 2 full size dipslays. I plug one into the adapter via its HDMI port, and then I plug my DisplayLink based dock into one of the usb 3.0 ports. The dock has a display plugged in via DVI. Both displays work, and I keep the MacBook Pro closed, running in clam shell mode.

My IT group will not allow an upgrade to Mojave when it is first released, so any fixes included in that will have to wait for me. This workaround meets my needs.