How to install macOS 27 Golden Gate on an unsupported Mac

Can you install macOS 27 on an unsupported Mac? I want to tackle this one clearly, because I’ve seen so many frustrated Intel users with a perfectly good MacBook who’ve just discovered that macOS 27, released on 14 September 2026, runs only on Macs with Apple silicon.

The short answer today is that there is no way to do it. The community patching tool people usually turn to, OpenCore Legacy Patcher, has said it has no plans to attempt macOS 27 at all.

That’s a change from previous years, when OCLP could eventually bring an unsupported Mac onto a new macOS release. Here’s what the project actually said, and what it means for your Mac.

Can OpenCore Legacy Patcher install macOS 27?

No, and not just because support is still being worked on. In its official statement on macOS Golden Gate 27, the OpenCore Legacy Patcher team wrote that “the team remains focused on macOS Tahoe 26 and releases previously supported by OCLP — there are currently no plans to attempt working with Golden Gate.”

The reason is technical rather than a matter of time. The same statement explains that in macOS 27 the userspace is “almost entirely Apple silicon-only” apart from Safari and command line tools kept for Rosetta, and that most kernel extensions for Intel-based Macs have been removed. What is left, the team wrote, “is not enough to grant entry to this release of macOS.”

Worth saying clearly, because it is easy to misread: this is not the end of OpenCore Legacy Patcher. The team is still working on macOS Tahoe 26 support for Intel Macs, and says it cannot give an ETA. It is macOS 27 specifically that is ruled out.

Apple's side of this matches: macOS 27 runs only on Macs with Apple silicon, and every model on Apple's compatibility list has an M-series or A-series chip. There is no Intel Mac for a patcher to bring across.

What are the risks when installing macOS 27 on an unsupported Mac?

Any unsupported installs come with risks, but I just want to be really clear and explicit about what those really are.

It can mean broken graphics acceleration, Wi-Fi issues, and sleep problems. You might also get missing features, failed point updates, or a Mac that needs patching again after every update.

It’s also possible that your security gets weaker, and that’s because you’re relying on unofficial patches and hardware Apple no longer supports.

There’s also a macOS 27-specific limitation worth knowing. Several of its headline features — Siri AI, Visual Intelligence, and the intelligent photo editing tools — depend on Apple Intelligence, which Apple supports only on Apple silicon Macs with M1 or later. An Intel Mac would miss those features even if a patched install were possible.

What you need before you begin

1. Find your Mac’s model identifier

Go to your Apple menu > About This Mac > More Info > System Report and match that identifier against the current OCLP supported models list.

2. What you’ll need

• A full Time Machine backup or bootable clone — do not skip this

• A USB drive large enough for the macOS installer

• Enough free storage to build the installer

• Time to troubleshoot if something breaks

Before backing up, I’d also clear up any obvious junk to make sure your backup is smaller and there’s room to work. CleanMyMac’s Cleanup feature can do this as it clears up system junk, while its My Clutter feature can also help find any large, old, and duplicate files. Start your free CleanMyMac trial — run a deep system clean before building the installer.

Why OpenCore Legacy Patcher can’t install macOS 27

In previous years, this is the point where a guide would list the steps: build the OpenCore configuration, create a patched installer, boot through OpenCore, then run a post-install root patch for graphics and Wi-Fi. That sequence doesn’t apply to macOS 27, because the installer it depends on has no Intel path to patch.

Intel kernel extensions have been removed from macOS 27, so the hardware a patcher would need to support is no longer addressable; the userspace is Apple silicon-only apart from Safari and command line tools; and OCLP has no plans to attempt the release, so no patched installer is being produced.

If your Mac is already running a patched install of an earlier macOS, OpenCore stays on the drive and your Mac boots through it — so don’t delete it.

If you already run a patched Mac

Updates need extra caution: before installing any macOS point release, update OCLP first and check the GitHub release notes for known issues. Unsupported installs can work, but they need maintenance, backups, and a lot of patience. If you’re on Tahoe 26 or earlier, that is where OCLP’s current work is focused.