Apple today released OS X El Capitan 10.11.6 which improves the stability, compatibility, and security of your Mac, and is recommended for all users.
This update:
• Resolves an issue that may prevent settings from being saved in accounts with parental controls enabled.
• Resolves an issue that prevented some network devices, such as speakers and multifunction printers, from accessing SMB share points.
Enterprise content:
• Improves startup time when connecting to a NetBoot server.
• Resolves an issue that may prevent startup from a NetBoot image created with an OS X v10.11.4 or OS X v10.11.5 installer.
• Resolves an issue that may cause Active Directory authentication to take longer than expected.
OS X El Capitan 10.11.6 is available via Software Update.
Bricked my iMac. No apps will open. Reinstalling OS X. 🙁
Without a hitch.
Ten minutes to update. Everything working as it should so far.
All is well after reinstalling OS X. Must have been a glitch in the small update.
Tried to do the update again and black screen for over an hour. Back to 10.11.5 for now. Bummer.
To hell with El Crapitan, I can wait for reviews of Sierra.
And, u think it’ll be better? Remember we”re speaking of Apple software
AND also out today, specifically for iOS 10.11.6 is:
OS X Server v5.1.7
Fixed an issue affecting Server installations configured with a third-party SSL certificate that prevented MDM enrollment using DEP
And yes, they’re still calling it ‘OS X’ Server, not ‘macOS’ Server.
And of course I meant: “specifically for OS X 10.11.6″.
These updates consistently remind me what a piece of crap the Mac App Store app continues to be. Good gawd it’s awful. 😛
Oh great. OS X 10.11.6 is working fine… Except Apple ignored my bug report regarding the Startup Disk Preference Pane. It’s a bug Apple introduced in OS X 10.9 and hasn’t bothered to fix until OS X 10.12 Sierra (beta) where Startup Disk actually works properly again. I actually IMPLORED Apple to finally fix this bug in 10.11.6. Begged them to fix it.
That will be 1, 2, 3 versions of OS X where Apple KNEW about the bug and didn’t bother to fix it. Wow, that really inspires me to bother with their AppleSeed testing program, not.
Bad show again Apple. Bad show. 😛 Asinine, in fact. Ticks me off to the nth degree. Etc. [expletives deleted]
What is the bug?
Since I usually have three OS volume versions setup on my Mac for testing but I don’t recall an issue. Of course I may not have triggered it.
This is a bug I’ve seen on all my Macs on all their partitions since 10.9.0. The problem is, in brief:
– In System Preferences: Security & Privacy: Advanced: Check ON “Require an administrator password to access system-wide preferences”
– Go to System Preferences: Startup Disk.
– UNlock the pane.
– Provide an admin ID and password.
– Change to another startup disk.
– At this point you should be able to:
– – Restart, or
– – Lock the Startup Disk preference pane, or
– – Close the Startup Disk preference pane.
Any of the above should NOT result in asking for the admin ID and password again. . . . And yet it irrationally does, over and over again. None of these further permission requests are required. Not a single one. And yet the bug pesters you over and over. If you attempt to ‘Cancel’ then it throws you a message that you don’t have permission to change startup disks. And yet you already have been provided that permission via the original admin ID and password. You can in fact cancel out of this nonsense, over and over and you’ll find that the startup disk HAS been changed, as it should be.
∑ = Entirely unnecessary nagging and provoking of the user with utter nonsense. And this has been going on for 3 versions of OS X. Apple has ignored bug reports about the problem all this time. Thankfully, they DID fix it in Sierra, about bloody time. But they clearly REFUSE to fix it in 10.11. Idiotic.
Tell me about it.
Apple introduced a bug in 10.9.3 that broke FInder connections to any SMB server that uses Windows deduplication, which meant that any time you tried to open, say a word doc you would likely get an unusable 0-length file.
They didn’t fix it until 10.10 was released. Guess who had just set up our new file server infrastructure with a de-duped Windows server 🙁
OMFG, Apple has had a TERRIBLE reputation supporting SMB, over and over with VARIOUS bugs. It got to the point of being a sick joke among OS X Server users who have been attempting to use Macs mixed with PCs in various enterprise organizations. Nightmare. I personally have not been involved in such a network. But as someone on the Mac Enterprise email list, this has probably been the #1 PEST problem of OS X. Apple attempted to fix things, but kept on bumbling, over and over.
Will update no time soon.
Learned my lesson long ago. It’s a mistake to be an early adopter with these releases.
Not always Apple’s fault, though, with all the third-party software and hardware.
Will wait until the changes have rippled through the system.