Developers Enable Windows 11 Android Subsystem on Qualcomm Snapdragon X Chips Despite Microsoft's Abandonment
Microsoft's newly launched devices, such as the Surface Pro 7 and Surface Laptop 7, come pre-installed with the Windows 11 Android subsystem (WSA). However, due to these devices being powered by Qualcomm Snapdragon X chips, the Android subsystem is, in reality, unable to function.
Microsoft is aware of this issue but has no plans to rectify it. The reason lies in Microsoft's decision to discontinue the WSA, with a shutdown scheduled for March 5, 2025, eliminating the need for further patches.
The fundamental reason for the failure to run is that the WSA system is mainly compatible with the x86 architecture and the Armv7 series architecture, while the latest Qualcomm Snapdragon X chip uses the Armv8 series architecture, which Microsoft is not compatible with at all.
To address this, developers, including one named Sinclair, have stepped in to offer support. Sinclair has created a custom WSA installation file that circumvents the Armv8 limitation, allowing users to run WSA on Snapdragon X chips.
However, as it stands, this custom image does not support automated deployment. Users are required to modify system files and multiple settings, posing significant challenges for inexperienced, non-professional users.
Additionally, there are some usability issues with the current image, which are expected to be simplified and fixed by developers and the community in the future, allowing ordinary users to directly download, install, and use the custom image.
According to Microsoft's timeline, the WSA will be completely discontinued by March 5 next year. Microsoft may enforce this through cloud policies to prevent usage, but there might be ways to circumvent these restrictions. However, the lack of Microsoft's Android 13 security updates could pose security risks for the WSA.
For users wishing to continue using Android apps on Windows 11, this may not pose a significant problem. Theoretically, as long as malicious apps are avoided, there should be minimal impact on the host machine.