The purpose of writing this article today is to verify with you that a Mac equipped with Apple’s own ARM chip can run Android applications smoothly or not after installing Windows 11. If you don’t have a Mac, don’t rush away when you see this. Of course, I did this experiment not to panic, but for a reason.
As we all know, since Apple used the self-developed chip M1 for MacBook Pro, it has supported macOS to install and run iOS applications. After Windows computers are updated to Windows 11, Microsoft also allows the new system to install and run Android applications through virtual machines.
If the Mac installs Windows 11, it can successfully install and run Android applications by opening a virtual machine through Windows 11. Then it is equivalent to the full compatibility of macOS, iOS, Windows and Android software with only one device. From then on, there is no software that Mac can’t run, it is invincible!
Next, I will take this M1 MacBook Pro as an example to show you whether you can use Android apps on your Mac.
I have to say that installing Windows 11 for Mac is quite simple. Since the Parallels Desktop virtual machine software was updated to 17.1, it has allowed the M1 chip Mac to run Windows 11. And just with the help of the installation assistant that comes with Parallels Desktop, it can help me automatically download and install Windows 11 on this Mac, which can be said to be straightforward in one step.
Since Microsoft has not fully opened the “Android application” function of Windows 11, if your system is the official version, you cannot install the Android subsystem directly from the Microsoft Store. I looked at the settings and found that the Windows 11 that the software installed for me by default is the official home version, so I can only do it by smuggling, which is to download and install the Android subsystem from a third-party channel.
If you want to know how to install Windows Subsystem for Android please check here.
Em… The result shows that the download of the Android subsystem is ok, but when it comes to the installation process, the system reports me an error “This package cannot find the framework”, and the Android subsystem cannot be installed.
I know it’s not that simple. Since the smuggling method doesn’t work, I have to go through official channels.
After downloading the image from Microsoft’s official website, I installed a “Windows 11 on ARM Insider Preview” version of the system on the Mac with the help of Parallels Desktop virtual machine.
Under this system, the Android subsystem was successfully installed successfully, but a new problem follows: when I started the Android subsystem, a pop-up window showed that I needed to start the virtual machine platform.
And I actually turned on the virtual machine function of Windows 11 before running the Android subsystem.
Is it possible that this does not allow me to open another virtual machine in the virtual machine?
That being the case, I tried to install several well-known third-party Android emulators in the Windows 11 system.
The results show that no matter it is NetEase MUMU, Thunderbolt Simulator or Huawei Mobile Application Engine, none of them can run normally in the Windows 11 system. Virtual machine errors occurred in all three software without exception…
After comparing with Windows running on a normal computer, I found that the virtual function of Windows 11 installed through a virtual machine cannot be fully turned on. In other words, its virtual machine function is disabled: Windows 11 in the virtual machine cannot be turned on Hyper-V Platform.
Sure enough, because of the inability to dual virtual machines, it seems that my idea of running Android applications through the Android subsystem after installing the Windows 11 system on the Mac has fallen through. In fact, in the previous so many third-party simulators, there were originally simulators that could be run directly on the Mac, but since the Mac uses Apple’s own ARM chip, these simulators are no longer compatible.
Google launched an Android emulator for Mac with M1 chip last year. It’s just that because it is specially built for Android developers, this Android emulator has barriers to use, and a lot of software cannot be installed in the emulator. It is simply incomparable with the Android subsystem.
In short, although I failed to run Android applications on the Mac in the end, this experiment was not without gain. At least it made me understand one truth deeply, that is, it is currently not possible to install Android applications in the virtual Windows 11 system on Mac.