macOS 27 Ignores “Open Using Rosetta”: Fix Missing Intel Plug-ins

You upgraded to macOS 27 Golden Gate, opened the app you use every day, and something is quietly missing. An audio plug-in no longer shows up in the list. A printer that worked on Friday now stops with "Filter failed". A utility that used to launch now asks you to install Rosetta — or, worse, launches fine and simply doesn't do the one thing you kept it for. None of these produce an error that names the cause, and the cause is the same in every case: macOS 27 changed how Rosetta 2 behaves, and two of those changes are only mentioned in Apple's developer release notes.

This guide walks through what changed, how to find everything on your Mac that depended on the old behaviour, and how to fix each kind of breakage. The inventory commands were run on a real Apple silicon Mac before its upgrade. The macOS 27 behaviour comes from Apple's own release notes, and we quote them wherever we rely on them.

Key Takeaways

• Upgrading to macOS 27 removes Rosetta 2. Apple's release notes: "If Rosetta was previously installed, it is not automatically restored after upgrading to macOS 27.0." Reinstall it with softwareupdate --install-rosetta --agree-to-license.
• The "Open using Rosetta" checkbox is now ignored. Apps you forced into Intel mode launch natively, and any Intel-only plug-in they were loading silently disappears. Apple says these plug-ins "may not appear in Settings or trigger notifications of their incompatibility."
• Helpers break more quietly than apps. An Intel-only app shows a Rosetta install prompt. An Intel-only printer filter, background agent or command-line tool just fails. On the Mac we audited, 117 of the 341 executables inside the printer driver folders were Intel-only.
• Installers changed too. Packages that don't declare a host architecture now default to arm64, so their install scripts run natively.
• This is the last year of the grace period. Apple states that all Intel-based software, except legacy games, will no longer be compatible with macOS 28.

What Apple Changed in macOS 27

The Rosetta section of the macOS 27 release notes is short, and every line matters. The notes list one change under "New Features":

On launch, Applications previously set to "Open using Rosetta" by a user will have the application launch natively. Any compatibility issues requiring Rosetta from the past should be re-assessed on macOS 27.

The rest are under "Deprecations":

If Rosetta was previously installed, it is not automatically restored after upgrading to macOS 27.0.

Installer packages which specify no hostArchitecture will now default to arm64. Ensure any pre and post install scripts behave as intended under arm64.

Intel-based plugins and loaders may not appear in Settings or trigger notifications of their incompatibility. All Intel-based software will no longer be compatible with macOS 28.0, excluding legacy games.

The same note lists the plug-in folders to check: VSTs, HAL, ARA, PDEs, colour pickers and Quick Look or Spotlight plug-ins, in places like ~/Library/Audio/Plug-Ins/, ~/Library/Printers/ and ~/Library/ColorPickers/.

Rosetta itself is still available in macOS 27 — Apple's WWDC 2025 commitment was to keep it as a general-purpose tool through macOS 27. But the upgrade removes it, and it no longer honours the per-app Intel setting. So the Rosetta you reinstall runs Intel-only programs, but it will no longer run a universal app in Intel mode just because you ticked a box.

Three Ways the Change Breaks Things

The symptoms depend on what kind of Intel code you had.

What you had	What happens after the upgrade	How visible it is
An Intel-only app	"To open this app, you need to install Rosetta" prompt	Obvious — you get a dialog
A universal app set to "Open using Rosetta"	The app launches natively; its Intel-only plug-ins don't load	Silent — the plug-in just isn't listed
An Intel-only helper: printer filter, launch agent, CLI tool, installer script	The program fails to start	Silent or cryptic — "Filter failed", "Bad CPU type in executable", a failed install

The first case fixes itself the moment you reinstall Rosetta. The second is the one that catches people out: reinstalling Rosetta does not fix it, because the app no longer runs under Rosetta at all. The third needs Rosetta back and, for the long term, a native replacement.

Step 1: Put Rosetta Back (If You Need It)

