Enterprise IT checklist for auditing Intel‑only Mac software before Rosetta removal

9To5Mac advises IT teams to audit their fleets now, deploy a Mosyle script workaround, and plan for a 90‑day testing block before rolling out macOS 27.

Overview of the Rosetta timeline

macOS 27 (Golden Gate) will automatically remove Rosetta upon installation, making it the last macOS version that can run on Intel‑based Mac hardware, expected in fall 2026. After macOS 27, Apple will retain Rosetta only as a limited version for older unmaintained games beginning with macOS 28, which Apple anticipates in fall 2027 and will end support for virtually all Intel‑only software. Apple’s WWDC 2025 statement noted that Apple would provide Rosetta for the next two major macOS releases, through macOS 27, to help developers migrate Intel apps to Apple silicon.

Apple expects macOS 27 in fall 2026 and macOS 28 in fall 2027.

Auditing Intel‑only software

IT teams should audit their fleets now while there is still time to deploy workarounds or engage vendors about native builds, as advised by 9To5Mac. Administrators can identify Intel‑dependent apps using third‑party tools such as iMazing’s free “Silicon” scanner; the RosettaCheck website tracks more than 18,800 Intel‑only Mac apps lacking Apple‑silicon builds. MDM platforms like Jamf Pro enable fleet‑wide architecture audits to spot Intel‑only software on managed devices.

Built‑in macOS utilities also help: Activity Monitor’s Kind column shows “Intel” for processes running via Rosetta, Finder’s Get Info lists an app’s Kind as “Application (Intel)” when it depends on Rosetta, and System Information groups all Intel‑only applications together by Kind for review. Additionally, macOS 26.4 and 26.5 display a system warning when an Intel‑only app launches, indicating that support will end in a future release.

Validating Apple‑silicon alternatives

Apple’s guidance is to replace any Intel‑only app with a Universal or Apple‑silicon native version before macOS 28 arrives, and for App Store apps an update check will provide a Universal build if one exists. For software obtained outside the App Store, administrators should visit the developer’s site for a “Universal” or “Apple silicon” label or ask the vendor about a native build plan. When no update path is available, the recommendation is to find an alternative now rather than wait for macOS 28. Some Universal apps still contain Intel‑only helper tools or plug‑ins that will stop functioning after macOS 28, causing loss of functionality even though the main application launches.

Staging the macOS 27 rollout

Enterprise fleets commonly use a 90‑day testing block for macOS 27 (Golden Gate) before broad rollout, providing a window to complete Rosetta‑removal plans. If Rosetta 2 installed under macOS 26 Tahoe, upgrading to macOS 27 Golden Gate will automatically uninstall it; administrators wishing to keep Rosetta must reinstall it after the upgrade. A temporary workaround described by Bradley Chambers uses a Mosyle script that runs softwareupdate –install-rosetta –agree-to-license to reinstall Rosetta on each Mac that joins a macOS 27 Dynamic Device Group, a profile that takes about five minutes to set up and administrators can assign the profile to the group for automatic deployment.

The script is strictly a stop‑gap; the permanent solution is to get Apple‑silicon native versions from vendors. Meanwhile, many menu‑bar utilities from vendors that have not shipped Apple‑silicon builds fail silently under macOS 27, offering no error prompt when they stop working.

Communicating changes

Administrators should consult Apple’s support article HT102527, which states that Rosetta will remain available through the forthcoming macOS 27, with a gaming‑only subset continuing starting with macOS 28. They should also be aware of contradictory Apple pages that describe macOS 27 as the final release with full Rosetta support and another that claims macOS 26 is the last release that runs on Intel Macs and that macOS 27 will be Apple‑silicon only. Because of this uncertainty, administrators should treat macOS 27 as the point at which Intel‑only apps may stop working and verify the current support article before installing the update. Meanwhile, many menu‑bar utilities from vendors that have not shipped Apple‑silicon builds fail silently under macOS 27, offering no error prompt when they stop working.

The operating system is currently in developer beta, with a public beta expected next month and a public launch anticipated in September 2026.