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. WinRM operations to Hyper-V fail on a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based computer that has Windows Management Framework 3.0 installed

WinRM operations to Hyper-V fail on a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based computer that has Windows Management Framework 3.0 installed

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You manage a Hyper-V host from a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
  • You install Windows Management Framework (WMF) 3.0 on the computer.
  • You use Microsoft System Center Virtual Machine Manager (SCVMM) to manage the Hyper-V host and virtual machines.
In this scenario, "PUT" operations between Windows Remote Management (WinRM) and Hyper-V fail. Therefore, SCVMM cannot manage updates to the computer or to the virtual machines. When this issue occurs, you receive an error message that resembles the following:
Error number: -2147024882 0x8007000E
Not enough storage is available to complete this operation.

↑ Back to the top

Resolution

This hotfix is also available at Microsoft Update Catalog.

Hotfix information

A 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 website:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

To apply this hotfix, you must be running Windows 7 SP1 or Windows Server 2008 R2 SP1. Additionally, you must have Windows Management Framework (WMF) 3.0 installed on the computer.

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.16xxx    		Windows 7 and Windows Server 2008 R2RTMGDR
    6.1.760
    0.20xxx    		Windows 7 and Windows Server 2008 R2RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Winrm.cmdNot Applicable3513-Dec-201222:59Not Applicable
Winrm.vbsNot Applicable204,10513-Dec-201222:59Not Applicable
Wsmagent.dll6.2.9200.1639821,50418-Dec-201206:41x86
Wsmagent.mofNot Applicable82213-Dec-201222:59Not Applicable
Wsmagentuninstall.mofNot Applicable75413-Dec-201222:59Not Applicable
Wsmanconfig_schema.xmlNot Applicable4,67513-Dec-201222:59Not Applicable
Wsmanhttpconfig.exe6.2.9200.1639830,20818-Dec-201206:41x86
Wsmanmigrationplugin.dll6.2.9200.1639856,83218-Dec-201206:42x86
Wsmauto.dll6.2.9200.16398138,75218-Dec-201206:41x86
Wsmauto.mofNot Applicable4,43013-Dec-201222:59Not Applicable
Wsmgcdeps.dll6.2.9200.16398526,84818-Dec-201206:41x86
Wsmplpxy.dll6.2.9200.1639810,24018-Dec-201206:42x86
Wsmprovhost.exe6.2.9200.1639835,84018-Dec-201206:41x86
Wsmpty.xslNot Applicable1,55913-Dec-201222:59Not Applicable
Wsmres.dll6.2.9200.1639860,41613-Dec-201222:59x86
Wsmsvc.dll6.2.9200.163982,039,29618-Dec-201206:41x86
Wsmtxt.xslNot Applicable2,42613-Dec-201222:59Not Applicable
Wsmwmipl.dll6.2.9200.20586226,81618-Dec-201206:41x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Winrm.cmdNot applicable3513-Dec-201222:57Not applicable
Winrm.vbsNot applicable204,10513-Dec-201222:57Not applicable
Wsmagent.dll6.2.9200.1639826,11213-Dec-201222:57x64
Wsmagent.mofNot applicable82213-Dec-201222:57Not applicable
Wsmagentuninstall.mofNot applicable75413-Dec-201222:57Not applicable
Wsmanconfig_schema.xmlNot applicable4,67513-Dec-201222:57Not applicable
Wsmanhttpconfig.exe6.2.9200.1639828,67213-Dec-201222:57x64
Wsmanmigrationplugin.dll6.2.9200.1639866,56013-Dec-201222:57x64
Wsmauto.dll6.2.9200.16398157,18413-Dec-201222:57x64
Wsmauto.mofNot applicable4,43013-Dec-201222:57Not applicable
Wsmgcdeps.dll6.2.9200.16398630,78413-Dec-201222:57x64
Wsmplpxy.dll6.2.9200.1639813,82413-Dec-201222:57x64
Wsmprovhost.exe6.2.9200.1639830,72013-Dec-201222:57x64
Wsmpty.xslNot applicable1,55913-Dec-201222:57Not applicable
Wsmres.dll6.2.9200.1639860,41613-Dec-201222:57x64
Wsmsvc.dll6.2.9200.163982,832,38413-Dec-201222:57x64
Wsmtxt.xslNot applicable2,42613-Dec-201222:57Not applicable
Wsmwmipl.dll6.2.9200.20586308,73618-Dec-201206:06x64
Winrm.cmdNot applicable3513-Dec-201222:59Not applicable
Winrm.vbsNot applicable204,10513-Dec-201222:59Not applicable
Wsmagent.dll6.2.9200.1639821,50418-Dec-201206:41x86
Wsmagent.mofNot applicable82213-Dec-201222:59Not applicable
Wsmagentuninstall.mofNot applicable75413-Dec-201222:59Not applicable
Wsmanconfig_schema.xmlNot applicable4,67513-Dec-201222:59Not applicable
Wsmanhttpconfig.exe6.2.9200.1639830,20818-Dec-201206:41x86
Wsmanmigrationplugin.dll6.2.9200.1639856,83218-Dec-201206:42x86
Wsmauto.dll6.2.9200.16398138,75218-Dec-201206:41x86
Wsmauto.mofNot applicable4,43013-Dec-201222:59Not applicable
Wsmgcdeps.dll6.2.9200.16398526,84818-Dec-201206:41x86
Wsmplpxy.dll6.2.9200.1639810,24018-Dec-201206:42x86
Wsmprovhost.exe6.2.9200.1639835,84018-Dec-201206:41x86
Wsmpty.xslNot applicable1,55913-Dec-201222:59Not applicable
Wsmres.dll6.2.9200.1639860,41613-Dec-201222:59x86
Wsmsvc.dll6.2.9200.163982,039,29618-Dec-201206:41x86
Wsmtxt.xslNot applicable2,42613-Dec-201222:59Not applicable
Wsmwmipl.dll6.2.9200.20586226,81618-Dec-201206:41x86

↑ Back to the top

Status

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

↑ Back to the top

More Information

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

For more information about the scenario that is described in the "Symptoms" section, click the following article number to view the article in the Microsoft Knowledge Base:
2795043 Managing Hyper-V hosts using Virtual Machine Manager fails with Error: 0x8033803b after installing WMF 3.0

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
 
File nameX86_5d79be5d2c3f651e42e40a4bba317a45_31bf3856ad364e35_7.1.7601.22197_none_b89de018c0cc44aa.manifest
File versionNot Applicable
File size720
Date (UTC)18-Dec-2012
Time (UTC)15:27
PlatformNot Applicable
File nameX86_microsoft-windows-w..for-management-core_31bf3856ad364e35_7.1.7601.22197_none_be135993af8c8164.manifest
File versionNot Applicable
File size194,964
Date (UTC)18-Dec-2012
Time (UTC)13:05
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_9a3eceeb917358c74b9ddbf1b8bd060a_31bf3856ad364e35_7.1.7601.22197_none_68f81fab60e2df1f.manifest
File versionNot applicable
File size1,090
Date (UTC)18-Dec-2012
Time (UTC)15:27
PlatformNot applicable
File nameAmd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_7.1.7601.22197_none_1a31f51767e9f29a.manifest
File versionNot applicable
File size194,970
Date (UTC)18-Dec-2012
Time (UTC)13:52
PlatformNot applicable
File nameWow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_7.1.7601.22197_none_24869f699c4ab495.manifest
File versionNot applicable
File size189,607
Date (UTC)18-Dec-2012
Time (UTC)12:35
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2781512
Revision : 1
Created on : 1/7/2017
Published on : 5/24/2013
Exists online : False
Views : 256