macOS High Sierra and APFS: Cautions!

October 6th, 2017

A computer’s file system may not seem to be a terribly interesting topic of discussion, but it becomes interesting when there’s the potential for things to go bump.

So along with the release of the first developer beta of macOS Sierra in June of 2016, Apple included a prerelease version of the Apple File System (APFS), a major update to the previous file system, HFS+, which was released in 1998 as an update to HFS.

Now the file system governs how a computing device, be it a smartphone, a tablet, or a personal computer, reads, writes, catalogs and stores data. If things go wrong with the index or catalog file, you can lose files, or some might end up damaged. While HFS+ worked well enough for tens of millions of Mac users, and hundreds of miles of users of iPhones and iPads, something had to give, so Apple finally developed a modern solution.

So you have such goodies as 64-bit support, robust file encryption, improved performance and efficiency, superior protection from disk catalog damage, and, under some circumstances, near instantaneous duplication of a file.

Obviously Apple proceeded slowly to implement APFS. Last year’s developer version could be installed on Macs with SSDs, but it didn’t support traditional hard drives nor that combo of HDD and SSD, the Fusion drive.

I sort of expected it would be fully implemented with Sierra’s successor, but that’s still a work in progress, which I’ll get to shortly.

But for users of iOS gear, an en masse conversion to APFS occurred virtually without a hitch with the 10.3 update. Hundreds of millions of people had their devices converted in the space of a few days. It was hard to see much of a change. You may have found more free space on our iPhone or iPad, but performance was not significantly different one way or the other. I noticed on my wife’s iPhone 5c that the amount of free space on the 16GB device was little changed. I didn’t bother to compare the before or after on any other device in our household, mostly because I have plenty of free space on my iPhone, and Barbara had no complaints about her iPad.

I suppose you might call it a dry run ahead of the expected conversion on Macs, though I’m sure Apple did a lot of testing before releasing APFS into the wild on such a grand scale. It also made me feel more confident about what might happen on the Mac once High Sierra was released.

With the first macOS High Sierra betas, Apple did provide the choice of converting Fusion drives, but put that to a halt when people ran into troubles. Unfortunately switching back to HFS+ involves invoking some Terminal commands, provided by Apple in a support document to public beta testers, and a full backup, erase and restore.

With the final release of High Sierra, you didn’t have a choice on an SSD. It was automatically convered for better or worse. A regular hard drive can be converted manually in Disk Utility, and I did that on two external drives with mixed results. There is no support for Fusion drives, but that’s promised by Apple in a “future update.”

As I reported yesterday, however, Time Machine evidently doesn’t like APFS. The external drive formatted in APFS was reverted to HFS+ with the first backup. So that, as they say, is that.

Unfortunately, APFS may have other problems. They seem to be related to a few apps, but I’d think that software the follows Apple’s guidelines in reading and writing data ought to work properly with APFS, and if there are problems, they are Apple’s to fix.

On the other hand, if a developer is doing something funky in the way an app talks to the file system, all bets are off.

So far there have been reports that the Unity gaming engine has problems, and a more recent report from AppleInsider mentions APFS issues with AutoCAD 2017 and Adobe Acrobat and Illustrator CC. If it’s a publisher’s issue, there will be updates to recent versions. But if you use an older version of an app, it’s very possible it’ll never work correctly under APFS.

Indeed, I’m going to try my old Adobe CS apps on my 2010 MacBook Pro, whose SSD was converted APFS, to see if any issues arise before I allow my iMac to undergo this conversion.

These reports also raise the possibility that other apps are going to have compatibility issues, but it may again be something Apple can fix for everyone rather than inconvenience customers who, for one reason or another, stick with an older version of an app.

At this point, if you haven’t installed High Sierra yet on a Mac with an SSD, it may be a good idea to check the compatibility of your apps. If you consult our Comments section, you’ll see a post listing a way to hack the installer package to prevent the APFS conversion. It may be the perfect solution, but I won’t endorse something that hasn’t been thoroughly tested. It would be far easier just to hold off for a while. The advantages of High Sierra aren’t so significant that you can’t live without it for a while.

These early release issues may be massaged away with a few maintenance update. There’s already a “Supplemental Update” for High Sierra, which was released Thursday to fix a handful of problems.

I’m still perfectly happy with my decision to install High Sierra. But when or if there’s an update that adds APFS support for Fusion drives, I’ll be gun-shy about converting until I know that my vintage Adobe apps are going to work properly.  I want to avoid the need to subscribe to CS if I can.

Otherwise, I am not changing my qualified recommendation, just adding a few more cautions.

| Print This Article Print This Article

9 Responses to “macOS High Sierra and APFS: Cautions!”

  1. dfs says:

    “As I reported yesterday, however, Time Machine evidently doesn’t like APFS. The external drive formatted in APFS was reverted to HFS+ with the first backup. So that, as they say, is that.” In all probability this is a feature, not a bug (see the section on Time Machine in this article This seems to be because the High Sierra design time realized that even if you have a Mac with a SSD, in all probability your Time Machine will be backing up to a standard HD external drive, and so your backups need to preserved in a format that your HD can handle. Think of the alternative: if your Mac’s Time Machine started producing APFS backups that your external HD couldn’t handle, and you’d be one very unhappy camper.

  2. dfs says:

    sorry, read “design team”

  3. gene says:

    Once again, the HD was formatted as APFS before I ran the Time Machine backup. But it converted the drive back to HFS+. I described the phenomenon, and Apple wouldn’t do that unless it was deliberate. It’s not an artifact of something that went astray. But people should be better informed as to how things are going to work.


  4. Jimmy says:

    How does APFS/ High Sierra work with 3rd party SSDs, like Samsung?
    I read there are problems with OWC SSDs.

    • gene says:

      Yes, one problem appears to involve the OWC Aura drives for some Macs, including MacBook Air and the 2013 Mac Pro. Apple and OWC are reportedly working on a solution. It appears that the High Sierra installer is mistaking the SSDs for rotational drives, and thus the installation fails.

      I have an OWC on my 2010 MacBook Pro, but High Sierra did its thing there, including the APFS conversion, without any problems.

      But I’m not surprised to learn about possible problems with third-party storage devices. That’s why my recommendation for High Sierra is conditional.


  5. Walt French says:

    I don’t know if it’s APFS or something else, but my Home/Student version of Excel® for Mac 2011 is marked as EOL, not supported on 10.11.

    Disk Warrior has saved my bacon more than once, and Alsoft reports it, too is incompatible. They give two reasons: first, that they were disrupted by a hurricane; second, that Apple has not released final specs on APFS for them to be confident with their intricate directory and meta-data recovery/correction.

    I’ve held off upgrading to 10.11 partly because of these incompatibilities. Maybe APFS will obsolete Disk Warrior, although I haven’t seen any claims about superior data de-corruption. Maybe Microsoft hasn’t coded in incompatibilities with APFS and I won’t be forced into the newer version with no new features of interest to me.

    • It’s 10.13 now. I don’t know about Disk Warrior, but it would have to be updated, as would any utility that deals with the file system, to function with APFS.

      Microsoft is marking Office 2011 due to the age of the suite rather than necessarily an APFS issue. But I wouldn’t be surprised if there were some.


  6. Jimmy says:

    You can bet old Al at Alsoft will have DW up and running for 10.13 and APFS pretty soon.

  7. Jeremy Fryman says:

    I had problems with the new Photos. A significant improvement in the interface and it does allow me to use the external apps.
    However, all my files used to be archived on an external hard drive.
    This causes problems for Photos, export, duplicate and calling the external editor.
    Moved it all to the local Mac HD, no problems.

Leave Your Comment