macos 15 sequoia

how-to-downgrade-from-macos-26-tahoe-on-a-new-mac

How to downgrade from macOS 26 Tahoe on a new Mac


Most new Macs can still be downgraded with few downsides. Here’s what to know.

An Ars Technica colleague recently bought a new M4 MacBook Air. I have essentially nothing bad to say about this hardware, except to point out that even in our current memory shortage apocalypse, Apple is still charging higher-than-market-rates for RAM and SSD upgrades. Still, most people buying this laptop will have a perfectly nice time with it.

But for this colleague, it was also their first interaction with macOS 26 Tahoe and the Liquid Glass redesign, the Mac’s first major software design update since the Apple Silicon era began with macOS 11 Big Sur in 2020.

Negative consumer reaction to Liquid Glass has been overstated by some members of the Apple enthusiast media ecosystem, and Apple’s data shows that iOS 26 adoption rates are roughly in line with those of the last few years. But the Mac’s foray into Liquid Glass has drawn particular ire from longtime users (developers Jeff Johnson and Norbert Heger have been tracking persistently weird Finder and window resizing behavior, to pick two concrete examples, and Daring Fireball’s John Gruber has encouraged users not to upgrade).

My general approach to software redesigns is to just roll with them and let their imperfections and quirks become background noise over time—it’s part of my job to point out problems where I see them, but I also need to keep up with new releases whether I’m in love with them or not.

But this person has no such job requirement, and they had two questions: Can I downgrade this? And if so, how?

The answer to the first question is “yes, usually,” and Apple provides some advice scattered across multiple documentation pages. This is an attempt to bring all of those steps together into one page, aimed directly at new Mac buyers who are desperate to switch from Tahoe to the more-familiar macOS 15 Sequoia.

Table of Contents

A preemptive warning about security updates and older versions of macOS

Before we begin: Apple handles macOS updates differently from iOS updates. Eventually, Apple requires devices that support the latest iOS and iPadOS versions to install those updates if they want to continue getting security patches. That means if your iPhone or iPad can run iOS or iPadOS 26, it needs to be running iOS or iPadOS 26 to stay patched.

Older macOS versions, on the other hand, are updated for around three years after they’re initially released. The first year, they get both security patches and new features. The next two years, they get security patches and new versions of the Safari browser. Macs running older-but-supported macOS versions also generally continue to get the same firmware updates as those running the latest macOS version.

Generally, we’d recommend against using macOS versions after security updates have dried up. For macOS 15 Sequoia, that will happen around September or October of 2027. Apple also sometimes leaves individual vulnerabilities unpatched on older operating systems; only the latest releases are guaranteed to get every patch. If you can look past the elements of Tahoe’s design that bother you most, staying on it is the safest option.

You can follow steps similar to the ones in this guide to downgrade some Macs to even older versions of macOS, but I wouldn’t recommend it; macOS 14 Sonoma will get security and Safari updates for only another six months or so, which isn’t long enough to justify spending the time to install it.

What we won’t cover is how to transfer data you want to keep from your Tahoe install to an older version of macOS. We’re assuming you have a new and relatively pristine Mac to downgrade, one that you haven’t loaded up with data other than what you already have synced to iCloud.

Can my Mac downgrade?

Mostly, yes. Any Mac with an M4 family chip or older, including the M4 MacBook Air and everything else in Apple’s current lineup, should support the current version of Sequoia (as of this writing, 15.7.4, with Safari 26.3).

As a rule of thumb, Macs will not run any version of macOS older than the one they shipped with when they launched. Apple provides security updates for older versions of macOS, but it doesn’t bother backporting drivers and other hardware support from newer versions to older ones.

The only Mac to launch since Tahoe was released is the M5 MacBook Pro, so owners of that system will need Tahoe or newer. If Apple puts out new Macs in early March as expected, those Macs will also only work with Tahoe or newer, and downgrades won’t be possible.

Although we’re mainly talking about new Macs here, these steps should all be identical for any Apple Silicon Mac, from the original M1 computers on up. If you buy a recently used Mac that ships with Tahoe installed, a downgrade still works the same way. We won’t cover the steps for installing anything on an Intel Mac—vanishingly few of them support Tahoe in the first place, and most people certainly shouldn’t be buying them at this late date.

