Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Hyper-V services fails to start after installing Windows Management Framework 3.0 on Windows Server 2008 Service Pack 2 (SP2)

Hyper-V services fails to start after installing Windows Management Framework 3.0 on Windows Server 2008 Service Pack 2 (SP2)

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 Service Pack 2 (SP2)
  • You have Hyper-V role configured on this computer
  • You install Windows Management Framework 3.0 for Windows Server 2008 SP2
In this scenario, you may notice the following symptoms:
  1. The Hyper-V services stops after about 10 minutes and when you try to open the Hyper-V MMC, a message appears stating that Hyper-V has not been installed. Additionally, you may notice the following event getting logged:

    Note: Error 2147749902 means WBEM_E_INVALID_NAMESPACE
  2. While rebuilding WMI repository, the operation finishes successfully, however compiling the WindowsVirtualization.mof fails and you may receive error code: 0x80041042. Even manually running mofcomp WindowsVirtualization.mof may give the error code: 0x80041042

    Note: Error 0x80041042 means WBEM_E_INVALID_QUALIFIER
  3. If you have a computer that is installed with System Center 2012 along with WMF 3.0, you may notice the following event reported:


↑ Back to the top

Cause

This issue occurs because certain server applications are not compatible with Windows Management Framework 3.0.

Important: Before you install Windows Management Framework 3.0, review the "Prerequisites" section from the Microsoft Knowledge Base article:

2506146 Description of Windows Management Framework 3.0 for Windows Server 2008 SP2

↑ Back to the top

Resolution

To resolve this problem, follow the steps mentioned below.
  1. Uninstall Hyper-V role and restart the computer
  2. Uninstall the WMF 3.0 (KB 2506146 ) and restart the computer
  3. Reset WMI repository
  4. Reinstall the Hyper-V role and restart the computer.

↑ Back to the top

Keywords: kbtshoot, kb

↑ Back to the top

Article Info
Article ID : 2819843
Revision : 1
Created on : 1/7/2017
Published on : 2/22/2013
Exists online : False
Views : 331