I was using Windows 10 LTSB with Visual Studio 2015. After enabled Hyper-V, I installed the standalone Visual Studio Emulator for Android. The Hyper-V functioned well since it's okay to add virtual machine to it.
However, when I was trying to create an android virtual machine in the Visual Studio Emulator for Android Manager, it failed with "Unable to add user to the Hyper-V Administrators group exit code 2220".
After some research I found there's no Hyper-V Administrator group as well as no existence of InitialStorage.xml in ProgramData\Microsoft\Windows\Hyper-V\.
Was my hyper-v installation succeed? Or is there any solution for that?
Thanks everyone.
PS. logging information:
2015/8/15 12:44:53: [Informational] Reinitializing installed profiles.
2015/8/15 12:44:53: [Informational] Installed profiles initialized. Devices: 3 Platforms: 1
2015/8/15 12:44:53: [Informational] Reinitializing installable profiles.
2015/8/15 12:44:53: [Informational] Installable profiles initialized. Devices: 30 Platforms: 4
2015/8/15 12:45:00: [Informational] Waiting to uninstall device...
2015/8/15 12:45:00: [Informational] Uninstalling Device: 4.5" KitKat (4.4) HDPI Phone
2015/8/15 12:45:00: [Informational] Uninstalling virtual machine for 4.5" KitKat (4.4) HDPI Phone
2015/8/15 12:45:01: [Critical] Unable to add user to the Hyper-V Administrators group. Exit code 2220.
What hardware is this? Is your machine SLAT compatible? SLAT is necessary to get Hyper-V up and going.
The emulator’s Hyper-V requirement requires a processor that supports Second Level Address Translation ( SLAT ) enabled hardware. SLAT support was introduced to Hyper-V circa Windows Server 2008 as a mechanism to reduce overhead during address mapping for virtual machines. Hyper-V R2 on Windows 8/10 requires SLAT hardware, and emulators that run on SLAT do as well.
GOT SLAT?
There are two methods to check if you have SLAT hardware. The best route is download the SLATStatusCheck tool from CodePlex ( http://slatstatuscheck.codeplex.com/ ). This tool runs is a WPF 4.5 app which very simply indicates if you have SLAT compatible hardware or not. The tool is open source if you want to see how to do the checks yourself in code.
The other route is CoreInfo.exe, a tool available from SysInternals ( http://technet.microsoft.com/en-us/sysinternals/cc835722.aspx ). When you run CoreInfo.exe with a “-v” parameter, you will have a “*” next to the “EPT Supports Intel extended page tables (SLAT)” entry. Note coreinfo must be run in an admin level command prompt.
CoreInfo can sometimes lie! If you’ve already got Hyper-V running, it may erroneously return a “false negative” on the slat capabilities. CoreInfo even tells you this in a screen entry (which I overlooked) – “Note: CoreInfo must be executed on a system without a hypervisor running for accurate results”. Note that SLATStatusCheck returns the correct results regardless of whether Hyper-V is running or not.
MORE RESOURCES
- Second Level Address Translation Benefits in Hyper-V R2 -
http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/general/second-level-address-translation-benefits-hyper-v-r2.html
- How to check if the Processor (CPU) supports the function SLAT?
http://www.softwaretipspalace.com/how-to/260-check-slat-support-on-intel-amd-processors-cpu.html
- SLAT Status Check Tool - http://slatstatuscheck.codeplex.com/
CoreInfo download from SysInternals -
http://technet.microsoft.com/en-us/sysinternals/cc835722.aspx
Taken (mostly) from my blog post at http://blogs.msdn.com/b/devfish/archive/2012/11/06/are-you-slat-compatible-wp8-sdk-tip-01.aspx .
The problem may be related to the version of Windows you have or started with. You have to start with a Pro install. Upgrading from Home to Pro is incomplete.
I recently discovered if you start with the MSDN Windows 10 (Multiple Editions), Version 1607 and install it, it defaults to the Home edition. Once you put in the Pro Key to upgrade it, it becomes "Pro"; but not really. The "Users And Group" snap-in will not work, you are stuck with the security model in "Home". Once you have upgraded, you need to Reset the installation -- but do not delete/format the partition or you get a "Home" edition again.
The MSDN version does not allow you to select Home/Pro and there is no Pro version to download. Very frustrating. MS has known about this for almost a year.
Some have postulated it is because they removed a Default group definition file that included Hyper-V Administrators, but I created the group in "Home" using a Net command and it still does not work.