Option one: A bootable USB installer

Apple hasn’t shipped physical install media for macOS in 15 years, but each downloadable installer still includes the bits you need to make a bootable USB install drive. And while late-Intel-era Macs with Apple T2 chips briefly made booting from external media kind of a pain, Apple Silicon Macs will boot from a USB drive just as easily and happily as early Intel-era Macs did.

This method will be the easiest for most people because it only requires you to own a single Mac—the one you’re downgrading.

Create the USB installer

Downloading the Sequoia installer through Software Update. Downloading this way serves as an additional compatibility check; your Mac won’t download any version of macOS too old for it to run.

Credit: Andrew Cunningham

Downloading the Sequoia installer through Software Update. Downloading this way serves as an additional compatibility check; your Mac won’t download any version of macOS too old for it to run. Credit: Andrew Cunningham

To make a USB installer, you’ll need a 32GB or larger USB flash drive and the downloadable macOS Sequoia installer. A 16GB drive was large enough for macOS for many years, but Sequoia and Tahoe are too large by a couple of gigabytes.

Apple’s support page here links to every downloadable macOS installer going back to 2011’s 10.7 Lion. In Tahoe, the macOS Sequoia link takes you to the App Store, which then bounces you to Software Update in the Settings app. This process has enough points of failure that it may not work the first time; try clicking the “Get” button in the App Store again and it usually goes.

If you’re downloading the installer from within macOS Tahoe, you’ll see a pop-up when the download completes, telling you that the installer can’t be run from within that version of macOS. Since we’ll be running it off of its own USB stick, you can safely ignore this message.

While the installer is downloading, install and prepare your USB drive. Open Disk Utility, click the View button, and select “show all devices.” Click the root of your USB drive under the “external” header in the left sidebar, and click the Erase button in the upper-right control area.

Change the disk’s name to whatever you want—I use “MyVolume” so I don’t have to change Apple’s sample terminal commands when copying the installer files—and make sure the Format is set to Mac OS Extended (Journaled) and the Scheme is set to GUID Partition Map. (That’s not an error; the macOS installer still wants an HFS+ filesystem rather than APFS.)

The handy thing is that if you have a larger USB drive, you can create installers for multiple macOS versions by partitioning the disk with the Partition button. A 64GB drive split into three ~21GB partitions could boot Tahoe, Sequoia, and another past or future macOS version; I just have it split into two volumes so I can boot Sequoia and Tahoe installers from the same drive.

Running the Terminal command to create our macOS 15 Sequoia boot drive.

Credit: Andrew Cunningham

Running the Terminal command to create our macOS 15 Sequoia boot drive. Credit: Andrew Cunningham

Once the Sequoia installer is in your Applications folder, run a Terminal command to copy the installer files. Apple has commands for each version of macOS on this page. Use this one for Sequoia:

sudo /Applications/Install macOS Sequoia.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

If you named the USB drive something other than MyVolume when you formatted it, change the name in the command as well. Note that names with spaces require a backslash before each space.

The Terminal will prompt you for your password and ask you to type Y to confirm. It will then reformat the drive and copy the files over. The time this takes will vary depending on the speed of the USB drive you’re using, but for most USB 3 drives, it should only take a few minutes to create the installer. When the Terminal command is done running, leave the disk inserted and shut down your Mac.

Using the USB installer

With your Mac powered down and the USB installer drive inserted, press and hold the power button on your Mac (the Touch ID button on any laptop or the dedicated power button on a desktop) until the text under the Apple logo changes to “loading startup options.” You should see the macOS Sequoia installer listed alongside Macintosh HD as a boot option; highlight it and click Continue. If you don’t see the Sequoia installer, you may need an extra step—highlight Options, then click Continue, and we’ll talk more about this momentarily.

