Rosetta support to be restricted with the arrival of macOS 27

Changes in macOS 27

A significant technical shift is coming to the Apple ecosystem. The official release of macOS 27, codenamed Golden Gate, will automatically remove Rosetta, the translation layer that allows applications built for Intel processors to run on Apple Silicon chips. While this move was anticipated, it creates a major headache for corporate IT specialists who still rely on legacy, non-native software.

It is important to distinguish between macOS 27 and macOS 28. With the former, Rosetta will be removed automatically, though the system will offer users the option to reinstall it. The real challenge arrives next year with macOS 28, when support for this tool will be discontinued entirely. Therefore, now is the ideal time to conduct a system audit.

Hidden Risks and IT Management

The greatest risks are posed by small background utilities. Testing has shown that some applications simply cease to function without Rosetta, often without providing an error message. This creates uncertainty, as users may not even realise why their work tools are failing.

For IT administrators, the solution lies in temporary scripts. Using Mobile Device Management (MDM) systems, it is possible to deploy an automated script that reinstalls Rosetta on all Macs updated to macOS 27. This is not a long-term solution, but it provides a window of time to contact software vendors and demand versions adapted for Apple Silicon.

Time for developers to take responsibility

Apple Silicon architecture has been on the market since 2020. Developers have had more than five years to make their products fully compatible with the new technology. Any company that still claims to be "working on" an Apple Silicon version is failing to prioritise correctly.

For companies managing large fleets of Macs, it is recommended to conduct thorough system testing over the next 90 days. Before macOS 27 is widely deployed, it is essential to identify applications that still rely on Intel architecture. This process requires both technical intervention and difficult negotiations with software providers.