What you will achieve
Install Rosetta 2 so Intel-only apps and installers run on Apple Silicon Macs.
Rosetta 2 is Apple’s translation layer for x86_64 binaries on arm64 Macs. It installs once per system and updates silently with macOS. You do not run Rosetta as an app — it activates per process when you launch Intel software.
1) Automatic install
- Open any Intel application or installer.
- Click Install on the Rosetta prompt and authenticate.
- Reopen the app — no restart needed.
2) Terminal install
softwareupdate --install-rosetta --agree-to-license3) Confirm installation
Open Activity Monitor while running an Intel app — Kind shows Intel. Or check:
pgrep -q oahd && echo "Rosetta active"4) Prefer native when possible
Universal and arm64 builds use less RAM and start faster. Use Rosetta only for apps without Apple Silicon builds.
5) Managed Macs
IT may deploy Rosetta via MDM. If install is blocked, request policy exception.
6) Remove or reinstall Rosetta
Rosetta is not a user-visible app in Applications. Reinstall by rerunning softwareupdate --install-rosetta --agree-to-license if oahd daemon crashes. Do not delete system Rosetta files manually — breaks all Intel binaries.
7) Performance expectations
Translated apps may use 10–30% more memory than native arm64 builds. If Activity Monitor shows sustained swap while running one Intel app, seek a native update or alternative. Creative Cloud, Office, and Chrome ship Universal binaries — update before relying on Rosetta.
8) Licensing and virtualisation
Some enterprise licences count Rosetta layers as separate seats — rare but check compliance. UTM and Parallels can run x86 guests on Apple Silicon with performance cost; prefer arm64 Linux images when testing servers.
Verify
Target Intel app launches without translation errors.
9) Classroom and lab deployment
IT admins pre-install Rosetta in golden images with softwareupdate --install-rosetta --agree-to-license in setup scripts. Students hitting Rosetta prompt mid-lesson waste time — pre-stage before term starts.
Additional troubleshooting notes
If steps above do not resolve the issue on the first attempt, reboot once, confirm System Settings → General → Software Update is current, and retry with a second administrator account to rule out profile or keychain corruption in your daily user. Document exact error text from Console.app with timestamp — vague “it still fails” without logs wastes support time. On Apple Silicon, re-test after full shutdown (not just restart) because firmware and Thunderbolt controllers reset only on cold boot. Intel Macs should repeat test in Safe Mode to bypass third-party login items. Before erase or keychain reset, verify Time Machine or clone backup completed — batch 3 guides assume Monterey/Ventura/Sonoma/Sequoia paths in System Settings; search Spotlight for renamed panes if your macOS version labels differ slightly.