Once booted, the Sequoia installer will automatically launch the macOS installer to do an in-place upgrade, which isn’t what we want. Hit Command+Q to quit the installer and click through the confirmation, and you’ll get the typical menu of recovery environment options; from here, launch Disk Utility, click the top level of the internal Macintosh HD disk, and click Erase. Click through the prompts to erase the Mac and restart.

My own macOS USB installer from my beloved Micro Center.

Credit: Andrew Cunningham

My own macOS USB installer from my beloved Micro Center. Credit: Andrew Cunningham

After the Mac restarts, you’ll need an Internet connection to activate it before you can do anything else with it; connect using the Wi-Fi menu in the top-right, typing in your network SSID and password manually if the menu doesn’t auto-populate. This will activate your Mac and get you back to the recovery environment menu.

Here, select the Sequoia installer and click through the prompts—you should be able to install Sequoia on the now-empty Macintosh HD volume with no difficulty. From here, there’s nothing else to do. Wait until the installation completes, and when it’s ready, it will boot into a fresh Sequoia install, ready to be set up.

If you didn’t see your Sequoia installer in the boot menu before and you clicked the Options gear instead, it usually means that FileVault encryption or Find My was enabled on the Mac—maybe you signed into your Apple account when you were initially setting up Tahoe before you decided you wanted nothing to do with it.

When you boot into the recovery environment, you’ll be asked to select a user you know the password for, which will unlock the encrypted disk. If all you want to do is erase the Mac and make it bootable from your USB stick, don’t worry about this; just select Recovery Assistant from the menu, select Erase Mac, and click through the prompts. Then, use the steps above to boot from your USB stick, and you should be able to install a fresh copy of whatever macOS version you want to the now-erased internal drive.

The nuclear option: A DFU restore

Normally, a bootable USB installer does everything you need it to do. It wipes the data from your Mac’s internal storage and replaces it with new data. But occasionally you need to drill a little deeper, either because your Mac becomes unresponsive or you’ve been running beta software and want to switch back to a stable release. Or just because other steps haven’t worked for you.

The nuclear option for resetting a Mac is a DFU (or Device Firmware Upgrade) restore. Based on the restore process for iPhones and iPads, a DFU restore uses a compressed IPSW archive that contains not only the macOS system files but also firmware files for all Apple Silicon Macs. The USB installer just replaces macOS; the DFU restore replaces everything from the firmware on up. (These are also the same files used to create macOS virtual machines using Apple’s Virtualization Framework.)

Because a DFU restore can only be performed on a Mac that’s booted into a special DFU mode, you’ll need a second Mac with a USB-C or Thunderbolt port, plus a USB-C cable. Apple says the USB-C charging cable included with Macs will work for this but not to use a Thunderbolt cable; I’ve used a generic USB-C cable, and it has worked fine.

The first step is to download the relevant IPSW file from Apple. This page on the Mr. Macintosh site is the one I have bookmarked because it’s a good repository of virtually every macOS IPSW file Apple has ever released, including beta versions for when those are useful.

First, download the macOS 15.6.1 IPSW file linked on that page (and here) to your host Mac (Apple stops releasing IPSW files for older OSes once newer ones have been released, so this is the newest file you’ll be able to get for macOS 15). Both iPhones and iPads have model-specific IPSW files, but for macOS, there’s just one image that works with all Macs.

On the Mac you’re trying to restore—we’ll call it the “target Mac” for simplicity’s sake—figure out which of its USB-C ports is the designated DFU port. There’s only one that will work, and it’s usually the leftmost or rightmost port. Plug one end of the USB-C cable into that DFU port and the other into any USB-C port on your host Mac and follow Apple’s instructions for how to boot the system into DFU mode.

A Mac in DFU mode will need permission before your Mac can work with it.

Credit: Andrew Cunningham

A Mac in DFU mode will need permission before your Mac can work with it. Credit: Andrew Cunningham

When it’s successfully booted into DFU mode, your host Mac will see the target Mac, and you’ll see the same notification you get any time you plug in USB accessories for the first time. Allow it to connect, open a Finder window, and scroll down the left-hand sidebar until you get to “Mac” under the Locations heading.

