Share via

Cannot allocate needed amount of RAM to Hyper-V machine, although host has more than enough free memory available

Anonymous
2025-01-03T16:42:31+00:00

Windows 10 version 1809 x64 running on the host PC; while attempting to start a VM in Hyper-V that has 16GB starting RAM, and the host has 112GB free, the VM cannot start producing a 0x800705AA error message linked to inability to allocate those 16GB of RAM (!). What gives? TIA!

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments
Accepted answer
  1. Anonymous
    2025-01-16T07:01:41+00:00

    In the screenshot the committed memory is close to the limit so you may need to check to see which application is using the committed memory. Open Task Manager, switch to Details, right click on the headers and select the Commit Size column.

    1 person found this answer helpful.
    0 comments

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-01-06T04:46:53+00:00

    Hi,

    Run services.msc as administrator, right-click on Hyper-V Virtual Machine Management service (VMMS) and select Restart.

    Open VM Settings in Hyper-V Manager, select Memory and uncheck Enable Dynamic Memory, then try restarting the VM again.

    If the issue persists, you may have to restart the computer.

    0 comments
  2. Anonymous
    2025-01-10T12:58:27+00:00

    Thank you for your response, Ian_Xue. Since I needed to run my VM at the time of the incident reported, I had to reboot anyhow (I wasn't aware at the time of the suggested alternative troubleshooting steps). Since that reboot 6 days ago, I've run my VMs multiple times with no memory-allocation issues as the one discussed herein. In case I bump into this in the future, I'll also check your other suggestions and I'll report accordingly.

    0 comments
  3. Anonymous
    2025-01-14T07:35:54+00:00

    Eventually the issue reappeared (with 88,7GB available and just 16GB needed for the VM); I tried the suggested steps but nothing worked and I again had to reboot. But the thing is that I don't want to have to reboot my PC (I've got other things running that I can't interrupt), while at the same time having so much RAM available, just to make a VM work.

    0 comments
  4. Anonymous
    2025-02-03T19:09:16+00:00

    Okay, thanks to your observation I was able to eventually pinpoint the culprit that's using so much committed memory (e.g. now it was a whole 86 GB!): it is a program from Dell, supposedly a diagnostic one under Dell\DTP\DiagnosticsSubAgent — namely memory.exe. 🙄

    0 comments