Something happened while starting a virtual machine: 'Emulator Name' could not initialize. (Virtual machine ID GUID)
Not enough memory in the system to start the virtual machine Emulator Name with ram size 1024 megabytes. (Virtual machine ID GUID)"
This problem can occur on a computer on which you may have previously been able to start the Windows Phone Emulator and also run the same programs when that computer was running Windows 8.
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
To work around this problem in a system that is running many programs that are using lots of memory, try to close those programs and then restart the emulator.
If the emulator still does not start, you can disable the Hyper-V runtime memory monitoring functionality by adding a MemoryReserve registry. To do this, follow these steps:
- Start Registry Editor.
- Locate the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization
- Right-click the Virtualization folder, point to New, and then click DWORD Value.
- Type MemoryReserve, and then press Enter.
- Double-click MemoryReserve, enter 2048 in the Value data box, select the Decimal option, and then click OK.
- Close Registry Editor.
Note You must restart the computer for this registry setting to take effect.
The MemoryReserve registry value determines how much memory is reserved for the hosting system. For example, if this value is set to 2048 (decimal), 2 GB of system memory is reserved for the hosting system. Instances of Windows Phone Emulator will then try to start in the rest of system memory without the system considering program memory usage.
Note This registry setting is shared with Client Hyper-V in Windows 8.1. This setting may interfere with Client Hyper-V scenarios and let virtual machines allocate too much system memory.
Article ID: 2911380 - Last Review: Jan 7, 2014 - Revision: 1