The Finder’s DFU interface is pretty simple—a picture, a line of text, and two buttons. We want to restore, not revive, the Mac. Clicking the Revive Mac button will normally download and install the latest macOS version from Apple. But you can force it to use a different IPSW file—like the Sequoia one we just downloaded—by holding down the Option key as you click it. Navigate to the IPSW file, open it, and allow the restore process to begin.

This will take some time; you can track progress in the first phase in the Finder window. After a few minutes, the Mac you’re restoring will light back up, and you can watch its progress there. Once the target Mac reboots with its signature chime, the process is complete.

Because the IPSW file is for an outdated version of Sequoia, the first thing you’ll want to do is hit Software Update for the latest Sequoia and Safari versions; you’ll be offered a Tahoe upgrade, but you obviously won’t want to do that after the trouble you just went through. Scroll down to “other updates,” and you’ll be offered all the non-Tahoe updates available.

Downgrader’s remorse?

You will run into a handful of downsides when running an older version of macOS, especially if you’re trying to use it with iPhones and/or iPads that have been updated to version 26.

Most of the awkwardness will involve new features introduced in Messages, Notes, Reminders, and other Apple apps that sync between devices. The Messages app in Sequoia doesn’t support background images or polls, and it handles spam filtering slightly differently. They’re minor absences and annoyances, mostly, but they’re still absences and annoyances.

At least for the time being, though, you’ll find Sequoia pretty well-supported by most of Apple’s ecosystem. Core services like iCloud and iMessage aren’t going anywhere; Xcode still supports Sequoia, as does every Apple Creator Studio app update aside from the new Pixelmator Pro. App support may eventually drop off, but there’s not a lot that requires the latest and greatest version of macOS.

If and when you decide it’s time to step up to a newer version of macOS, Tahoe (or whatever macOS 27 is called) will be there in Software Update waiting for you. You’ll need to install a new version eventually if you want to keep getting app updates and security patches. But you don’t have to yet.

Photo of Andrew Cunningham

Andrew is a Senior Technology Reporter at Ars Technica, with a focus on consumer tech including computer hardware and in-depth reviews of operating systems like Windows and macOS. Andrew lives in Philadelphia and co-hosts a weekly book podcast called Overdue.

How to downgrade from macOS 26 Tahoe on a new Mac Read More »

macos-15-sequoia-makes-you-jump-through-more-hoops-to-disable-gatekeeper-app-checks

macOS 15 Sequoia makes you jump through more hoops to disable Gatekeeper app checks

gate-kept —

But nothing is changing about the kinds of software you can run on your Mac.

The Mac's Gatekeeper feature has been pushing developers to digitally sign their apps since it was introduced in 2012.

Enlarge / The Mac’s Gatekeeper feature has been pushing developers to digitally sign their apps since it was introduced in 2012.

Apple/Andrew Cunningham

It has always been easier to run third-party software on a Mac than on an iPhone or iPad. Despite the introduction of the Mac App Store a couple of years after the iPhone’s App Store opened, it has always been possible to download and run third-party scripts and software on your Mac from anywhere. It’s one reason why the iPhone and iPad are subject to new European Union regulations about software sideloading and third-party app stores, while the Mac isn’t.

That’s not changing in macOS 15 Sequoia, the new version of macOS that’s due to be released to the public this fall. But it is about to get more annoying for some apps, according to a note added to Apple’s developer site yesterday.

“In macOS Sequoia, users will no longer be able to Control-click to override Gatekeeper when opening software that isn’t signed correctly or notarized,” the brief note reads. “They’ll need to visit System Settings > Privacy & Security to review security information for software before allowing it to run.”

Users (including me) had noticed this behavior in early macOS Sequoia betas, but this note confirms that the change was made on purpose and that the software is working as intended.

What’s changing and what isn’t

To understand what’s changing, it’s helpful to understand how macOS handles third-party apps. Though software can be downloaded and run in macOS from everywhere, Apple encourages developers to digitally sign their software and send it to Apple for notarization, which Apple describes as “an automated system that scans your software for malicious content, checks for code-signing issues, and returns the results to you quickly.” Notably, it is not the same as the app review process in Apple’s App Stores, where humans check submitted apps and can refuse to distribute them if they run afoul of Apple’s rules.

