Apple:

In macOS 28 and later, the Mac OS Extended file system format will be supported only for volumes (disks and other storage devices) that aren’t encrypted. For future macOS compatibility, either decrypt or reformat any encrypted Mac OS Extended volumes.

I think Apple removed the user interface for creating such volumes way back in Big Sur. It’s not really surprising that they’re going away, although only offering a year of warnings seems rather aggressive. Many people delay updating to major OS versions or wait until they get a new Mac. There will be users that switch to a Mac that can only run macOS 28 and get rid of their old one before realizing that some drive they haven’t connected in a while won’t mount.

The other surprising part is that Apple’s options—reformat or decrypt—are not great. During the initial transition to APFS, macOS would transparently convert an encrypted HFS+ boot volume to encrypted APFS without rewriting any data. This functionality is nominally still available via the diskutil apfs convert command, but Apple hasn’t mentioned this or built an automatic upgrader GUI.

[Decrypting] doesn’t apply to encrypted Time Machine backup disks.

It’s obvious why. The old Time Machine format with hard links is totally different from the new one based on APFS snapshots. But this means that you’ll either need to buy a new Time Machine drive for use with macOS 28 or delete your backup history. Even if you keep the old drive, you’ll need an older boot drive or an old Mac in order to be able to access it.

Previously:

• Searching Time Machine Backups and Versions
• macOS 27 Golden Gate Announced
• macOS 27 to Drop Support for AirPort and Time Capsule Backups
• Removing Unwanted APFS Time Machine Backups
• Should You Continue Using HFS+?
• Time Machine Evolution and APFS
• SuperDuper 3.3 for Catalina
• APFS to be Mandatory for SSDs in High Sierra

Update (2026-07-24): Marcus Mendes:

Apple has now revised the page to add a third option, allowing users to convert an encrypted HFS+ volume directly to encrypted APFS without decrypting it first.

[…]

The company has also removed its previous instructions for decrypting the volume first, converting it to APFS without erasing it, and then optionally re-encrypting it.

Hammer:

Ignore Apple’s guidance and do not use Convert to APFS in Disk Utility for disk images.

The first encrypted HFS+ disk image I tried to convert that way failed and left me with an unusable disk image. If I didn’t have backups I’d have lost its contents.

It didn’t corrupt the disk images that I tried, but it didn’t work, either, instead failing with an error about expecting a GPT partitioning scheme.

Update (2026-07-28): Howard Oakley:

As encrypted disk images have never used CoreStorage, withdrawal of support for that has no impact on the continued use of any form of encrypted disk image, including those using HFS+ as their virtual file system.

This is a good point. Apple’s support page refers to “encrypted Mac OS Extended disks,” but the developer release notes refer to CoreStorage specifically. So this shouldn’t affect most encrypted disk images, which show up in Finder as unencrypted after mounting. The encryption is at the disk image level rather than at the file system level. However, I’m not sure that all encrypted disk images are safe. Presumably, a device image, which directly copies the blocks rather than the files, would still use CoreStorage.

Mike Bombich:

The USB device drivers report that they are destroying the “Rocket XTRM Q” device due to a “link change interrupt”

APFS filesystem drivers report a “dangling mount”, failures to finish transactions before unmount, and dozens of “media is not present” errors.[…]

storagekit collects a report of the “disappeared” devices and notices that one of them was mounted. This is ultimately what leads to the “Disk Not Ejected Properly” notification.

Unfortunately, nothing in here explains what caused the “link change interrupt”; all we know is that the USB device drivers detected an interruption.

Not discussed here, perhaps because there’s little we can do about it, is the role of changes to macOS. I’ve documented problems in the past of hard drives, which used to work perfectly, suddenly start spontaneously unmounting with every backup after updating to a new OS version. The Sierra to Big Sur period was particularly bad, as I recall. (There are also some hard drive enclosures, and cheap SSDs, that seem to be problematic to matter the OS version, but I don’t continue to use those.) Sometime around Monterey or Ventura, the spontaneous unmounts almost completely disappeared for me, though Ventura introduced other mounting/unmounting problems. Last week, I finally updated to Tahoe, and I’m sad to say that spontaneous unmounts are back. Almost every night, one of my Samsung SSDs—connected to a Thunderbolt dock—gets reported as improperly ejected. Sometimes it remounts by itself; other times I have to unplug and replug it.

Previously:

• Upgrading My Mac’s External SSD
• Remaining Issues in Big Sur
• OWC Dual Drive Dock USB 3.1
• Some Known Bugs in macOS 10.12.6
• RocketStor Drive Dock: More Expensive But Reliable
• Highpoint RocketStor 5212 Thunderbolt Dual Drive Dock
• Ejecting External Disks With macOS 13
• Ventura Issues

Update (2026-07-09): Rosyna Keller:

I keep getting these errors too. It only started when I connected the external SSD to a OWC Thunderbolt dock. It never happened with direct connect.

My Thunderbolt dock is from Anker.

Update (2026-07-10): Matt:

I also just stared getting these a bunch. Mine is connected to a CalDigit Thunderbolt dock.

I have to wonder if something changed in a recent update (15.7/26.4?)

macOS 27 Golden Gate Beta 3 Release Notes:

Apple Intelligence for Home requires an iCloud+ subscription starting at 2TB.

Via Rajesh Pandey:

As part of the upgrade, the Home app uses AI to generate summaries of motion alerts from compatible HomeKit Secure Video cameras.

[…]

Apple likely requires the 2TB iCloud+ tier because HomeKit Secure Video already relies on iCloud+ storage tiers. The 2TB plan supports a larger number of cameras, and AI-generated video descriptions would add to Apple’s cloud processing costs.

That makes sense, but it seems odd because the iCloud tiers are named based on storage amounts, yet the feature isn’t tied to how much space you’re actually using. A lower iCloud plan with tons of free space doesn’t get the features, yet a nearly full 2 TB plan does. There are already restrictions where supporting more cameras requires higher plans, but that is at least quasi related to storage.

I reluctantly upgraded to a 2 TB family plan within the last year or so. We don’t store many files in iCloud, messages are set to auto-delete after a year, and I manually offload photos older than a year (except for hearted favorites). It’s hard to believe given how I remember the original 5 GB free tier once being sufficient, but staying under 200 GB became untenable without a lot of extra work. It doesn’t help that Live Photos sometimes gets inadvertently turned on, so that we’re storing all these little videos without realizing it.

Previously:

• “Don’t Let Me Go” and iCloud Storage Tiers
• Limiting iMessage’s Disk Usage
• The Missing iCloud Storage Bump