MOTUnation.com

Combo:
https://support.apple.com/kb/DL1876?vie ... cale=en_US

Doesn't look like too much has changed according to this:

https://support.apple.com/kb/HT206230

I think I'll wait on this one. Why tempt fate?

Also iTunes 12.4 and iOS 9.3.2. I am concerned that Apple chooses to release updates on a specific date or keynote presentation, rather than when completely baked.

Seems to have a rather extensive Security update list:
https://support.apple.com/en-us/HT206567

cuttime wrote:Also iTunes 12.4 and iOS 9.3.2. I am concerned that Apple chooses to release updates on a specific date or keynote presentation, rather than when completely baked.

Seems to have a rather extensive Security update list:
https://support.apple.com/en-us/HT206567

I've had zero problems with any software update through the entire OS X cycle. Why be concerned?

Frankly, I'm not at all concerned. It's just a bit of work and no apparent benefit for my system, based on their notes.

Gravity Jim wrote:I've had zero problems with any software update through the entire OS X cycle. Why be concerned?

Here are a few reasons for some. This is followed by reports that 10.11.5 did not address the first of these issues.

http://osxdaily.com/2016/03/26/resolvin ... x-10-11-4/

10.11.0 turned a number of Macs into doorstops. You can see a long thread on this in the Apple Community lists. So far update notes have not made a specific mentions of fix for this.

Ahhh... the famous followed by reports—not one with a specific cause for the effect. What crapware is on these systems? What did those "expert" users do via (Onyx or other useless utility)? Were these systems created by cloning without repair partitions?

The fact is that we don't know what the problems were and there's no attempt to report accurately on most of these sites.

I have updated seven out of thirty one Macs so far and will be done by Friday. Didn't have any of those problems after 10.11.4; haven't seen any with 10.11.5.

10.11.0 caught a lot of developers flat-footed. The usb issues are well known and pretty much solved by 10.11.1.

Like anyone else who does audio, I have old tools that no longer work. 10.8.2 was the watershed for me. Nearly everything that worked afterwards still does for me (or the recent updates do).

What is going on behind the scenes to try to keep us safe from security risks is a nightmare. If you don't want to keep up, my only advice is to disconnect from the internet.

My concern is that my clients take security risks when they don't update. That overrides any other. If the ransomware creeps figure out how to hack Time Machine backups in a way that leaves me unable to restore, we're screwed.

Apple appears to be doing their best and, as much as Windows 10 is resembling a clown car, I believe that Microsoft is, too.

OSX Daily reported the problems with 10.11.4 and then followed up with a report that these were not addressed in 10.11.5 when they announced that release. There is no cause and effect relationship here, real or implied. I can't even figure out what the implied causal relationship would be. They didn't fix the errors because people experienced them? The errors were caused by not fixing them in a later release?

Anyway, very nice that you have not had any problems. But as we have seen frequently for a few years now, experience with OS X is not consistent across users, nor is user experience with DP. However Macs are built now, they are not all the same, and don't respond to the OS the same way. In the previous post, I was simply replying to the assertion that there is nothing to worry about, suggesting there is no risk.

As for crapware, I installed it on a newly erased partition, and I could not get through the startup process. Somewhere around 10.11.2, a release note offered a cryptic comment to the effect that it fixed a bug that may precent startup.

To the OP, by all means install. What could possibly go wrong?

FWIW, DP 9.02 and 10.11.5 seem to be playing nicely together for me. My AlphaTrack is still working fine and even LiquidMix with 32 Lives is hanging in there.

I can't even figure out what the implied causal relationship would be. They didn't fix the errors because people experienced them? The errors were caused by not fixing them in a later release?

OK... you understand that was my point, right? The article makes no attempt to do anything except to let you know that the sky is falling for some users.

There is no rigourous analysis that provides evidence of a causal relationship between a bug in 10.11 and the inability to complete the startup sequence despite Apple's release note, and despite, for affected users, the curious cotemporous presence of EC and the problem, and the disappearance of the problem when EC is removed. But that's the slipperey slope of solipsism. Then, there's the saying "if it smells like s%^$, and it looks like ...".

mikehalloran wrote:... as much as Windows 10 is resembling a clown car...

You're killing me, Mike.

Did the update today. Pretty uneventful. All is well.

The update has completely disabled viewing Quicktime (legacy) web sites. HTML5 ONLY now. Infuriating. At least in the last update you could get the QT internet plugin to work again. Now, not a chance.

Also, my Epson scanner in only recognized in the Epson app. Also very infuriating.

Did I mention boot problems? Black screen on first boot. Reboot, all fine again.

I'm really beginning to hate Apple - and computers in general. It seems they were more reliable in 1989 when I got my Atari machines. Sure, not as powerful, but at least they were reliable.

Go ahead, ask me how I really feel?

So far so good (on my non-studio Macs.)
10.8 and DP8.07 on my studio Mac. Extremely solid. Just sayin'.