Notarization does come with benefits for users—users can be sure that the apps haven’t been tampered with and can run them with minimal hassle from Gatekeeper, macOS’ app-screening security feature. But it creates an extra step for developers and requires the use of a $100-a-year paid Apple Developer account, something that may not be worth the cost for hobby projects or open source projects that don’t generate much (or any) income for their contributors.

Unsigned, non-notarized software will refuse to run in current macOS versions, but it has always been possible to right-click or control-click the app or script you want to run and then click Open, which exposes an “open anyway” option in a dialog box that lets you launch the software. Once you’ve made an exception for an app, you can run it like you would any other app unless the software is updated or changed in some way.

The section of the Settings app where you'll need to go in macOS Sequoia to allow unsigned apps to run.

Enlarge / The section of the Settings app where you’ll need to go in macOS Sequoia to allow unsigned apps to run.

Andrew Cunningham

Which gets us to what Sequoia changes. The right-click/control-click option for easily opening unsigned apps is no longer available. Users who want to open unsigned software will now need to go the long way around to do it: first, try to launch the app and dismiss the dialog box telling you that it can’t be opened. Then, open Settings, go to the Privacy & Security screen, scroll all the way to the bottom to get to the Security section, and click the Open Anyway button that appears for the last unsigned app you tried to run.

This has always been an option for skirting around Gatekeeper, going all the way back to the days when Settings was still System Preferences (and when Apple would let you disable Gatekeeper’s checks entirely, something it removed in 2016). But it takes so much more time that I never actually did it that way once I discovered the right-click trick. Now, doing it the long way is mandatory.

I don’t want to oversell how disruptive this is—generally once you allow an app to run the first time, you don’t have to think about it again unless the app is updated or otherwise modified or tampered with. Apple isn’t allowing or disallowing any new behavior in macOS. Popular apps from major developers do tend to be notarized, rendering this change irrelevant. And if this change pushes more developers to sign and notarize their apps, that is arguably a win for user security and convenience.

But for most people most of the time, it’s just going to make a minor annoyance into a medium-size annoyance. And among the conspiratorially minded, it’s going to reignite 12-year-old anxieties about Apple locking macOS down to the same degree that it already locks down iOS and iPadOS.

The macOS 15 Sequoia update is currently available to developers and the general public as a beta if you’ve signed up for either of Apple’s beta programs. An early iteration of the 15.1 update with some Apple Intelligence generative AI features enabled is also available to developers with Apple Silicon Macs.

macOS 15 Sequoia makes you jump through more hoops to disable Gatekeeper app checks Read More »

“do-not-hallucinate”:-testers-find-prompts-meant-to-keep-apple-intelligence-on-the-rails

“Do not hallucinate”: Testers find prompts meant to keep Apple Intelligence on the rails

explain it to me like i’m an LLM —

Long lists of instructions show how Apple is trying to navigate AI pitfalls.

Craig Federighi stands in front of a screen with the words

Enlarge / Apple Intelligence was unveiled at WWDC 2024.

Apple

As the parent of a younger child, I can tell you that getting a kid to respond the way you want can require careful expectation-setting. Especially when we’re trying something new for the first time, I find that the more detail I can provide, the better he is able to anticipate events and roll with the punches.

I bring this up because testers of the new Apple Intelligence AI features in the recently released macOS Sequoia beta have discovered plaintext JSON files that list a whole bunch of conditions meant to keep the generative AI tech from being unhelpful or inaccurate. I don’t mean to humanize generative AI algorithms, because they don’t deserve to be, but the carefully phrased lists of instructions remind me of what it’s like to try to give basic instructions to (or explain morality to) an entity that isn’t quite prepared to understand it.

The files in question are stored in the /System/Library/AssetsV2/com_apple_MobileAsset_UAF_FM_GenerativeModels/purpose_auto folder on Macs running the macOS Sequoia 15.1 beta that have also opted into the Apple Intelligence beta. That folder contains 29 metadata.json files, several of which include a few sentences of what appear to be plain-English system prompts to set behavior for an AI chatbot powered by a large-language model (LLM).

