Menu
When I installed Microsoft Visual Studio 2015 Professional RC, I get the following error:
Microsoft Visual Studio Emulator for Android : The installer failed. Fatal error during installation. Error code: 1603
I am not finding anything related for error code 1603. It appears to be a generic error. Any ideas?
I'm running on Windows 10 Technical Preview. The Visual Studio System Requirements state that Windows Emulators, not Android, require a Hyper-V compatible processor. (my Core 2 does not support that) I don't have Java installed. Is Java required for the VS Android emulator?
UPDATE:
As the comments and answers suggest, the Android Emulator appears to require Hyper-V.
A November 12, 2014 MSDN Blog post titled, "Introducing Visual Studio’s Emulator for Android", under the section, "A peek under the covers" states:
If you are interested in how we built the Visual Studio Emulator for Android, the short answer is that we reused the work of others. Conceptually, an emulator consists of 4 pieces:
- A virtualization technology that XDE needs to load the image before it can RDP to it. Windows has a great virtualization technology called Hyper-V and that is what we used.
(Emphasis added)
XDE is the Windows Phone Emulator Shell that they reused for the Android Emulator.
640
Background: Error 1603 is a general Windows error that means the Sync installer failed to run. Next steps: Ensure you are running the Sync installer as an Admin User in Windows: Right-click the Sync installer and select Run as Administrator.
The error 1603 might occur on a computer system that does not have enough disk space to install the setup and store rollback files. This space is required on the root drive even if the setup may be installed to a different drive. Check that there is enough space on the root drive of the computer system.
A 1603 essentially means “an error occurred” trying to commit the change, causing msiexec.exe to “backout the change”. This type of error is either caused by msi misengineering (most vendor msi are misengineered) or by an “machine specfic issue”.
Chances are that you have either not enabled Hyper-V or your machine does not allow Hyper-V due to hardware limitations
80
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
