You cannot connect to a virtual machine when the Windows Server 2008 Hyper-V VMMS certificate has expired

Symptoms

On a Windows Server 2008-based computer that has the Hyper-V role installed, or on a Microsoft Hyper-V Server 2008-based computer, you may experience one of the following issues:

  • When you try to connect to a virtual machine, you receive the following error message:

    Cannot connect to the virtual machine because the authentication certificate is expired or invalid. Would you like to try connecting again?

  • When you start a virtual machine, you receive the following error message:

    'VMName' failed to initialize.

    Could not initialize machine remoting system. Error: ‘Unspecified error’ (0x80004005).
    Could not find a usable certificate. Error: ‘Unspecified error’ (0x80004005).

Cause

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:

968849 How to obtain the latest service pack for Windows Server 2008

Update information

The following file is available for download from the Microsoft Download Center:

Update for Windows Server 2008 x64 Edition (KB967902)

Download Download the 967902 package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

Before 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:

950050 Description of the update for the release version of the Hyper-V technology for Windows Server 2008

Restart requirement

You must restart the computer after you apply this update

Update replacement information

This update does not replace any other updates.

File information

The English version of this update 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 notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for 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.

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Vmms.exe

6.0.6001.22383

3,878,400

21-Feb-2009

06:17

x64

Vmwp.exe

6.0.6001.22383

3,526,144

21-Feb-2009

06:17

x64


The hotfix also contains the GDR version for all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Vmms.exe

6.0.6001.18221

3,878,816

21-Feb-2009

05:06

x64

Vmwp.exe

6.0.6001.18221

3,526,120

21-Feb-2009

05:06

x64



After you install this update, the Hyper-V VMMS certificate can be renewed automatically when it is expired.

Workaround

To work around this issue, you can generate a new certificate. To do this, follow these steps:

  1. Shut down or save all virtual machines.

  2. Restart the Hyper-V VMMS.

  3. Start the virtual machines.

Note Because the Hyper-V VMMS certificate is valid for one year, the update has to be applied to prevent this issue from occurring in the future.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

To determine the expiration date for the Hyper-V VMM service self-signed certificate, follow these steps:

  1. Click Start , click Run , type mmc , and then click OK.

  2. On the File menu, click Add/Remove Snap-in.

  3. Click Certificates , and then click Add.

  4. Click Service account , and then click Next.

  5. Click Local Computer , and then click Next.

  6. Click Hyper-V Virtual Machine Management , and then click Finish.

  7. Click OK to close the Add/Remove Snap-in window.

  8. Expand Certificates - Service , expand Vmms\Personal , and then click Certificates.

  9. Double-click the VMM Service certificate, and then check the expiration date in the VMM Service certificate window.


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: -

824684
Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Amd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.0.6001.22383_none_92eac53930a5ec97.manifest

Not Applicable

249,723

21-Feb-2009

06:38

Not Applicable

Amd64_microsoft-hyper-v-vstack-vmwp_31bf3856ad364e35_6.0.6001.22383_none_91954bdf3181df4c.manifest

Not Applicable

192,587

21-Feb-2009

06:37

Not Applicable

Package_for_kb967902_sc_0_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,505

21-Feb-2009

14:39

Not Applicable

Package_for_kb967902_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,529

21-Feb-2009

14:38

Not Applicable

Package_for_kb967902_sc_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,411

21-Feb-2009

14:39

Not Applicable

Package_for_kb967902_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,431

21-Feb-2009

14:38

Not Applicable

Package_for_kb967902_server_0_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,509

21-Feb-2009

14:39

Not Applicable

Package_for_kb967902_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,532

21-Feb-2009

14:38

Not Applicable

Package_for_kb967902_server_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,419

21-Feb-2009

14:39

Not Applicable

Package_for_kb967902_server~31bf3856ad364e35~amd64~~6.0.1.0.mum

Not Applicable

1,439

21-Feb-2009

14:38

Not Applicable

Update-bf.mum

Not Applicable

1,771

21-Feb-2009

14:39

Not Applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×