Many of these prompts are utilitarian. “You are a helpful mail assistant which can help identify relevant questions from a given mail and a short reply snippet,” reads one prompt that seems to describe the behavior of the Apple Mail Smart Reply feature. “Please limit the reply to 50 words,” reads one that could write slightly longer draft responses to messages. “Summarize the provided text within 3 sentences, fewer than 60 words. Do not answer any question from the text,” says one that looks like it would summarize texts from Messages or Mail without interjecting any of its own information.

Some of the prompts also have minor grammatical issues that highlight what a work-in-progress all of the Apple Intelligence features still are. “In order to make the draft response nicer and complete, a set of question [sic] and its answer are provided,” reads one prompt. “Please write a concise and natural reply by modify [sic] the draft response,” it continues.

“Do not make up factual information.”

And still other prompts seem designed specifically to try to prevent the kinds of confabulations that generative AI chatbots are so prone to (hallucinations, lies, factual inaccuracies; pick the term you prefer). Phrases meant to keep Apple Intelligence on-task and factual include things like:

  • “Do not hallucinate.”
  • “Do not make up factual information.”
  • “You are an expert at summarizing posts.”
  • “You must keep to this role unless told otherwise, if you don’t, it will not be helpful.”
  • “Only output valid json and nothing else.”

Earlier forays into generative AI have demonstrated why it’s so important to have detailed, specific prompts to guide the responses of language models. When it launched as “Bing Chat” in early 2023, Microsoft’s ChatGPT-based chatbot could get belligerent, threatening, or existential based on what users asked of it. Prompt injection attacks could also put security and user data at risk. Microsoft incorporated different “personalities” into the chatbot to try to rein in its responses to make them more predictable, and Microsoft’s current Copilot assistant still uses a version of the same solution.

What makes the Apple Intelligence prompts interesting is less that they exist and more that we can actually look at the specific things Apple is attempting so that its generative AI products remain narrowly focused. If these files stay easily user-accessible in future macOS builds, it will be possible to keep an eye on exactly what Apple is doing to tweak the responses that Apple Intelligence is giving.

The Apple Intelligence features are going to launch to the public in beta this fall, but they’re going to miss the launch of iOS 18.0, iPadOS 18.0, and macOS 15.0, which is why Apple is testing them in entirely separate developer betas. Some features, like the ones that transcribe phone calls and voicemails or summarize text, will be available early on. Others, like the new Siri, may not be generally available until next year. Regardless of when it arrives, Apple Intelligence requires fairly recent hardware to work: either an iPhone 15 Pro, or an iPad or Mac with at least an Apple M1 chip installed.

“Do not hallucinate”: Testers find prompts meant to keep Apple Intelligence on the rails Read More »

my-favorite-macos-sequoia-feature-so-far-might-be-the-old-timey-mac-wallpaper

My favorite macOS Sequoia feature so far might be the old-timey Mac wallpaper

classic —

Combo wallpaper-screen saver is a walk down memory lane for classic Mac users.

The classic Mac OS wallpaper in macOS 15 Sequoia mimics the monochrome user interfaces used in System 1 through 6.

Enlarge / The classic Mac OS wallpaper in macOS 15 Sequoia mimics the monochrome user interfaces used in System 1 through 6.

Apple

I’m still in the very early stages of poking at macOS 15 Sequoia ahead of our customary review later this fall, and there are quite a few things that aren’t working in this first developer beta. Some of those, like the AI features, aren’t working on purpose; I am sure some of the iCloud sync issues I’m having are broken by accident.

I’ve already encountered a few functional upgrades I like, like iCloud support inside of virtual machines, automated window snapping (at long last), and a redesigned AirDrop interface in the Finder. But so far the change that I like the most is actually a new combo wallpaper and screen saver that’s done in the style of Apple’s Mac operating system circa the original monochrome Mac from 1984. It’s probably the best retro Mac Easter egg since Clarus the Dogcow showed up in a print preview menu a couple of years ago.

