Today I updated to OS X 10.10.4. I was really happy when I read through the change notes despite the fact that I actually shouldn’t have been as there were also a dozen or so fixes for possible unauthenticated remote code executions in several components of the system.

But I was happy because it was promised that they had fixed an issue which could lead to the system to stop responding under certain conditions. One of them was your computer being connected to a directory service. Check – my computer is member of an Active Directory domain. So I know some of those certain conditions.  Like trying to connect my Mac to the Internet via my Windows Phone’s WiFi Internet sharing. Or trying to login to my non-directory account first after boot without having logged in as directory user. Or sometimes when waking up from sleep. And some other conditions I could not find a pattern for. This can really be a pain especially when being somebody who is doing on-call duty and needs to be able to rely on the computer to actually work when servers are burning.

I cannot tell if the update works. I hope it does but my hope is limited though. And this is why I’m writing these lines. Because I just witnessed another thing that adds into why my fate in OS X is declining:

UpdateFail

Maybe I should start looking at Linux again…

4 thoughts on “UPDATING_LOCKED_DEFAULT_BUTTON

  1. Don’t get me wrong. UX wise OS X is still years ahead of what I see in my regular Linux assessments (unfortunately).

  2. I am getting this message when trying to open iTunes. Apple Support are clueless. I suspect that the only way to make it go away and open iTunes will be to visit the app store and update iTunes to 12.2.2, but I really don’t want to do this yet as that – in combination with iOS 8.4 and iCloud library – was what completely screwed my library at the weekend. Apple Support’s answer to everything is ‘back up, restore’, which is incredibly time consuming. What happened to just properly testing software updates before release?

    • In my case it was OneCloud that had this issue. It started working again after a reboot. But as soon as AppStore tried to update again it got into the same state again. I recovered the App from that state by removing it entirely and re-installing it from the AppStore.

      BTW: The latest Update for iTunes fixed a possible remote code execution vulnerability which you don’t want to miss. So be sure to update soon.

Leave a Reply

Your email address will not be published. Required fields are marked *