Dynamic Memory is enabled but not responding on some virtual machines
Applies To: Windows Server 2016
For more information about best practices and scans, see Run Best Practices Analyzer Scans and Manage Scan Results.
|Operating System||Windows Server 2016|
In the following sections, italics indicates UI text that appears in the Best Practices Analyzer tool for this issue.
One or more virtual machines are experiencing problems with the driver required for Dynamic Memory in the guest operating system.
The guest operating system in the following virtual machines might not run or might run unreliably because Hyper-V cannot adjust the memory dynamically to respond to changes in memory demand. This impacts the following virtual machines:
<list of virtual machines>
This is expected behavior if the virtual machine is booting. If the virtual machine is not booting, make sure that integration services are upgraded to the latest version and that the guest operating system supports Dynamic Memory.
As of Windows Server 2016, integration services are delivered through Windows Update. Ensure the virtual machines are configured to receive updates to get the latest version of integration services.
Dynamic Memory works with specific versions of supported guests. See Hyper-V Dynamic Memory Overview for versions older than Windows Server 2016 and Windows 10.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.