At one point, though, about a third of the way through the progress bar on the black install screen with the white Apple logo, it got stuck. The Big Sur update started fine, and it went through several reboots, as expected. The only thing "unusual" about my Mojave volume is that it had FileVault enabled. In fact, I uninstalled Little Snitch before updating, because I was still using an older version of Little Snitch with a legacy kernel extension, which isn't supported on Big Sur. I don't think I had any third-party kernel extensions installed. What happened this time? I started with the latest version of macOS Mojave on my 2014 MacBook Pro, and I had plenty of free disk space for the update, more than 100 GB. Over the years I've seen many Mac bugs, and even some kernel panics, but I've never had a Mac OS update just fail to finish. Ultimately, though, I couldn't wait any longer, because I need to run the latest Xcode beta in order to develop Safari extensions for iOS, and the latest Xcode beta requires Big Sur, so I finally decided to update to Big Sur on Saturday. I did skip macOS 10.15 Catalina, however, which I've heard was very buggy, and I had been holding off as long as possible on macOS 11 Big Sur, which I've seen is very ugly. My current machine is a 2014 MacBook Pro, which I had updated from Mavericks through Mojave. It came installed with Mac OS X 10.1 Puma, and I've been installing minor and major Mac OS X and macOS updates ever since, with the one exception of Mac OS X 10.7 Lion, which in my opinion was the worst Mac OS version ever (before now). I bought my first Mac, an iMac G4, in 2002. Support this blog: StopTheMadness, Link Unshortener, Tweaks for Twitter, PayPal.Me Articles index Mac OS update failed for the first time in 19 years Augby Jeff Johnson
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |