macOS 10.13.2 failed to install and now won't show in App Store at all

I don't think so. From the sounds of it, software raid and macOS are basically done.

I just converted to an AppleRAID and I still cannot run the update. Apparently you cannot run Mac OS updaters on RAID volumes any more. Now I really wish I had purchased a single 1 TB drives instead of a pair of 500s. What the **** Apple? Please don't turn your computers into appliances. It works for phones and tablets but literally nobody wants that for their computers.

Glad some people are getting there... but no Softraid here.

Company computer, so the “weird stuff” is: AirWatch, Endpoint Protector and BitDefender (which has been very angry since converting to APFS).

A bit off topic but APFS is so poorly supported, I cannot believe they made it automatic already. If you boot a Mac into Sierra, it CAN NOT SEE an APFS volume! DiskWarrior and disk programs cannot work with APFS. It's is NUTS that they went live with it. In the past, with features like this, what they would do is start supporting it with this version and the next version, and only many versions down the road, switch to it as the default. By then, all current older OS versions would still be able to read the disks fine, and all disk related programs would have been updated to work with it just fine, and it would be an invisible non-issue.

APFS has been a huge issues for me. And downgrading back to HFS+ is (while worth it) a HUGE hassle! What is going on in Cupertino these days?

l008com wrote:

A bit off topic but APFS is so poorly supported, I cannot believe they made it automatic already. If you boot a Mac into Sierra, it CAN NOT SEE an APFS volume!

That's not the case. Sierra can see and work with APFS volumes. Sierra had some APFS support. I just copied a large RAW image from an external APFS drive to my iMac with Sierra 10.12.6.

As far as DiskWarrior, it's up to them to update for APFS support. Some file handling software has already had upgrades, some have not. That's how it's always been.

I had this problem too since the day it got released, until now. What made it work for me was to disable F-Secure XFence (not just learning mode) and also in System Preferences -> Security & Privacy -> Firewall disable Stealth Mode and enable both of the "Automically allow..." options. I know some of these are obvious, and some of them were already tried before, but this time I went all-in unprotected so that none of these would possibly interfere with the update.

I have the same problem. I tried updating my MacBook Pro with touch bar multiple times and still get the pop up saying updates could not be installed. About this mac says I'm running OS 10.13.1 however, when I go to the App Store and click on update, it says I will be updating from 10.13.2 to 10.13.2....huh??? Seems like the update was successful, but the laptop does not recognize it, so it keeps giving me the update pop up. Guess it's something I have to ignore until apple comes up with a bug fix in 10.13.3

Thank you! This actually worked for me. I tried doing the update by allowing the App Store to detect it for me. I keep hitting update but it doesn't seem to finish the job so I keep getting the banner up on my App Store icon. This issue has been on going for a week and a few days nows.

I just downloaded from this link you gave and it did the trick. That download actually detected that the dmg pack is already installed in my system. I wouldn't have known. I sent that one to trash and proceeded with the one I got from this link and it did the job!

Thank you so much!!!

I tried just about everything on a brand new 2017 model Macbook Pro, and none of it worked. Even the standalone installers would go through all of the motions and the machine would STILL identify itself as 10.13.1

The ONLY thing that worked, was upgrading from 10.12.6 directly to 10.13.2 . That worked just fine, I couldn't get to 10.13.2 any other way.

This looks like an older thread, but I thought I would share what worked for me hoping it may possibly help someone else having this issue. I too tried multiple installs of 10.13.2 and all failed. Not knowing the cause of the failure, I searched and found this thread. I read them all. I use BitDefender on my Macbook Pro. I went in under

Security ---> Privacy and disabled my firewall with the admin password. I ran the update which took about 25 minutes to complete, and when it was finished and I logged back in, it showed updated to 10.13.2. I seems the firewall, at least on my machine, was the issue. I hope that helps somebody! 🙂

Fresh install= formatted partition and installed 10.13 just as it came from the Apple site. Tried to install the 10.13.2 Combo right after, again as it came from Apple. So, if I have something that prevents the installation, it came from Apple.......

Just out of curiosity, what HD format did you use? MacOS Extended or the new APFS? I was just at the Genius Bar and was told a few horror stories in running High Sierra from a MacOS Extended formatted partition, which is what I have.

The advice was to use an SSD APFS formatted. That of course prevents older OSes from residing on the same HD. And, BTW, ….. use an SSD.

Thanks for your help

LM

b.rydberg wrote:

Just out of curiosity, what HD format did you use?

Two of my Macs have Fusion drives and are formatted as HFS+. The other two are SSDs and are formatted as APFS.

And, BTW, ….. use an SSD.

I use both and both are fine.

Well, I have a 1TB SSD (not Apple) formatted HFS+ (I run all operating systems from 10.6.8 to 10.13) and all except High Sierra need HFS+.

High Sierra on HFS+ is quite funky, it really needs to be on an APFS formatted SSD.

I am looking for an external SSD with Thunderbolt, but so far the prices I have seen are scary .... :-)

Same here... Nothing I have tried has worked. I'm also on a company computer, and I'm not allowed to disable Kaspersky Internet Security which is my guess as to the culprit. Although since it doesn't work in safe mode I have no idea...

What ended up working for me (who knows why, maybe an antivirus prevented this directory from being created) was this:

Open the Terminal application. Type in "sudo mkdir -p /private/tmp" without the quotes and press enter. You'll need to enter your password and press enter again. Then try running the update again.