If anything on your Mac is Intel-only — and on most Macs something is — reinstall Rosetta now rather than waiting for a prompt. Some of the programs that need it never show one.

softwareupdate --install-rosetta --agree-to-license

The --agree-to-license flag accepts the licence non-interactively. Without it, the command asks you to type A to agree. On Tahoe, softwareupdate --help lists the option as "Install Rosetta 2", and it is the same mechanism Apple uses for the in-app prompt.

To confirm Rosetta is installed and running:

# The Rosetta runtime directory exists only when Rosetta is installed
ls -d /Library/Apple/usr/share/rosetta 2>/dev/null && echo "Rosetta installed"

# oahd is the Rosetta translation daemon
pgrep -l oahd

# The installer receipt
pkgutil --pkgs | grep -i rosetta

On the Mac we used for this guide, still on Tahoe 26.5.2 before its upgrade, all three checks succeed: the directory exists, oahd is running, and the receipt is com.apple.pkg.RosettaUpdateAuto. After the macOS 27 upgrade, expect the first and last to return nothing until you reinstall.

Should you reinstall it at all? If you have nothing Intel-only, no. Staying without Rosetta is the clean state Apple is moving towards. But run the audit below before you decide — "I don't use any Intel apps" is often true of apps and false of drivers.

Step 2: Find the Apps You Had Set to "Open Using Rosetta"

The Finder's Get Info window has shown an Open using Rosetta checkbox for universal apps since the first Apple silicon Macs. People ticked it for one reason: the app itself was universal, but something it loaded — an audio plug-in, a scanner module, an add-in, a font or colour tool — was still Intel-only. A process runs as either arm64 or x86_64, never both, so the only way to load an Intel plug-in was to run the whole host app under Rosetta.

macOS stores that choice in the LaunchServices preferences, not in the app. You can list every app that has the flag set:

plutil -p ~/Library/Preferences/com.apple.LaunchServices/com.apple.LaunchServices.plist \
  | grep -E '^    "'

