On a computer that is running Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2008 R2 Service Pack 1 (SP1), you have Windows Management Framework (WMF) 3.0 installed and you upgrade the operating system to Windows Server 2012. In this scenario, Server Manager refresh would fail with the following error:
When WMF 3.0 is installed on a down-level server operating system, FeatureInfoXml registry key value is created under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerManager\MgmtProvider
In Windows Server 2012, MgmtProvider does not expect this registry value to exist and when a down-level machine with WMF 3.0 installed is upgraded to Windows Server 2012, FeatureInfoXml registry value continues to exist. In the upgraded Windows Server 2012, when MgmtProvider determines that FeatureInfoXml registry value exists, it tries to execute the down-level features extraction code instead of calling the UXD provider for getting features. This results in the failure.
To resolve this problem, delete the FeatureInfoXml registry key value.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
Remove any incorrect values that may exist in the Registry. To do this, follow these steps:
Open Registry editor (regedit.exe)
Locate and then select the following registry subkey:
Right-click on the MgmtProvider key and then choose Export. Give the file a name and then save it.
From the right-side pane, select FeatureInfoXml registry value and delete it.
Click on OK to close out of the editor and then exit the registry editor.
Restart the computer.
To avoid this issue to occur, before upgrading to Windows Server 2012, uninstall Windows Management Framework 3.0.