The Macintosh wallpaper and screen saver—it uses the animated/dynamic wallpaper feature that Apple introduced in Sonoma last year—cycles through enlarged, pixelated versions of classic Mac apps, icons, and menus, a faithful replica of the first version of the Mac interface. Though they’re always monochrome, the default settings will cycle through multiple background colors that match the ones that Apple uses for accent colors.

If you’re too young to be familiar (or if you were using MS-DOS in the mid-’80s instead of a Mac), this Mac theme hearkens back to the days before Mac OS (then Mac OS X, then OS X, then macOS) was called Mac OS. The first seven versions of the software were simply called System or System Software, all the way up through 1991’s System 7. The Mac OS name didn’t appear until the System 7.5.1 update in 1995, and the name was formally changed in the 7.6 update in 1997 (OS updates were obviously released at a more leisurely pace back then).

If you want to poke at a live, interactive version of the monochrome System Software, developer Mihai Parparita’s Infinite Mac project hosts classic System, Mac OS, and NeXTStep versions that will all run in a browser window using ports of various emulators.

My only complaint is that now I want more of these screen savers. As a millennial, my exposure to Systems 1 through 6 was fairly minimal, but I’d definitely take a color version of the screen saver modeled on Mac OS 9, or an early Mac OS X version with shiny candy-colored Aqua-themed buttons and scroll bars.

My favorite macOS Sequoia feature so far might be the old-timey Mac wallpaper Read More »

apple-quietly-improves-mac-virtualization-in-macos-15-sequoia

Apple quietly improves Mac virtualization in macOS 15 Sequoia

virtual realities —

It only works for macOS 15 guests on macOS 15 hosts, but it’s a big improvement.

Macs running a preview build of macOS 15 Sequoia.

Enlarge / Macs running a preview build of macOS 15 Sequoia.

Apple

We’ve written before about Apple’s handy virtualization framework in recent versions of macOS, which allows users of Apple Silicon Macs with sufficient RAM to easily set up macOS and Linux virtual machines using a number of lightweight third-party apps. This is useful for anyone who needs to test software in multiple macOS versions but doesn’t own a fleet of Mac hardware or multiple boot partitions. (Intel Macs support the virtualization framework, too, but only for Linux VMs, making it less useful.)

But up until now, you haven’t been able to sign into iCloud using macOS on a VM. This made the feature less useful for developers or users hoping to test iCloud features in macOS, or whose apps rely on some kind of syncing with iCloud, or people who just wanted easy access to their iCloud data from within a VM.

This limitation is going away in macOS 15 Sequoia, according to developer documentation that Apple released yesterday. As long as your host operating system is macOS 15 or newer and your guest operating system is macOS 15 or newer, VMs will now be able to sign into and use iCloud and other Apple ID-related services just as they would when running directly on the hardware.

This is still limiting for developers, who might want to run an older version of macOS on their hardware while still testing macOS 15 in a VM, or those who want to do the reverse so that they can more easily support multiple versions of macOS with their apps. It also doesn’t apply to VMs that are upgraded from an older version of macOS to Sequoia—it has to be a brand-new VM created from a macOS 15 install image. But it’s a welcome change, and it will steadily get more useful as Apple releases more macOS versions in the future that can take advantage of it.

“When you create a VM in macOS 15 from a macOS 15 software image… Virtualization configures an identity for the VM that it derives from security information in the host’s Secure Enclave,” Apple’s documentation reads. “Just as individual physical devices have distinct identities based on their Secure Enclaves, this identity is distinct from other VMs.”

If you move that VM from one host to another, a new distinct identity will be created, and your iCloud account will presumably be logged out. This is the same thing that happens if you backup a copy of one Mac’s disk and restore it to another Mac. A new identity will also be created if a second copy of a VM is launched on the same machine.

Mac users hoping to virtualize the Arm version of Windows 10 or 11 will still need to look to third-party products for help. Both Parallels and VMware offer virtualization products that are officially blessed by Microsoft as a way to run Windows on Apple Silicon Macs, and Broadcom recently made VMware Fusion free for individuals.

Apple quietly improves Mac virtualization in macOS 15 Sequoia Read More »