From cf809480e8247c33fa82200787f71c1b19a6aa8a Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 19 Sep 2025 19:41:55 +0000 Subject: [PATCH 1/2] Initial plan From 200e3992bb8c278642336c64259021aa67855d81 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 19 Sep 2025 19:48:10 +0000 Subject: [PATCH 2/2] Add Windows ARM device limitations documentation for Android emulators Co-authored-by: jfversluis <939291+jfversluis@users.noreply.github.com> --- docs/android/emulator/hardware-acceleration.md | 16 ++++++++++++++++ docs/android/emulator/troubleshooting.md | 17 +++++++++++++++++ docs/get-started/installation.md | 3 +++ 3 files changed, 36 insertions(+) diff --git a/docs/android/emulator/hardware-acceleration.md b/docs/android/emulator/hardware-acceleration.md index 2be5c98a3..021098a46 100644 --- a/docs/android/emulator/hardware-acceleration.md +++ b/docs/android/emulator/hardware-acceleration.md @@ -31,6 +31,22 @@ For the best experience on Windows, it's recommended you use WHPX to accelerate > [!IMPORTANT] > A Virtual Machine (VM) accelerated emulator can run inside another VM, including Microsoft Dev Box, provided that nested virtualization is enabled in the VM. +### Windows ARM device limitations + +The Android emulator currently requires x64 processor architecture and is **not supported on Windows ARM devices**. This limitation affects devices such as: + +- Surface Pro X +- Surface Pro 9 (5G/ARM variant) +- Other Windows devices with ARM64 processors (Snapdragon, etc.) + +If you're using a Windows ARM device, consider the following alternatives: + +- Use a physical Android device for testing via USB debugging. For more information, see [Set up Android device for debugging](~/android/device/setup.md). +- Use cloud-based testing services or remote development environments with x64 architecture. +- Consider using Windows Subsystem for Android (WSA) if available, though this has different limitations and capabilities compared to the Android emulator. + +For the latest information about Android emulator requirements, see [Android Emulator requirements](https://developer.android.com/studio/run/emulator#requirements) on developer.android.com. + For information about launching and debugging with the Android emulator, see [Debugging on the Android Emulator](debug-on-emulator.md). ## Accelerate with Hyper-V diff --git a/docs/android/emulator/troubleshooting.md b/docs/android/emulator/troubleshooting.md index da5bc4604..654ae464c 100644 --- a/docs/android/emulator/troubleshooting.md +++ b/docs/android/emulator/troubleshooting.md @@ -60,6 +60,7 @@ Performance issues are typically caused by one of the following problems: - The emulator is running without hardware acceleration. - The virtual device running in the emulator using an Arm-based image. +- You're trying to run the emulator on a Windows ARM device (not supported). The following sections cover these scenarios in more detail. @@ -71,6 +72,22 @@ When you start a virtual device, and you don't have hardware acceleration enable To fix this error, follow the troubleshooting steps in the [Hardware acceleration issues](#hardware-acceleration-issues) section. +### Windows ARM device compatibility + +The Android emulator is **not supported on Windows ARM devices** and will not run on devices with ARM64 processors such as: + +- Surface Pro X +- Surface Pro 9 (5G/ARM variant) +- Other Windows devices with Snapdragon or ARM-based processors + +If you're using a Windows ARM device and encounter emulator startup issues or performance problems, this is likely due to the architecture incompatibility. The Android emulator requires x64 processor architecture. + +**Alternatives for Windows ARM devices:** + +- Use a physical Android device connected via USB for debugging. For setup instructions, see [Set up Android device for debugging](~/android/device/setup.md). +- Use cloud-based development environments or remote machines with x64 architecture. +- Consider Windows Subsystem for Android (WSA) if available in your region, though it has different capabilities and limitations. + ## Hardware acceleration issues When using hardware acceleration, you may run into configuration problems or conflicts with other software on your computer. The first step in troubleshooting is verifying that hardware acceleration is enabled. You can use the Android's SDK to check this setting. Open a command prompt and entering the following command: diff --git a/docs/get-started/installation.md b/docs/get-started/installation.md index 5c7241671..616322243 100644 --- a/docs/get-started/installation.md +++ b/docs/get-started/installation.md @@ -295,6 +295,9 @@ To download and install an Android emulator on which to run your apps: For more information about the `avdmanager` command, see [avdmanager](https://developer.android.com/tools/avdmanager) on developer.android.com. + > [!IMPORTANT] + > **Windows ARM devices**: The Android emulator requires x64 architecture and is not supported on Windows ARM devices (such as Surface Pro X). If you're using a Windows ARM device, consider using a physical Android device for testing instead. For more information, see [Set up Android device for debugging](~/android/device/setup.md). + ### iOS and macOS To set up your Mac for .NET MAUI development on iOS and Mac Catalyst with Visual Studio Code: