macos 10.14 mojave hardware requirements

In most cases, though, the update should have succeeded and no further update will be available. Robert advises restarting that Mac, and if necessary installing the update again, within 30 minutes, if that’s offered. Once they had done that, the restart should have completed correctly, and that Mac resumed working normally. Instead of the updated macOS booting silently straight into the Finder, the Mac ended up in Recovery where the user had to authenticate to unlock FileVault. macOS 13.2.1 updateĪs Robert Hammen has proposed, what most probably happened at the end of the 13.2.1 (or 13.2 for some) update was that authenticated restart didn’t work properly. This relies partly on what’s known as an authenticated restart, sparing you from having to enter your password to unlock FileVault. Now everything is orderly, quiet, and on Apple silicon Macs in particular very quick. There was a time when I used to count the number of startup chimes sounded during each update. Like so much else, macOS updates aren’t what they used to be. This article explains what happened, and other accidents that can happen when updates don’t work right. Instead of the updated macOS automatically returning them to the Finder and Desktop once the update was complete, it bounced the Mac into Recovery (or similar, if your Mac is managed) and asked for the password. A small minority of users experienced something strange when they updated to macOS 13.2.1, or even 13.2.

Macos 10.14 mojave hardware requirements