Issue 1If you back up a Hyper-V virtual machine that has multiple volumes, the backup may fail. If you check the VMMS event log after the backup failure occurs, the following event is logged:
Issue 2The Microsoft Hyper-V VSS Writer may enter an unstable state if a backup of the Hyper-V virtual machine fails. If you run the vssadmin list writers command, the Microsoft Hyper-V VSS Writer is not listed. To return the Microsoft Hyper-V VSS Writer to a stable state, the Hyper-V Virtual Machine Management service must be restarted.
Issue 3You cannot restore a Hyper-V virtual machine if the virtual machine was configured to use a legacy network adapter.
- On a Windows Server 2008-based computer, the updated Integration Services are listed as KB960242 in the Programs and Features item in Control Panel.
- On a Windows Vista-based computer, the updated Integration Services are listed as KB960243 in the Programs and Features item in Control Panel.
Service Pack InformationTo 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:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
PrerequisitesBefore you apply this update, the release version of Hyper-V must be installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Restart requirementYou have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2008 file information notesThe .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for 64-bit versions of Windows Server 2008" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.
Windows Server 2008, 64-bit versions
|File name||File version||File size||Date||Time||Platform|
|Blank.vfd||Not Applicable||1,474,560||18-Dec-2007||21:18||Not Applicable|
|Vmguest.iso||Not Applicable||42,584,064||21-Dec-2008||23:20||Not Applicable|
|Windowsvirtualization.mof||Not Applicable||406,536||13-Jan-2009||00:52||Not Applicable|
|Windowsvirtualizationuninstall.mof||Not Applicable||572||11-Jul-2008||20:06||Not Applicable|
Additional file information for 64-bit versions of Windows Server 2008
|File name||File version||File size||Date||Time||Platform|
|Amd64_5ea2a0e012fba496634951da2e3c633f_31bf3856ad364e35_6.0.6001.22352_none_898535921950c54c.manifest||Not Applicable||703||14-Jan-2009||00:09||Not Applicable|
|Amd64_08d4dc4f14b70e82efea40a20802f63d_31bf3856ad364e35_6.0.6001.22352_none_c03e75641cbceedb.manifest||Not Applicable||698||14-Jan-2009||00:09||Not Applicable|
|Amd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.0.6001.22327_none_932fa5e93071aa4d.manifest||Not Applicable||249,723||13-Jan-2009||5:28||Not Applicable|
|Amd64_microsoft-hyper-v-vstack_31bf3856ad364e35_6.0.6001.22327_none_c157114ac5a25cab.manifest||Not Applicable||45,508||13-Jan-2009||5:23||Not Applicable|
|Package_1_for_kb959962~31bf3856ad364e35~amd64~~184.108.40.206.mum||Not Applicable||2,563||14-Jan-2009||00:09||Not Applicable|
|Package_2_for_kb959962~31bf3856ad364e35~amd64~~220.127.116.11.mum||Not Applicable||2,563||14-Jan-2009||00:09||Not Applicable|
|Package_for_kb959962_sc_0~31bf3856ad364e35~amd64~~18.104.22.168.mum||Not Applicable||1,528||14-Jan-2009||00:09||Not Applicable|
|Package_for_kb959962_sc~31bf3856ad364e35~amd64~~22.214.171.124.mum||Not Applicable||1,430||14-Jan-2009||00:09||Not Applicable|
|Package_for_kb959962_server_0~31bf3856ad364e35~amd64~~126.96.36.199.mum||Not Applicable||1,532||14-Jan-2009||00:09||Not Applicable|
|Package_for_kb959962_server~31bf3856ad364e35~amd64~~188.8.131.52.mum||Not Applicable||1,438||14-Jan-2009||00:09||Not Applicable|