On our test Mac, this returns three entries under the "Architectures for arm64" dictionary:

    "ArcTime Pro" => [
    "com.ScooterSoftware.BeyondCompare" => [
    "ImageJ" => [

Each entry holds a bookmark to the app bundle followed by the string x86_64. One app had three bookmark and x86_64 pairs — three copies of the same app in different folders, each forced to Intel mode separately. That's how the setting builds up over years, and it's why the list is worth reading before you upgrade: you probably don't remember ticking all of them.

What these apps do on macOS 27

Per the release note, each of those apps now launches natively. The app itself will work, since it is universal. What stops working is whatever you needed Intel mode for. The release note warns that such plug-ins "may not appear in Settings or trigger notifications of their incompatibility", so you get no error. The plug-in just isn't in the list, or a menu item is missing, or a file format stops importing.

Make a note of every app on that list and, for each, answer one question: why did I tick this? If the answer is "an old plug-in", Step 3 finds it. If you don't remember, the setting may have been a workaround for a bug fixed years ago, and native mode may be fine.

Step 3: Audit the Plug-in Folders

Apps are easy to check because Finder and System Information show their kind. Plug-ins, drivers and filters are not, which is why Apple's note lists folders rather than apps. This loop walks the folders Apple names, plus the camera-plug-in folder, and prints every executable that has no arm64 code:

for dir in ~/Library/Audio/Plug-Ins /Library/Audio/Plug-Ins /Library/Printers \
           ~/Library/ColorPickers /Library/ColorPickers /Library/QuickLook \
           ~/Library/Spotlight /Library/Spotlight /Library/CoreMediaIO/Plug-Ins; do
  [ -d "$dir" ] || continue
  find "$dir" -type f -perm -u+x 2>/dev/null | while read -r f; do
    archs=$(lipo -archs "$f" 2>/dev/null) || continue
    case "$archs" in *arm64*) ;; *) echo "INTEL-ONLY  $f" ;; esac
  done
done

lipo -archs prints the architectures a Mach-O binary contains — x86_64 arm64 for universal code, arm64 or arm64e for native-only, x86_64 (sometimes with i386) for Intel-only. Scripts and data files make lipo fail, and the || continue skips them.

On our test Mac the result was entirely printer drivers:

Location	Intel-only executables
/Library/Printers/hp	108
/Library/Printers/KONICAMINOLTA	9
Audio, colour picker, Quick Look, Spotlight, camera folders	0

The printer folders held 341 Mach-O executables in total: 224 contained arm64 code and 117 did not. The five audio HAL drivers installed by third-party apps were all universal or native. It's worth checking anyway: every Mac's list is different, and a producer's Mac with ten years of Audio Units will look nothing like this one.

For individual apps, the same check is one line:

lipo -archs "/Applications/Some App.app/Contents/MacOS/$(defaults read "/Applications/Some App.app/Contents/Info" CFBundleExecutable)"

Of the 84 apps in this Mac's /Applications folder, 48 were universal and 11 were Intel-only. The rest were arm64-only. Those 11 are the apps that will ask for Rosetta after the upgrade.

Printers: The Breakage Nobody Connects to Rosetta

Printers deserve their own section because the failure never mentions Rosetta. The CUPS printing system passes each job through a chain of filters, and vendor drivers add their own filters and backends to that chain. On our test Mac, the Intel-only files included HP's hpPreProcessing and hpPostProcessing filters, HP's fax backend, and a Konica Minolta PostScript filter, psToKMC759PS.

When one of those filters can't run, the job stops and the queue shows Filter failed — exactly what Apple silicon owners saw in 2020 when they printed before Rosetta was installed. After the macOS 27 upgrade removes Rosetta, the same thing can happen to a printer that has worked for years.

There are three fixes, from quickest to most durable:

1. Reinstall Rosetta (Step 1). The filters run again under translation. This buys you the macOS 27 year and nothing more.
2. Update the vendor driver. Many vendors now ship universal drivers; the HP and Konica Minolta packages on our test Mac were old installs, not current downloads.
3. Switch the printer to AirPrint. Remove the printer in System Settings → Printers & Scanners, add it again, and in the Use menu choose AirPrint or Secure AirPrint rather than the vendor driver. AirPrint and IPP Everywhere are driverless, so there's no vendor filter to break. You may lose vendor-specific options such as stapling or finishing, but ordinary printing no longer depends on Rosetta.

The Print dialog has its own dependency. The extra panes it shows for a vendor driver come from Printer Dialog Extensions (PDEs), and three of the five HP PDEs on our test Mac were Intel-only. If a vendor options pane disappears from the Print dialog after the upgrade, that's the first place to look.

If you have already hit "Filter failed" and want the full diagnostic path, our printer filter failed fix guide covers the CUPS side in detail.

Audio Plug-ins and Other Plug-in Hosts

Music software is where the "Open using Rosetta" checkbox was used most. A universal DAW run under Rosetta could load a decade-old Intel Audio Unit or VST. On macOS 27 the DAW launches natively, so those plug-ins no longer load and are simply missing from its list.

To see what is actually running natively, open Activity Monitor and look at the Kind column on the CPU tab: every process shows Apple or Intel. After the upgrade, a host that used to show Intel will show Apple, and that's your confirmation that its Intel-only plug-ins are no longer being loaded.

Your options, in order of preference:

• Update the plug-in. Most actively maintained plug-in vendors shipped universal builds years ago. Check before assuming it's abandoned.
• Replace it with a native equivalent, and re-save the projects that used it while you can still open them with the old setup — on a second Mac, or before upgrading this one.
• Freeze the old setup. If a project depends on an abandoned Intel plug-in, finish or bounce it down on a Mac still running Tahoe. macOS 28 removes the general-purpose Rosetta option entirely, so Golden Gate is not a place to park that dependency for long.

The same logic applies to any plug-in host: image editors with old filters, office suites with add-ins, scientific tools with Intel-only modules, and color pickers or Quick Look plug-ins that the Finder loads on your behalf.

Can You Still Force an App to Run Under Rosetta?

The checkbox is gone, but the command-line route to Intel mode may not be. On Tahoe, arch launches the x86_64 slice of a universal binary under Rosetta:

arch -x86_64 /usr/bin/uname -m    # prints x86_64 on Tahoe with Rosetta installed
uname -m                          # prints arm64

For an app, you would point arch at the executable inside the bundle:

arch -x86_64 "/Applications/Some App.app/Contents/MacOS/Some App"

Treat this as untested on macOS 27. We ran the commands above on Tahoe 26.5.2. Apple's release note talks only about the "Open using Rosetta" setting, and it says nothing either way about arch. Apple's direction is also clear: it asks you to re-assess any compatibility issue that needed Rosetta. Even if the trick works on Golden Gate, it's a way to finish one job, not a setup to keep.

Installers That Now Run Their Scripts as arm64

The quietest change is in the installer. A flat package's Distribution file can declare which host architectures it supports, with an attribute on its <options> element:

<options customize="never" hostArchitectures="arm64,x86_64"/>

Apple's note says packages that "specify no hostArchitecture will now default to arm64". Older packages that never set the attribute used to get Intel behaviour on Apple silicon, so their pre- and post-install scripts ran under Rosetta. Now they run natively. A script that calls an Intel-only helper, or checks the architecture and takes the wrong branch, can make the whole installation fail.

When an older installer reports "The installation failed", check whether this is the cause:

# Unpack the package without installing it
pkgutil --expand "Some Installer.pkg" /tmp/pkg-inspect

# Does it declare host architectures?
grep -o 'hostArchitectures="[^"]*"' /tmp/pkg-inspect/Distribution

# What did the installer log say?
grep -i -E "error|failed" /var/log/install.log | tail -20

If the grep finds no hostArchitectures attribute and the log shows a script failing, you've found it. The fix belongs to the vendor, but reinstalling Rosetta often lets the Intel helper inside the script run, which may be enough for a one-off install. Apple is also asking developers to audit "any remaining installer plugins", so old packages with custom installer panes are the likeliest to break.

What About Games?

Games are the one exception Apple has carved out for macOS 28 and later, and you may see a game-test-tool command mentioned online. The release notes describe it precisely:

A new command line tool lets you enable support for legacy Intel-based games during beta releases. To enable it, run the following command in Terminal: sudo game-test-tool enable.

The same note adds three caveats that rule it out as a general workaround: enabling it "disables Rosetta", "non-game processes might crash or behave unexpectedly", and the feature "is not available outside of macOS beta releases". It is a testing switch for the gaming subset Apple plans to keep. It won't bring back the checkbox, and it isn't meant to be on a shipping Mac.

The Timeline You Are Now On

Release	What Rosetta does
macOS 26 Tahoe	Full Rosetta; "Open using Rosetta" checkbox honoured
macOS 27 Golden Gate	Rosetta removed on upgrade, reinstallable; checkbox ignored; general-purpose translation still works
macOS 28	"All Intel-based software will no longer be compatible", excluding legacy games

So you have one release left. The practical way to spend it is to use Rosetta as a bridge while you replace each Intel dependency on your list, rather than rebuilding the old setup and forgetting about it.

For the wider plan — which categories of software are most exposed and how to budget the migration — see our Rosetta 2 end-of-life guide and the Intel app audit guide.

A Ten-Minute Post-Upgrade Checklist

If you've just upgraded and want to know where you stand, go through this list in order:

1. Run plutil -p ~/Library/Preferences/com.apple.LaunchServices/com.apple.LaunchServices.plist | grep -E '^ "' and write down every app listed.
2. Run the plug-in audit loop from Step 3 and save the output to a file.
3. Check /Applications for Intel-only apps with lipo -archs or the Kind column in Activity Monitor.
4. If either list is non-empty, reinstall Rosetta with softwareupdate --install-rosetta --agree-to-license.
5. Print a test page on every printer you use.
6. Open each app from step 1 and check that the plug-ins you actually use are still listed.
7. For each Intel item that matters, note its native replacement or the date you'll retire it.

The whole list takes about ten minutes, and it turns "something is missing" into a list you can work through.

Troubleshooting Common Issues

A plug-in is missing but Rosetta is installed

Problem: You reinstalled Rosetta, but the plug-in still doesn't appear in the host app.

Solution: The host now runs natively because macOS 27 ignores "Open using Rosetta", and a native process can't load Intel code. Confirm with the Kind column in Activity Monitor. Update or replace the plug-in. Rosetta alone won't bring it back.

"Bad CPU type in executable" in Terminal

Problem: A command-line tool or script that worked before now fails with this message.

Solution: The binary is Intel-only and Rosetta isn't installed. Check with lipo -archs $(which toolname), reinstall Rosetta, and look for a native build — Homebrew users should reinstall from an arm64 Homebrew prefix in /opt/homebrew.

A background app stopped doing its job

Problem: A sync tool, menu-bar helper or launch agent seems to have stopped without an error.

Solution: Helpers launched by launchd have no window to show a Rosetta prompt in. List the agents with ls ~/Library/LaunchAgents /Library/LaunchAgents /Library/LaunchDaemons, find each one's ProgramArguments path, and check it with lipo -archs.

The installer fails with no clear reason

Problem: An older .pkg reports that the installation failed.

Solution: Follow the installer section above: expand the package, check for hostArchitectures, and read /var/log/install.log. Reinstalling Rosetta and trying once more is a reasonable one-off workaround.

Printing fails only for one printer

Problem: AirPrint printers work, and one printer using a vendor driver fails.

Solution: Its vendor filter is almost certainly Intel-only. Reinstall Rosetta, update the driver, or re-add the printer using AirPrint.

FAQ

Does macOS 27 still include Rosetta 2?

Yes, as a reinstallable component. Upgrading removes it, and you add it back with softwareupdate --install-rosetta --agree-to-license or through the prompt an Intel app triggers. Apple's commitment is general-purpose Rosetta through macOS 27, with only legacy games supported afterwards.

Why did Apple stop honouring "Open using Rosetta"?

Apple's note gives the rule, not the reasoning: previously flagged apps launch natively, and compatibility issues should be re-assessed. The likely intent is to find hidden Intel dependencies while Rosetta still exists, instead of having them all fail at once in macOS 28.

Will reinstalling Rosetta bring back my Intel plug-ins?

Only if the plug-in's host itself is Intel-only. If the host is universal and you had forced it into Intel mode, macOS 27 now launches it natively regardless, and the Intel plug-in can't load. You need a universal version of the plug-in.

How do I tell whether an app is Intel-only?

Run lipo -archs on the executable inside the bundle, or check the Kind column in Activity Monitor while it runs. x86_64 alone means Intel-only; x86_64 arm64 means universal; arm64 or arm64e means Apple silicon only.

Is it safe to leave Rosetta uninstalled?

Yes, if nothing you use needs it. Rosetta isn't needed by macOS itself. But run the plug-in and printer audit first, because helpers and drivers fail without asking for Rosetta.

Conclusion

macOS 27 turns Rosetta from a background assumption into an explicit choice. The upgrade removes it, the per-app Intel switch no longer works, and installers stop defaulting to Intel. Anything that relied on those defaults now fails, and most of it fails without an error that mentions Rosetta.

The fix is mostly inventory. List the apps you forced into Intel mode, run the plug-in audit, print a test page, and reinstall Rosetta only if the lists say you need it. Then use the rest of the Golden Gate year to replace each Intel item before macOS 28 removes the option for good.

Related reading: macOS 27 Golden Gate day-one update guide · Rosetta 2 end-of-life guide · Intel app audit before macOS 27 · Printer "Filter failed" fix guide · The end of the Intel Mac era