Running into a problem with a Server 2016 machine being used a DC and file server for our small office. Hardware is a SuperMicro SuperServer 1029P-MTR. 2 Xeon Silver 4110 8 core processors, 32GB Ram. We have Server Core installed as a hypervisor and then an instance of a full Server 2016 (64 bit) installed as a VM. It's the only running VM on the server at the moment. I had previously allocated 16GB of RAM to it, and we were having some speed issues that I started investigating.

In Resource Monitor, I discovered that of the 16GB allocated, 11GB was "Hardware Reserved", leaving only 5GB for everything else. I changed the VM settings to allow 24GB to the VM. The Resource Monitor now shows 19GB as "Hardware Reserved", leaving the same 5GB available. The VM sees the full 24GB as "Installed Memory".

(The rest of the VM memory settings are: RAM - 24000MB, Enable Dynamic memory checked, minimum RAM 512MB, maximum RAM 1048576 MB, Memory Buffer 20%, Memory Weight slider set to highest setting)

Following some hints here, I've looked at Device Manager to see what hardware had memory allocated. It looks like 8GB (!) is allocated to "Microsoft Hyper-V Video" and another 4MB assigned to each of two "Advanced programmable interrupt controller" (total of 8MB).

Not sure if 8GB is normal for Hyper-V video, but that doesn't explain the rest of the missing RAM, or why the reserved portion increased when I increased the memory allocation...

Any advice on how to resolve this and release the memory?

  • Hi, the integrator tool is installed correctly ?
    – yagmoth555
    Jun 24, 2019 at 18:09
  • Not sure. I believe in Server 2016 that's installed automatically by Windows Update? Is there a way to check if it's properly installed?
    – jgalak
    Jun 24, 2019 at 18:11
  • I went to Hyper-V Manager and opened the settings screen for VM. Under Integration Services, everything was checked except "Guest Services". I've turned that on just in case. Not sure if that helps.
    – jgalak
    Jun 24, 2019 at 18:17

1 Answer 1


I turned off dynamic memory for this VM, and the "Hardware Reserved" went away.

Which makes me think that the "Hardware Reserved" was actually that part of dynamic memory that the VM was entitled to, but was not actually allocated to it by the hypervisor, as it was not needed. Not sure if that's what it actually was.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.