3

I have a new MacBook Air. I just bought it and first started it. I try to update it to the latest version, but I get Installation failed. I try to install macOS 10.14.5.

Where are the updates stored after they are downloaded? Maybe it works if I delete it and download the update again?

I am totally new to macOS any help is appreciated.

  • What is current version ? – ankii May 27 '19 at 15:41
  • macOS Mojave 10.14.2 – Black May 27 '19 at 15:59
  • Did you try installing from App Store? – ankii May 27 '19 at 16:00
  • 2
    You can get the downloadable Combo Updater to 10.14.5 at this link. Make sure you do a full backup before you run any updates. – IconDaemon May 27 '19 at 16:48
  • Although I recommend waiting for a few days and getting yourself familiar to the file structure and usage of Mac as well as appleID . It can get tough to come out a problem in case you run into trouble while updating. @Black – ankii May 27 '19 at 17:16
3

I had to disable System Integrity Protection (SIP). Just follow this answer:

https://apple.stackexchange.com/a/361046/333653

Then I had to open a terminal and delete all folders in /Library/Updates with sudo rm -Rf e.g. sudo rm -Rf 041-57076. These are the update files, I need to delete them because they are corrupted because of poor internet connection.

Now I triggered the update again, it began to download the update again and now it works :)

If it does still fail, then try this procedure again, but connect via cable not via Wifi.

| improve this answer | |
  • 1
    +1 for documenting where internally these are stored. I normally just boot to internet recovery to get a fresh copy of everything. – bmike May 28 '19 at 9:24
  • 4
    You do not need to disable System Integrity Protection (SIP). Simply boot to the Recovery HD and delete it from Terminal there and no need to use sudo as it's already a root shell. Then reboot the Mac. BTW You do need to delete it from e.g., /Volumes/Macintosh\ HD/Library/Updates when done from the Recovery HD. – user3439894 May 28 '19 at 9:49
0

In my case the reason was a missing /private/tmp directory. I recreated it like this:

sudo mkdir /private/tmp
sudo chmod 1777 /private/tmp

Afterwards the installation went through successfully.

| improve this answer | |

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .