Fixes a problem in which the Vmms.exe process crashes and an event ID 1000 is logged in the Application log. This problem typically occurs after you start a computer that is running Windows Server 2008 R2 that has the Hyper-V role installed.

You create a virtual machine (VM) in the Hyper-V cluster and enable the dynamic memory (DM). You restart the virtual machine management service (VMMS.exe). In this scenario, you encounter the following issues: The memory demand is empty in the Hyper-V Manager UI.

This issue occurs because of a race condition in the Hyper-V Virtual Machine Management service. When the race condition occurs, a thread that performs the service cleanup does not exit its message loop as expected. Therefore, you experience the issue that is described in the "Symptoms" section.

When a failover starts, the Vmms.exe process freezes on some of the failover cluster nodes. Therefore, several virtual machines are in the offline state. Cause. This issue occurs because of a mismatch of the access tokens. Resolution. Update information. To resolve this issue, install update rollup 2855336.

You create a virtual machine (VM) in the Hyper-V cluster and enable the dynamic memory (DM). You restart the virtual machine management service (VMMS.exe). In this scenario, you encounter the following issues: The memory demand is empty in the Hyper-V Manager UI.

You have a Server Message Block (SMB)-based storage system that is running on a Windows Server 2012 R2-based Hyper-V server. You try to perform a live migration. In this scenario, the Virtual Machine Management Service (Vmms.exe) on destination Hyper-V host crashes and the live migration fails.

This article describes an issue when you move the VM storage to another SMB storage in Windows 8.1 or Windows Server 2012 R2. The issue is resolved in hotfix 2965506 that is described in this article and has a prerequisite.

This issue occurs because the Hyper-V Virtual Machine Management service (VMMS) certificate has expired. Resolution. Service Pack Information. To resolve this problem, obtain the latest service pack for Windows Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hyper-V storage migration fails when you try to migrate virtual hard disk (VHD) and configuration files to Cluster Shared Volumes (CSV) volumes in Windows Server 2012 R2. When this issue occurs, you receive an error message that looks something like this: Migration did not succeed. Not enough disk space at '\'.

You try to perform a Shared Nothing Live Migration to migrate the virtual machine to the destination server. More specifically, you try to migrate the VHD files as follows: You try to migrate the smaller VHD file to the network share that maps to local drive C. Drive C has limited available space.