Windows 10: Could not initialize memory, Ran out of memory (0x8007000E) Hyper-V VM error on Windows 11/10

​

If while starting a Hyper-V virtual machine on your Windows 11 or Windows 10 host computer, but you receive the Hyper-V error message Could not initialize memory: Ran out of memory with error code 0x8007000E, then this post is intended to help you with the most suitable solutions to resolve this issue. When you encounter […]

This article Could not initialize memory, Ran out of memory (0x8007000E) Hyper-V VM error on Windows 11/10 first appeared on TheWindowsClub.com.

read more...

 

Windows 10 and Hyper-V dynamic memory


Of course a Hyper-V vm becomes slower if you use dynamic memory with default settings. The Hyper-V will be constantly monitoring the demand and assign the required RAM to the vm.

For the dynamic memory to work you need to assign enough startup memory (#1 in screenshot below), increase the the memory buffer (#2) and memory weight (#3):




A Windows 10 virtual machine needs surprisingly little RAM to function well. Here in the screenshot the memory usage of a Windows 10 vm otherwise idle at the moment, only running Macrium to create a system image. Memory demand only 522 MB but because I have assigned a 35% buffer, it's using 768 MB of the assigned maximum 8 GB:




The buffer is important: When using dynamic memory and the demand suddenly increases for example due a resource heavy application being launched, it takes time for Hyper-V to assign more RAM to the vm. The bigger the buffer, the better the vm reacts to increased demand.

Dynamic memory should only be used when it really is needed, for instance when it is important to have multiple virtual machines running at the same time. Dynamic memory should not be used when installing Windows, it can make the time needed for installation somewhat longer.

Generally speaking a Windows 10 vm with 2 GB of static RAM assigned works faster than the same vm with 512 MB to 4 GB dynamic RAM.

 

Hyper-V Virtual Machines Fail to Start and Initialize after Windows 10 Upgrade from Windows 8.1

yeah those and the ones in the link

still getting the could not start and failed to initialize errors.

I did happen to check the system requirements listed by M$ for hyper-v on windows 10 and it does not list any video requirements or say anything about remoteFX, which makes the error I am seeing confusing.

I also ran the systeminfo command while hyper-v was uninstalled, and the lines that needed to be true in order for hyper-v to work were all yes. my next step I suppose, is to go over to my mom's system and see if it will run hyper-v

 

Problem with Install Hyper-V in Windows 10

Do you have Windows 10 pro? If not then Hyper V will not work.

Do you have the 64 bit version of Windows?

Requirements:

64-bit Processor with Second Level Address Translation (SLAT).

CPU support for VM Monitor Mode Extension (VT-c on Intel CPU's).

Minimum of 4 GB memory. As virtual machines share memory with the Hyper-V host, you will need to provide enough memory to handle the expected virtual workload.

The following items will need to be enabled in the system BIOS:

Virtualization Technology - may have a different label depending on motherboard manufacturer.

Hardware Enforced Data Execution Prevention.

To verify compatibility, open up PowerShell or a command prompt (cmd.exe) and type systeminfo. If all listed Hyper-V requirements have a value of Yes, your system can run the Hyper-V role. If any item returns No, check the requirements listed in this document
and make adjustments where possible.

https://docs.microsoft.com/en-us/virtualization...