With the newer release of bluestack I got to know Android support for Pie. But when I when I tried to create a new instance for pie support it show me this issue Pie(64) version is not supported on this operating system. Please provide me solution, It will be very helpful
First of all check few things here.
If BlueStacks 5 Nougat 32-bit or Nougat 64-bit is already installed on your PC, then you can create a Pie 64-bit (Beta) instance on it using the Multi-Instance Manager.
Windows 11 will not support of 64-bit Pie.
Your bluestacks version should be 5.2.100 or above to use this feature.
For more details just check official doc
Hypervisor disabling has a lot more to do with than just the "Hyper V" in the 'turn windows features on or off'. Make sure to tick off at least a couple of more tick boxes detailed here in the official support page. These were the "Virtual machine platform" and "Windows hypervisor platform" for me. Once the Hypervisor support is completely removed, Pie 64 is able to be installed, instantiated, and run.
I had the same problem. I solved it by disabling Hyper V using an .exe file, which you can download from the official Bluestacks website at the link
I have got an AMD Ryzen CPU and Android emulator doesn't work.
It doesn't start the emulator becouse the CPU doesn't support the x86 emulator
Update - My previous answer is no longer true. Google has added AMD and Hyper-V support into their latest beta. Thanks to ReverseCold for letting me know. Please see his answer below.
Update 2 - I had to set this up today. To save some googling, here is the powershell command to enable Hyper-V. Pulled from Microsoft's Docs
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
Make sure to run powershell as an administrator.
Update 3 - Turns out there's a difference between Windows Hypervisor Platform and Hyper-V. You'll need to enable the first one for Android emulation to work. Just click start and type Turn Windows features on or off until you see the control panel option of the same name. Then enable the feature from the menu that pops up after clicking that.
According to This answer, AMD virtualization for Android is only supported on Linux. If Ryzen becomes hugely popular, maybe they'll write one for Windows, but I won't be holding my breath.
The latest beta has support for Ryzen. Source
The following is from the google blog post: If you have an AMD processor in your computer you need the following setup requirements to be in place:
AMD Processor - Recommended: AMD® Ryzen™ processors
Android Studio 3.2 Beta or higher - download via Android Studio Preview page
Android Emulator v27.3.8+ - download via Android Studio SDK Manager
x86 Android Virtual Device (AVD) - Create AVD
Windows 10 with April 2018 Update
Enable via Windows Features: "Windows Hypervisor Platform"
Here is a list of ways to get around it:
genymotion personal is free but you need to register
Visual studio android emulator is also free and is fast. I had issues with it disconnecting on android studio
Physical device. You will have a hard time trying to see the sqlite database if it isn't rooted.
With the physical device you can download Vysor on play store and install the extension on google chrome. Then you can have the physical device on your monitor.
I managed to run the Android emulator on Windows 10 (AMD Ryzen 5 2600) after installing the KB4505903 update.
In my case, only two configuration requirements were needed:
Windows 10 May 2019 Update (1903), OS Build 18362.267
Enable via Windows Features: "Windows Hypervisor Platform" ("Платформа низкоуровневой оболочки Windows")
Gennymotion should work for amd users. I emailed them and they said yes it should work.
check here to see their specific requirements.
Yeah I have AMD CPU somehow it works now.
I don't have x86 installed by HAXM and it still works strange.
Gigabyte CPU/AMD Ryzen 7 ->
MIT Settings -> frequency settings -> advanced -> have SVM enabled
Go to windows turn on and off feature
-> if you're using windows home, not pro edition, then you need to find "windows Hypervision platform" then check mark it.
Create a new AVD virtual device, the newest version may or may not work. You have to do trial and error with different API versions like 25, 26, or newest one.
Somehow on SDK Tools, i don't have x86 intel HAXM installed, and it works fine? Does anyone know why it works without intel x86 on my AMD CPU? When i uninstalled it and did everything else again, it finally worked... Strange..
If you have an AMD processor in your computer you need the following setup requirements to be in place:
AMD Processor - Recommended: AMD® Ryzen™ processors
Android Studio 3.2 Beta or higher - download via Android Studio
Preview page
Android Emulator v27.3.8+ - download via Android Studio SDK Manager
x86 Android Virtual Device (AVD) - Create AVD
Windows 10 with April 2018 Update
Enable via Windows Features: "Windows Hypervisor Platform"
**Note:There is Hyper-V features... You should enable Windows Hypervisor Platform not Hyper-V. Windows Hypervisor Platform is at the bottom of features **
I know I am a bit late to answer this but after a few hours of research and verification, here is what I have found. As of July 2018, if you run AMD Ryzen CPU/APU, you should be able to run Android emulator. (see link). It does not work on my old AMD Phenom II X6 because the CPU needs to support SSSE3 and SSE4.1 features. I guess it's time for me to upgrade :) The toast message I received was "Emulator: emulator: WARNING: Host CPU is missing the following feature(s) required for x86_64 emulation: SSSE3 SSE4.1"
You can follow the instructions in the link above, although I also had to do these in my Android Studio.
In the Tools menu > Android SDK > SDK Tools (tab) > Uncheck the option "Intel x86 Emulator Eccelerator (HAXM installer)".
Go to Tools menu > AVD Manager > Ceate a new virtual device (choose an image for the x86-64 platform)
A related question was asked here - Ryzen 3 with VS android emulator - I've responded there and so thought to cross-link in case others missed it.
This might help you:
https://www.reddit.com/r/Amd/comments/cgpaq4/ryzen_android_emulator_whpx_fix_for_windows/
The issue seems to be to do with Windows and has been fixed in the insider builds - you can get it working by following the link above, and without having to become a Windows Insider.
--
Unfortunately After turning on Windows Hypervisor Platform I can not change the resolution window. It was fixed at non resolution recommended. I do not like at all. Here is my computer's information
I should install VS Android Emulator but I can't. Because VS Android Emulator doesn't show in installer. I use Macbook Pro that installed Windows 10 Education and it support VT. Also I has installed Hyper-V and I can start virtual machine. I has tried for VS 2015 Community and Enterprise but it hasn't emulator. What can I do to install VS Android Emulator and What is system requirements?
Edit:
I upgrade Windows to Enterprise edition and Android Emulator is working. I think Windows 10 Education Edition is not fine for Hyper-V.
The VS Emulator for Android requires Hyper-V, which is only available in certain versions of Windows 10. Windows 10 Home and Education editions do not have Hyper-V, so you'll need Windows 10 Pro or greater to use the emulator.
Try installing the emulator by itself from this link:
https://www.visualstudio.com/en-us/features/msft-android-emulator-vs.aspx
The VS Emulator for Android does not work on Windows 10 (for me).
My advice is do not worry because there are much better options. I use Genemotion & VirtualBox with Hyper-V disabled and it is great. Also, the Google Android emulator with HAXM is great.
Google emulators include two versions (with and without Google APIs). And I've been able to successfully install Google Play services in Genemotion on 4.4.4 hosts.
Therefore, either the Google or Genemotion options are extremely more useful than Microsoft's VS Emulator for Android on Hyper-V (even if it worked on Windows 10).
I have a problem with the Visual Studio 2015 RC Emulator for Android. The emulator is not starting when I'm starting debugging (F5) nor from "Tools > Visual Studio Emulator for Android...". The process is stuck on "Preparing virtual machine" and there is a "Xde.exe" process with 0% CPU usage in Task Manager. This happens for all virtual machines. Previous emulators (pre-RC) were working just fine.
The necessery APIs (19 and 21) are installed according to SDK manager.
I have tried re-installing Visual Studio and also repairing it but it didn't help.
How can I fix that?
Update:
Here are logs: http://pastebin.com/xgyTNkJ9 . The [Critical] The operation was canceled. lines are self explenatory. [Critical] Could not launch 'VS Emulator 5.5" KitKat (4.4) HDPI Phone' device.occured when I killed xde.exe in Task manager.
What's weird is a fact that when I import VHD file from %localappdata%\Microsoft\VisualStudioEmulator\Android\Containers\Local\Devices into Hyper-V manager it works just fine and I can even start it and use it. Unfortunately, I still can't debug application from Visual Studio that way.
Update 2:
So I've reinstalled the Windows on my notebook and same thing happens after installing Visual Studio 2015 RC. So two different hardware, one clean Windows installation and same effect.
This might be a duplicate of Visual studio (2015) emulator for android not working - XDE.exe - Exit Code 3.
I was having the same issue as yourself and this was solved by following the steps provided in this answer: https://stackoverflow.com/a/31698124/1010492.
The key for me was to disable the Network Sharing I had set on my Wi-fi adapter.
You are probably not a member of the Hyper-V Admins group on the computer. Do this:
Open Control Panel > Administrative Tools > Computer Management.
Expand "Local Users and Groups" and then click on "Groups."
Double click on "Hyper-V Administrators" group.
Click "Add" and add your username to the group.
If the group doesn't exist, you can create it using the PowerShell script in this blog post: http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/09/28/creating-a-hyper-v-administrators-local-group-through-powershell.aspx
It may be that you do not have enough memory available to start the Hyper-V VM. If you go to Hyper-V Manager and attempt to start the emulator image, you'll be able to see if it starts at all or if you don't have enough free RAM on the machine.
I came up with a very genuine solution that can fulfill your basic need of running the emulator. All you need to do is follow these steps:
Sign in to https://www.genymotion.com/account/login/
Download Genymotion from there.
First Download and run the Emulator of your own choice from Genymotion.
[Start the Emulator From Start Button][2]
Then Keep it running and Open the Visual Studio.
Open your Solution,and while your Genymotion Emulator Running,You will see that at Play option,you will be having new Emulator device which will be Genymotion Device.
Deploy using that device.
Hurray!! Your Solution is Successful.
I have an issue with my HAXM installation. Here is the thing. I got this error every single time I tried to install HAXM for my computer:
Problem is, that my computer supports Virtualization Technology (see pic below). Any idea how to fix this issue?
Just follows these steps:
Go to Control Panel → Program and Feature.
Click on Turn Window Features on and off. A window opens.
Uncheck Hyper-V and Windows Hypervisor Platform options and restart your system.
Now, you can Start HAXM installation without any error.
Hello and welcome to the 3rd installment of the infamous Android Emulator on Windows saga. Despite the combined 3 trillion dollar market cap of Microsoft and Google, this remains to be a problem harder than going to the moon.
Below is the somewhat comprehensive list for Windows (so far as of circa 11/2022)
First make sure you have the latest version of Windows. As of writing, this is Windows 11 22H2 with all updates installed. If you have an older version of Windows, you'll have to try each one of the below, with possibly different combinations. Otherwise follow from the top until your issue is solved. It is ordered from the easiest/most likely culprit on a decent Windows machine, to the most unlikely cause.
Note that if you're doing below on a corporate machine, some of the below actions may be blocked by your admin, and/or flag your machine as suspicious activity as some actions intentionally turns off some security features. Depending on your situation, you may want to give a heads-up to your IT/security team.
If your Windows device has Bitlocker enabled on your boot drive contact your IT admin first. Messing with virtualization and boot configuration may trigger bitlocker prompts upon reboot. If you're working from home,this may mean taking your laptop to the office to get it unlocked by IT, as Windows may refuse to boot without unlocking BitLocker.
To find what is blocking the emulator launch, the surefire way is to open a terminal (cmd or powershell) and launch to from there as below.
First kill any existing emulator.exe instances, adb.exe instances, java.exe instances, qemu instances, android studio instances. Check in task manager to be sure.
The adb relaunches itself so its ok be running. But make sure android studio is not running. It seems to lock files/cache and not flush emulator configs, that may crash the emulator at launch, without any useful logs.
in a terminal
cd your_sdk_location\emulator
emulator.exe -list-avds
this will list what AVDs you have. Find the one you want
emulator.exe -avd your_avd_name -verbose
This will have a long log, and will have some information on what the failure is. If you see a VM heap size being outside of limits, it may say that it it automatically set to lowest or highest value. This is a lie. Open emulator settings and set it to within the limits manually, usually 550MB works. Launch android studio and edit the emulator instance to be within this limit, then close android studio, then wait about 30 seconds before attempting to launch the emulator. For all attempts of launching the emulator below, do not rely on android studio, launch from command line instead.
Note that the emulator editor UI in android studio can corrupt the config at times. If this happens, I don't know where this is stored, so you may have to delete and re-create the AVD. If this doesn't work, do not change and configs during AVD creation, then launch it from command line.
If the emulator doesn't launch, no useful failure logs, yet the emulator.exe exits after a few minutes, you may have android studio running. Exit/Kill Android studio, wait a minute or so and try again. If still fails, reboot.
Have an Antivirus (other than Microsoft Defender)?
Disable it
Reboot and try to launch the emulator
Disable Hypervisor Boot
open an admin terminal (cmd or powershell)
run bcdedit /set hypervisorlaunchtype off
try to launch the emulator. If still broken, try rebooting.
If your failure is due to install of HAXM/AMD hypervisor driver failing
run systeminfo in a terminal
at the end under Hyper-V Requirements: if it says A hypervisor has been detected this means emulator cannot launch virtualization.
Open Start > Windows Security > Device Security > Core isolation
turn off Core Isolation (previously known as Memory Integrity/Isolated User Mode)
Open Turn Windows features on or off and disable
Hyper-V Platform
Hyper-V Management Tools
Windows Hypervisor Platform
You can enable them after HAXM/AMD Driver install
on an admin prompt run bcdedit /set hypervisorlaunchtype off
reboot
try to launch the emulator
Check BIOS
go into BIOS/UEFI setup and look for settings like
VT-x
VT-d
Virtualization Technology
Hardware Virtualization
Make sure these settings are enabled
try to launch the emulator
Uninstall Docker Desktop
Some users have reported that uninstalling Docker Desktop fixed their issue.
It is unclear as to why docker desktop interferes with haxm installation. The reason is probably that it supports running docker images via a Hyper-V backend, and disabling this feature does not remove the hypervisor completely.
Go to Settings -> Add or remove programs, and uninstall docker desktop
reboot
try to launch the emulator
Nothing works
You shouldn't get here, since Android emulator can now run alongside with Hyper-V if you have 'Windows Hypervisor Platform' enabled.
If nothing above works, as a last resort you can try running Android in a Hyper-V VM and get ADB to connect to it. (Not a solution, but a workaround)
You can also run android using a third-party emulator like Genimotion.
¯\(ツ)/¯
Debug on a physical device
You can also use Wifi debugging via adb pair ip:port and adb connect ip:port commands.
or get a Macbook
After few days of googling I found, that problem was caused by hyperthreading (or hyper - v). I decided to edit my boot.ini file with option to start up windows with hyperthreading turned off.
I followed this tutorial and now everything works perfect
chances are that you have windows 8 with hyper-v installed? if yes remove hyper-v and your problem goes away!
First of all make sure you enabled Virtualization Technology in your BIOS. After restarting your computer press F1-F12 on your keyboard and find this option.
Make sure you disabled Hyper-V in your Windows 7/Windows 8. You can turn it off in Control Panel -> Programs -> Windows functions
You can try to disable your antivirus program for the whole installation process. Remember to restore all antivirus services after installing HAXM.
Some people recommend cold boot which is:
Disabling Virtualization in your BIOS
Restart computer and turn it off
Enable VT in your BIOS
Restart computer, turn it off
It's likely that now might be allowed to install HAXM
Unfortunately this step didn't work for me
Last but not least: try this workaround patch released by Intel.
http://software.intel.com/en-us/blogs/2013/04/25/workaround-patch-for-haxm-installation-error-failed-to-configure-driver-unknown
All you have to do is to download the package, unzip it, put it together with HAXM installator file and run .cmd file included in the package - remember, start it as an Administrator.
I had a lot of problems with installing HAXM and only the last step helped me.
In the "Turn Windows features on or off" window, un-check Hyper-V and also ensure that Windows Hypervisor Platform is unchecked. Windows Hypervisor Platform being enabled can also block the installation of the Intel HaxM
Maybe VT-X is not enabled in your BIOS.
See Intel HAXM documentation here: http://software.intel.com/en-us/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-windows
Intel VT-x not enabled
In some cases, Intel VT-x may be disabled in the system BIOS and must
be enabled within the BIOS setup utility. To access the BIOS setup
utility, a key must be pressed during the computer’s boot sequence.
This key is dependent on which BIOS is used but it is typically the
F2, Delete, or Esc key. Within the BIOS setup utility, Intel VT may be
identified by the terms "VT", "Virtualization Technology", or "VT-d."
Make sure to enable all of the Virtualization features.
Anti-virus software may interfere with the HAXM installation.
After trying to figure out what went wrong for a few hours I found a strange solution - uninstalling my anti-virus software , installing HAXM (which worked) and then re-installing the anti-virus software (Avast in my case but it could happen with other anti-virus programs as well.
The full check I went through to get this running is:
Check the 'Virtualization' and vt-X feature in the BIOS.
Verifying Hyper-V is not installed.
Checking weather vt-X is enabled in windows with the Intel tool and MS tool (mentioned in previous posts in this thread).
Disabling the anti-virus which didn't help.
Uninstalling the anti-virus (which solved the problem for me).
In Windows 10, Windows Defender has a feature of core isolation which uses virtualisation technology that will also interupt in working of HAXM. Disable it and try again. In my case disabling it solved my issue.
If you have an AMD Ryzen processor in your computer you need the following setup requirements to be in place:
AMD Processor - Recommended: AMD® Ryzen™ processors
Android Studio 3.2 Beta or higher - download via Android Studio
Preview page
Android Emulator v27.3.8+ - download via Android Studio SDK Manager
x86 Android Virtual Device (AVD) - Create AVD
Windows 10 with April 2018 Update
Enable via Windows Features: "Windows Hypervisor Platform"
Note:There is Hyper-V features... You should enable Windows Hypervisor Platform not Hyper-V.
Windows Hypervisor Platform is at the bottom
After conditions done avd x86 work without haxm install
Reference
In many cases some antivirus also start HyperV with window start and does not allow HAXM to install.
I faced this issue because of AVAST antivirus.
So I uninstalled AVAST, then HAXM installed properly after restart.
Then I re-installed AVAST.
So its just a check while installing as now even with AVAST installed back, HAXM works properly with virtual box and android emulators.
After I installed Visual Studio 2013 Update 2, Visual Studio notified me about a Windows Phone emulator update, which I installed (it was really a new component, not an update). It turned out this enabled Hyper-V, which broke HAXM.
The solution was to uninstall the emulator from Programs and Features and to turn off Hyper-V from Windows Features (search for "Windows Features" and click "Turn Windows features on or off").
If you dont find Hyper-V option in control panel as said in other responses here, try entering BIOS setup (restarting and pressing F-12 or ESC or other depending on your PC) and enabling Virtualization, located probably in CPU options.
I'm running Windows 10 and had this problem after I changed my SSD, I fixed it by disabling the VT support on Bios. I got a different error after I ran the installer. I rebooted and enabled VT support again and voila, working now.
If any of the answers doesn't work just remove Android Emulator and reinstall it again. and after that try installing Intel Haxm.
If none of the answers worked out for you, try this,
Hyper-V might not be disabled
If you have windows 10 features such as Device Guard and Credential Guard is enabled, it can prevent Hyper-V from being completely disabled.
The Device Guard and Credential Guard hardware readiness tool released by Microsoft can disable the said Windows 10 features along with Hyper-V:
Download it here, https://www.microsoft.com/en-us/download/details.aspx?id=53337
Download the latest version of the Device Guard and Credential Guard hardware readiness tool.
Unzip
Open the Command Prompt using Run as administrator
#powershell -ExecutionPolicy RemoteSigned -Command "X:\path\to\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1 -Disable"
Reboot.
I already tried all of the possible solutions on stackoverflow and didn't work
What I tried:
Disable Hyper-V in windows feature
Disable Hyper-V with command
Disable Device Guard
etc etc
Above solution still give me information about Hyper-V in System Information and the HAXM still failed to install.
But finally I found the solution, you have to disable Hyper-V from System Configuration:
Open System Configuration
Click Service tab
Uncheck all of Hyper-V related
Check System Information then Hyper-V is off now
Fix the error. follow the following steps
Turn off Hyper-V and Windows Hypervisor Platform
Goto RegEdit "Windows Defender is blocking HAXM."
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard
Set the key EnableVirtualizationBasedSecurity to '0'
if Key is not available create a key
Re-boot the machine
Install the intelhaxm-android.exe