Vmwp.exe is a virtual machine worker process that leaks memory on a Hyper-V host when a third-party management console is installed on a Windows 7 guest virtual machine. A hotfix is available from Microsoft Support to fix this problem in Windows 8 or Windows Server 2012.

However, virtual machine worker process (vmwp.exe) does not refresh all of its file handles. Resolution. Verify there is sufficient space on the storage supporting the virtual machine configuration files. Execute a Live Migration of the virtual machine (s) experiencing the problem to another node in the cluster.

Cause. This issue occurs because one Vmwp.exe process incorrectly enters into a deadlock situation. Resolution. Hotfix information. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.

This article describes an issue that occurs on a Windows Server 2012 R2 computer tha's running Hyper-V with generation 2 virtual machines (VMs). A hotfix is available to fix this issue. The hotfix has a prerequisite.

Fixes an issue in which the system time of a virtual machine becomes incorrect after it crashes or resets and then restarts. The issue occurs on a Hyper-V host that is running a 64-bit version of Windows 8 or Windows Server 2012.

Fixes an issue in which a cross-page memory read or write operation causes a virtual machine to crash. The issue occurs when a memory read or write operation is performed that touches the MMIO region on a 64-bit Windows 8-based or Windows Server 2012-based Hyper-V host.

Fixes an issue in which it takes a very long time to generate a complete memory dump file on a Hyper-V virtual machine in Windows Server 2008 R2. This issue occurs if the virtual machine uses Dynamic Memory and you set the "Maximum RAM" setting to a value that is larger than 4 GB.

You attach a virtual hard disk (VHD) that is larger than 127 gigabytes (GB) to the Hyper-V virtual machine. In this scenario, Linux displays only 127 GB of available space. Cause. This issue occurs because Hyper-V cannot set bits in the LBA48 code. Resolution. Hotfix information. A supported hotfix is available from Microsoft.

Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. Cause. This issue occurs because the Hyper-V virtual IDE controller erroneously reports success if an operating system on the guest requests to disable the disk cache.

Virtual machine live migration is unsuccessful on a server that is running Windows Server 2008 R2 - Microsoft Support. Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Standard. Symptoms. You perform virtual machine live migration on a server that is running Windows Server 2008 R2.