Hyper-V: Update List for Windows Server 2008 R2

The latest Hyper-V service packs, updates, and hotfixes for Windows Server 2008 R2 are listed here in chronological order.

Last Updated: April 27, 2011

You can subscribe to updates for this page using RSS: http://social.technet.microsoft.com/wiki/contents/articles/hyper-v-update-list-for-windows-server-2008-r2/rss.aspx

Updates that are available on Windows Update are indicated, as well as the download location for those that are available at the Microsoft Download Center. These updates and hotfixes can help avoid some known issues and may save you a support call.

Note: Some updates are required only under certain circumstances, as noted in the table. Also, you may want to see the list of updates for Hyper-V in Windows Server 2008 (which includes updates for Windows Server 2008 Service Pack 2)(http://go.microsoft.com/fwlink/?LinkId=183322). A hotfix is intended to correct only the problem that is described in the article. You should not apply the hotfix if you have net seen the symptoms.

Originally published: May 26, 2010 at: http://technet.microsoft.com/en-us/library/ff394763%28WS.10%29.aspx

Applies To: Windows Server 2008 R2 (This wiki page is part of a pilot program to remove topics such as this one from the TechNet and MSDN libraries and move them to the wiki. Why not leave this on the Library? Customers asked for an RSS feed so that they can get a notification when the list is updated and a new update is released. The RSS feed for this wiki article is http://social.technet.microsoft.com/wiki/contents/articles/hyper-v-update-list-for-windows-server-2008-r2/rss.aspx.) The following table shows the list of software updates and hotfixes for Hyper-V in Windows Server 2008 R2. Updates that are available on Windows Update are indicated, as well as the download location for those that are available at the Microsoft Download Center. These updates and hotfixes can help avoid some known issues and may save you a support call.

Note Some updates are required only under certain circumstances, as noted in the table. Also, you may want to see the list of updates for Hyper-V in Windows Server 2008 (which includes updates for Windows Server 2008 Service Pack 2)(http://go.microsoft.com/fwlink/?LinkId=183322). A hotfix is intended to correct only the problem that is described in the article. You should not apply the hotfix if you have net seen the symptoms.

In some cases, the version number of the Integration Services (also known as Integration Components) has changed. The IC version number for the RTM version of Windows Server 2008 is 6.0.6001.17101.The IC version number for Windows Server 2008 R2 is 6.1.7600.16385.The IC version number for Windows Server 2008 R2 SP1 (Beta) is 6.1.7601.16562.Other IC version numbers related to KBs are listed with the KB in the table below for your reference.Comprehensive list of Hyper-V R2 updates

KB Article and Date Published	Required?	File Name/IC Version	Applies to:	Availability
KB974598, “You receive a “Stop 0x0000007E” error on the first restart after you enable Hyper-V on a Windows Server 2008 R2-based computer” (http://go.microsoft.com/fwlink/?LinkId=181559) Publication date: 10/1/2009	Yes, if you encounter this error and your server uses a “C-state” (lower power state) that is supported by the processor, but is not supported by Hyper-V.	Windows6.1-KB974598-x64.msu	Windows Server 2008 R2	Hotfix
KB974909, “The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer” (http://go.microsoft.com/fwlink/?LinkId=183312) Publication date: 10/21/2009	No	Windows6.1-KB974909-v2-x64.msu	Windows Server 2008 R2	Hotfix
KB975354, “A Hyper-V update rollup package is available for a computer that is running Windows Server 2008 R2” (http://go.microsoft.com/fwlink/?LinkId=179092) Publication date: 10/21/2009	Yes, if you are running a backup or restore solution.	Windows6.1-KB975354-v2-x64.msu Windows6.1-KB975354-ia64.msu Windows6.1-KB975354-x86.msu	Windows Server 2008 R2	Hotfix
KB975530, “Stop error message on an Intel Xeon 5500 series processor-based computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed: “0x00000101 – CLOCK_WATCHDOG_TIMEOUT” (http://go.microsoft.com/fwlink/?LinkId=179091) Publication date: 11/20/2009	Yes, if you are running Hyper-V on the affected hardware.	Windows6.1-KB975530-v3-x64.msu IC 6.1.7600.20542	Windows Server 2008 R2	Download Center, Hotfix
KB974672, “Virtual machines stop responding (hang) during startup and the Vmms.exe process crashes on a Windows Server 2008 R2 computer that has the Hyper-V role installed“ (http://go.microsoft.com/fwlink/?LinkId=193212) Publication date: 10/14/2009	No	Windows6.1-KB974672-x64.msu	Windows Server 2008 R2	Hotfix
KB977894, “MS10-010: Vulnerability in Windows Server 2008 Hyper-V could allow denial of service” (http://go.microsoft.com/fwlink/?LinkId=193214) Publication date: 2/9/2010	Yes	Windows6.0-KB977894-x64.msu Windows6.1-KB977894-x64.msu	Windows Server 2008, Windows Server 2008 SP2, Windows Server 2008 R2	Security Bulletin
KB980856, “Stop error in Windows Server 2008 R2: “0x000000CA PNP_DETECTED_FATAL_ERROR”” (http://go.microsoft.com/fwlink/?LinkId=193215) Publication date: 3/12/2010	Yes, if you store VHDs on non-PNP disks.	Windows6.1-KB980856-x64.msu	Windows Server 2008 R2	Hotfix
KB981618, “The computer stops responding or restarts during the Hyper-V Live Migration process in Windows Server 2008 R2” (relates to AMD Errata 383)*** (http://go.microsoft.com/fwlink/?LinkID=193217) Publication date: 3/27/2010	Yes, if you are running Hyper-V on AMD processors.	Windows6.1-KB981618-x64.msu	Windows Server 2008 R2	Hotfix
KB981836, “Network connectivity for a Windows Server 2003-based Hyper-V virtual machine is lost temporarily in Windows Server 2008 R2” (http://go.microsoft.com/fwlink/?LinkId=193220) Publication date: 4/28/2010	Yes, if the server running Hyper-V has a virtual machine that is running Windows Server 2003.	Windows6.1-KB981836-x86.msu Windows6.1-KB981836-v2-x64.msu	Windows Server 2008 R2	Hotfix
KB981791, “”STOP: 0x0000001a” error message on a computer that has an Intel Westmere processor together with the Hyper-V role installed on Windows Server 2008 or on Windows Server 2008 R2” (http://go.microsoft.com/fwlink/?LinkID=193221) Publication date: 5/5/2010	Yes, if you are running Hyper-V on Intel Westmere processors.	Windows6.1-KB981791-x64.msu	Windows Server 2008 R2	Hotfix
KB982210:”Startup time increases or hangs at the logon “Welcome” screen if you frequently backup Hyper-V virtual machines on a Windows Server 2008 R2 system.” (http://support.microsoft.com/kb/982210) Publication date: 11/24/2010	Yes, if the issue applies to you.	Varies	Windows Server 2008 R2	Hotfix
KB345316 : “MS10-102: Vulnerability in Hyper-V could allow denial of service” (http://support.microsoft.com/kb/2345316) Publication Date: 12/14/2010	Yes	Varies	Windows Server 2008 R2	Security Bulletin
KB2264080:”An update rollup package for the Hyper-V role in Windows Server 2008 R2″ (http://support.microsoft.com/kb/2264080) Published on: 8/24/2010	Yes	N/A	Windows Server 2008 R2	Hotfix
KB2496089:”The Hyper-V Virtual Machine Management service stops responding intermittently when the service is stopped in Windows Server 2008 R2″ (http://support.microsoft.com/kb/2496089) Published on: 2/23/2011	Yes, if the issue applies to you.	N/A	Windows Server 2008 R2	Hotfix
KB2485986:”An update is available for Hyper-V Best Practices Analyzer for Windows Server 2008 R2″ (http://support.microsoft.com/kb/2485986) Published on: 2/24/2011	Yes	N/A	Windows Server 2008 R2	Hotfix
KB2263829: “The network connection of a running Hyper-V virtual machine may be lost under heavy outgoing network traffic on a computer that is running Windows Server 2008 R2 SP1” (http://support.microsoft.com/kb/2263829) Published on: 4/5/2011	Yes, if the issue applies to you.	N/A	Windows Server 2008 R2 SP1	Hotfix
KB2517374: “You cannot start virtual machines on a computer that is running Windows Server 2008 R2 and on which a CPU is installed that supports the AVX feature” (http://support.microsoft.com/kb/2517374) Published on: 4/5/2011	Yes, if the issue applies to you.	N/A	Windows Server 2008 R2, Windows Server 2008 R2 SP1	Hotfix
KB2521348: “A virtual machine online backup fails in Windows Server 2008 R2 when the SAN policy is set to “Offline All”” (http://support.microsoft.com/kb/2521348) Published on 4/27/2011	Yes, if the issue applies to you	N/A	Windows Server 2008 R2, Windows Server 2008 R2 SP1	Hotfix

KB2223005 (http://support.microsoft.com/kb/2223005) — The network connection is lost for a Windows Server 2003-based or Windows XP-based virtual machine that is hosted on a computer that is running Windows Server 2008 R2 KB2096902 (http://support.microsoft.com/kb/2096902) — Virtual machines in a VDI environment are not rolled back as expected if the disconnected Remote Desktop connections on the virtual machines are stopped by Group Policy KB2133637 (http://support.microsoft.com/kb/2133637) — The computer stops responding at startup in Windows Server 2008 R2 if you enable the Hyper-V role and if you have more than 512 GB of RAM KB2230887 (http://support.microsoft.com/kb/2230887) — The memory of a virtual machine does not increase when Dynamic Memory is enabled for a virtual machine system that is running Windows Server 2008 SP2 or Windows Web Server 2008 SP2
• KB2264080 (http://support.microsoft.com/kb/2264080) — An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010Note: This update supersedes the following three hotfixes (all three are currently included into the table above):
  KB975530 (http://support.microsoft.com/kb/975530) — Stop error message on an Intel Xeon 5500 series processor-based computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed: “0x00000101 – CLOCK_WATCHDOG_TIMEOUT

KB974909 (http://support.microsoft.com/kb/974909) — The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer KB981791 (http://support.microsoft.com/kb/981791) — “STOP: 0x0000001a” error message on a computer that has an Intel Westmere processor together with the Hyper-V role installed on Windows Server 2008 or on Windows Server 2008 R2

Hotfix: Longer startup time after backing up all disks of Windows Server 2008 R2 with Hyper-Vmghazai

Hotfix: The startup time increases every time after you back up the data on all the disks of the computer in Windows Server 2008 R2 if the computer runs some virtual machineshttp://support.microsoft.com/kb/982210 Whenever you backup a virtual machine using VSS, Windows momentarily connect the backup copy of the virtual machines virtual hard disks to the parent partition in order to clean them up after backup. Unfortunately with Windows Server 2008 R2 a new plug-and-play entry would get created in the Windows registry each time that we did this. Over time this would cause the registry to get larger and larger, which would in turn slow down the Windows boot process.This only applies to Windows Server 2008 R2 with Hyper-V and Windows Server 2008 R2 Hyper-V Server (not Windows Server 2008)

Missing from the tablePronichkin … Hans Vredevoort

975921 — “You may be unable to perform certain disk-related operations after an exception when a hardware provider tries to create a snapshot in Windows Server 2008 R2 or in Windows 7” (Vssvc.exe 6.1.7600.20532, required for proper backup with DPM) 977894 — “MS10-010: Vulnerability in Windows Server 2008 Hyper-V could allow denial of service” (Vid.sys 6.1.7600.16475) 976264 — “Application Compatibility Update for Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2: February 2010” [Not Required] 978637 — “An application runs in a Windows Vista context instead of in a Windows 7 context on a computer that is running an x64 edition of Windows 7 or of Windows Server 2008 R2” (Kernelbase.dll) [Not Required]

“STOP 0x000000A” When there is a request to allocate a large amount of contiguous physical memoryHans Vredevoort

This issue may occur when there is a request to the system to allocate a large amount of contiguous physical memory. For example, the issue occurs when there is a request to the system to allocate several gigabytes of contiguous physical memory to a virtual machine.Stop 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUALNot all 0xA STOPS are caused by this.http://support.microsoft.com/kb/979903

Network connectivity for a Windows Server 2003-based Hyper-V virtual machine is lost temporarilyHans Vredevoort

Consider the following scenario:

You install the Hyper-V role on a computer that is running Windows Server 2008 R2. The computer hosts a virtual machine (VM) that is running Windows Server 2003. The VM is running under a heavy load.

In this scenario, the network connectivity of the VM is lost and then resumes. The downtime for the network connectivity may be from several seconds to several minutes.http://support.microsoft.com/default.aspx?scid=kb;EN-US;981836

The “Validate Multiple Arbitration” test on Hyper-V R2-based failover cluster may incorrectly failHans Vredevoort

http://support.microsoft.com/kb/978562If SP1 stays away for a couple of months, it might not be a bad idea to roll up all these hotfixes for Hyper-V R2 clusters ?Hans Vredevoort, Cluster MVPhttp://hyper-v.nu/blogs/hans/

***April 2010 hotfix for Hyper-V R2 Live Migration on AMD Family 10h processorsHans Vredevoort

When you run Windows Server 2008 R2 Hyper-V on a computer that uses AMD Family 10h processors, the host computer may restart unexpectedly or stop responding. When the computer restarts or stop responding, you receive no error messages. This issue may occur when the Live Migration feature is used to move a virtual machine (VM) from one Windows Server 2008 R2 Hyper-V-based node to another node. This problem usually affects the source node that is the original location of the VM and usually does not affect the target node that is the new location where the VM will be moved.

Note: This issue may occur in other scenarios and occurs not only in Live Migration scenarios.