AI News Feed
Market watch
Products & Applications

Apple IT admin urges Rosetta audit ahead of macOS 27 removal

9to5Mac column: macOS 27 removes Rosetta; some Intel-only tools fail silently, prompting a script workaround.

According to the column, macOS 27 (Golden Gate) automatically removes Rosetta, and macOS 28 will no longer support it. For traditional apps, macOS 27 will prompt users to reinstall Rosetta through a GUI prompt. Chambers said the more troubling cases are menu bar utilities from vendors that have not shipped native Apple Silicon builds; in his testing this summer, those tools failed without an error prompt. He said that makes auditing a fleet before macOS 27 rolls out more important than it might appear.

Chambers described his short-term fix in Mosyle, the device management system used in the column. He creates a script profile named for the task and enters the command softwareupdate --install-rosetta --agree-to-license. Under Execution Settings, he selects a trigger, assigns the profile to his macOS 27 Dynamic Device Group and saves it. When a device appears in that group, Mosyle automatically pushes the script, aiming to install Rosetta before the user runs into a problem. He called it a temporary measure that buys time while he works on the real solution: getting vendors to ship native builds.

Chambers was direct about those vendors. He wrote that Apple Silicon shipped in late 2020 and it is now late 2026. Any vendor still telling customers that a native Apple Silicon build is 'on the roadmap' before Rosetta stops working in macOS 28 has had five-plus years to solve the problem and has chosen not to, he wrote. He said the issue is not a resource problem or a technical challenge at this point but a prioritization choice that falls on the IT teams managing the software. Even if those vendors ship Apple Silicon-native versions before macOS 28, he wrote, the delay makes him question their commitment to macOS.

He advised IT admins who have not audited their fleets for Rosetta-dependent software to do it now, while there is still time to push a script workaround or hold harder vendor conversations before users encounter problems. Most enterprise fleets are likely doing a 90-day block on Golden Gate for final testing and QA, he wrote. The Mosyle script fix takes about five minutes to set up, while vendor conversations and migrations will take longer, according to the column.