macOS 10.13.4 Breaks Third-Party Dual-Display Systems


(Adam Engst) #1

Originally published at: https://tidbits.com/2018/04/08/macos-10-13-4-breaks-third-party-dual-display-systems/

If you rely on a third-party solution like AirDisplay, DisplayLink, Duet, or iDisplay for extending your display to a second screen, hold off on upgrading to macOS 10.13.4 High Sierra, since it currently breaks those products.


(Charles) #2

I am using Astropad Standard and it works fine on the latest macOS version. It’s not quite the same functionally as the other dual display systems but should suffice for many users.


(Chris R) #3

I wonder if the problem isn’t more pervasive. I run two ATD (27") units that were daisy chained to my MacPro. As soon as I upgraded/rebooted the second display on the chain was gone (no power and not in Sys Info.) I cabled it several other ways and was ready to conclude it was a hardware issue when a few days later I happened to connect form home over ARD and there it was and still there when I returned to the office. I will reboot at the end of the day and report back!


(Adam Engst) #4

How were they connected to the Mac Pro?


(Chris R) #5

Originally a “Daisy Chain” - MacPro (late 2013) to ATD to ATD. Now I have both displays connected direct. I just rebooted for the first time and all is well but for 3 or 4 days after the upgrade … nothing!

This is reminiscent of the 10.13.2(?) upgrade when both home and office MacPro’s (with different dual display setups) started crashing during screen sleep. The fix was to always Log Out then .3 fixed it.

Gremlins and Demons!


(Jeff Hecht) #6

I was very surprised this evening to find my new Macbook Air in process of rebooting to a just updated 10.13.4 when I picked it up this evening. It hasn’t caused any trouble YET, and I don’t have a second screen running with it, but I had made a point of avoiding updating. Apparently the default App store preferences had been set at the factory was to Install system data files and security updates, and it decided to do so several days after I had bought it. So if you want to avoid updating, be sure you check the App Store settings.


(Simon) #7

I have my prefs set up to allow only “install system data files and security updates” but not “macOS updates”. And in my case 10.13.4 was not auto-installed as I’d expect. Are you sure you didn’t have “Install macOS updates” checked?

In principle I don’t want anything installed without my knowledge or my explicit consent. So I would like to have turned off all those options. However, I recall there was some lower-level updates that would only take place if you’d check the “system data files and security updates” box with no other simple way to have those updates otherwise take place. I think there was actually a TidBITS article with the details not so long ago. My compromise was to turn on only that option.


(David Byrum) #8

Perhaps I’m being dim, a good possibility, but I don’t understand how this problem is a “surprise” when the 10.13.4 update went through, I believe, 4 different betas that were available for testing by the general public of macOS users before it’s release as a GM.

If no one saw this as a problem before its release, this would imply that Apple made the changes that caused this problem between the final beta and release of 10.13.4. Why would this happen as it would seem to defeat the purpose of having a wide range of folks try out the betas.

Hopefully some informed reader of this site can help me understand what’s going on here!

Thanks!


(Simon) #9

This has happened many times in the past. In fact, looking at the last few years, I’d say the more Apple has invested in beta programs and public betas and multiple testing releases, the more they have released buggy software. Either Apple cannot process feedback or public betas are a complete and total hoax.


(GraphicMac) #10

I think you’re at least half correct with that statement. Public betas are little more than publicity for the company and a gift for the ever-impatient and easily distracted end-user.

I would be willing to bet a cream-filled donut that 99% of public beta users never test anything, or provide any feedback in the correct manner—but they sure do complain a lot in web forums like MacRumors, etc.


(Adam Engst) #11

Why yes, there was! And you really don’t want to turn off that checkbox.


(Simon) #12

Thanks for the link, Adam. I just enjoyed going through that article once more. Very valuable information. :+1: