Apple just dropped the first beta of macOS 27 Golden Gate. Hours later, the Asahi Linux project issued a stark warning. Don’t upgrade. The new software blinds the boot picker to Linux partitions on Apple Silicon hardware.
Short and simple. The change hides valid boot volumes. Asahi Linux installations vanish from the Startup Disk tool and the boot menu. Users can’t switch to their Linux setup. Yet the data stays intact. Partitions remain on disk.
The Asahi team traced the problem to modifications in how macOS 27 detects valid OS boot volumes. The Register reported the details on June 10, 2026. Apple’s boot picker and Startup Disk app no longer recognize the Asahi volumes created by the project’s custom installer. Result? No easy way to boot Linux.
But there’s more. The issue appears tied to broader shifts in macOS 27. Apple ended support for Intel Macs with this release. Some observers speculate the boot code cleanup exposed or introduced this side effect. AppleInsider tested the selector and found similar problems even when running older macOS versions from separate volumes. The bug hits multi-OS setups hard.
Developer Response and Workarounds
Asahi Linux didn’t waste time. They updated their installer to block runs on the macOS 27 beta. The message is direct. It prints a warning and exits. The team also filed a bug report with Apple. Feedback ID FB22994760. They view the behavior as unintended. Yet they prepare for the possibility it isn’t.
Advice for users lands blunt. Install a secondary copy of macOS 26 before touching the beta. Or place macOS 27 on its own volume. Keep at least one stable macOS install available. Set it as the default boot option. The project made this clear in their public statement. “We will not support users who have installed the macOS 27 beta without ensuring at least one stable version of macOS is installed.”
Those who upgraded already face a different reality. Panic isn’t necessary. “If you have already upgraded to the beta and noticed that your Asahi partition has disappeared, do not stress. Your Asahi partition is still there, and you have not lost any data.” The quote comes straight from the Asahi Linux team via Phoronix coverage published June 9, 2026.
Recovery paths exist. Hold the power button during startup to force the full boot menu. Some Reddit users in the r/AsahiLinux community reported success after repeated attempts. The partition can reappear. Still, the experience frustrates. Dual-boot users on M1 through M4 chips lose convenient switching until Apple or Asahi ships a fix.
This episode highlights the fragile balance Asahi Linux maintains. The project ports Linux to Apple Silicon through reverse engineering. It delivers GPU acceleration, hardware support, and a polished Fedora Asahi Remix. Version 44 arrived in April. Momentum had built despite internal changes. A leadership transition hit the project earlier in 2026. Yet development pressed forward.
Apple’s hardware presents unique obstacles. Custom boot firmware. Secure boot chains. Hardware tied tightly to macOS. Asahi’s solution relies on specific volume layouts and boot objects that Apple’s tools must recognize. When those detection rules shift, compatibility breaks. The macOS 27 change strikes exactly there.
Industry watchers note the timing. WWDC 2026 introduced Golden Gate with emphasis on Apple Intelligence features and platform consistency. Boot loader modifications rarely make headlines. They matter deeply to users who run alternative operating systems. Developers who test software across platforms. Security researchers who prefer Linux toolchains on Apple hardware.
So far Apple offers no public comment. The bug report sits with them. Beta one often carries rough edges. Later builds could restore visibility. Or the change might reflect a deliberate tightening of the boot process now that Intel Macs exit the picture. Either way, Asahi Linux must adapt.
The project has adapted before. Early days required months of work for basic boot. GPU drivers came later through heroic reverse engineering. Each macOS update brings new variables. This time the disruption arrived fast. Within days of the beta drop, documentation, installers, and community posts updated.
Longer term questions linger. Will Apple provide stable APIs for third-party boot loaders? Or does the company prefer a single-OS world on its silicon? Asahi Linux proves Linux runs well on these machines. Performance in some workloads exceeds expectations. Yet reliance on undocumented behaviors and precise volume formatting creates recurring risk.
Users who rely on Asahi for development, testing, or daily drivers now weigh options. Stick with macOS 26 and wait. Maintain multiple volumes. Explore virtual machines, though they lack the native performance Asahi delivers. Or accept temporary Linux downtime while the bug gets addressed.
The situation underscores a larger truth. Hardware vendors control the platform. Open source projects borrow access through ingenuity and persistence. When vendor code moves, the borrowers scramble to catch up. Asahi Linux has scrambled many times. They will again.
Recent discussions on X echoed the warnings. Developers urged patience for beta two or official fixes. Community posts on Reddit’s Asahi forum filled with screenshots of vanished partitions and recovery steps. The consensus holds. Test the beta on non-critical systems. Keep a fallback macOS ready. The Linux side isn’t gone. It simply waits out of sight for now.
WebProNews is an iEntry Publication