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.

Windows Remote Management (WinRM) does not accept HTTP authorization requests that are larger than 16 KB on a computer that is running Windows Server 2008 or Windows Vista


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have Windows Remote Management (WinRM) installed on a computer that is running Windows Server 2008 or Windows Vista.
  • You have a user security token that is larger than 16 KB because of the domain configuration.

    Note The size of the user security token grows together with the number of groups to which the user belongs.
  • You start a WinRM operation from this computer. Or, you use another application that uses WinRM for communication, such as Microsoft System Center Virtual Machine Manager.
In this scenario, the operation fails and you receive following error code:
0x803380f7
Additionally, the following event is logged in the System log:


Log Name: System
Source: Microsoft-Windows-Security-Kerberos
Date: Date & Time
Event ID: 6
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Computer Name
Description: The kerberos SSPI package generated an output token of size number bytes, which was too large to fit in the token buffer of size number bytes, provided by process id number. The output SSPI token being too large is probably the result of the user user name being a member of a large number of groups. It is recommended to minimize the number of groups a user belongs to. If the problem can not be corrected by reduction of the group memberships of this user, please contact your system administrator to increase the maximum token size, which in term is configured machine-wide via the following registry value: HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters\MaxTokenSize.


If you run command "winrm identify -remote: <name-of-remote-machine>" at the command prompt, you will receive the follwoing error message:
WSManFault
Message = WinRM cannot process the request. An error occured while using the following authentication method: Kerberos. Possible causes are:
The user name or password specified are invalid.
Kerberos is used when no authentication method and no user name are specified.
Kerberos does not accept a local user name.
The Service Principal Name (SPN) for the remote computer name and port does not exist.
The client and remote computers are in different domains and there is no trust between the two domains.
You may check the Event Viewer for events related to authentication.
To continue using the same authentication method, check and resolve the issues above.
To use a different authentication method, specify a valid user name and password and do one of the following: add the destination computer to the TrustedHosts configuration setting for WinRM or use HTTPS transport. You can get information about the WinRM configuration by running the following command: winrm help config.

Error number: -2147024843 0x80070035
The network path was not found.

↑ Back to the top


Cause

In some domain environments, the user security token that is used to authenticate the user to the server may be larger than 16 KB. This can occur when a user is a member of many security groups.

However, WinRM has a 16 KB size limit for HTTP authorization requests. Therefore, WinRM does not accept HTTP authorization requests that use a user security token that is larger than 16 KB.

↑ Back to the top


Resolution

A hotfix is available to resolve this issue. After you apply this hotfix, you can customize the values of MaxFieldLength and MaxRequestBytes registry entries to make WinRM accept authorization requests larger than 16 KB.

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 this specific problem. 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.

Prerequisites

To apply this hotfix, your computer must be running one of the following operating systems:
  • Windows Vista Service Pack 1
  • Windows Vista Service Pack 2
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

After you apply this hotfix, you can customize the following two registry entries to make WinRM accept authorization requests larger than 16KB.

The MaxFieldLength registry entry
Name: MaxFieldLength
TYPE: REG_DWORD
Value: default (16384). Range (64 to 65534)
Location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Explanation: The MaxFieldLength registry entry specifies the maximum size limit of each HTTP request header in byte.


The MaxRequestBytes registry entry
Name: MaxRequestBytes
Type: REG_DWORD
Value: default (16384). Range (64 to 65534)
Location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Explanation: The MaxRequestBytes registry entry specifies the upper limit for the total size of the Request line and the headers in byte.
Typically, the MaxFieldLength registry entry is configured together with the MaxRequestBytes registry entry. If the MaxRequestBytes value is less than the MaxFieldLength value, the MaxFieldLength value is adjusted.

For more information about the Http.sys registry settings, click the following article number to view the article in the Microsoft Knowledge Base:
820129 Http.sys registry settings for IIS

File information

The 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 Vista and Windows Server 2008 file information note

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameFile versionFile sizeDateTimePlatformSP requirement
Winrm.cmdNot Applicable3501-Apr-200919:13Not ApplicableSP1
Winrm.vbsNot Applicable195,12201-Apr-200919:13Not ApplicableSP1
Wsmanhttpconfig.exe6.0.6001.2243230,72013-May-200912:42x86SP1
Wsmanmigrationplugin.dll6.0.6001.22432188,92813-May-200914:53x86SP1
Wsmauto.dll6.0.6001.22432123,90413-May-200914:53x86SP1
Wsmauto.mofNot Applicable4,43001-Apr-200919:13Not ApplicableSP1
Wsmcl.dll6.0.6001.224321,53613-May-200914:53x86SP1
Wsmprov.dll6.0.6001.2243255,29613-May-200914:53x86SP1
Wsmpty.xslNot Applicable1,55901-Apr-200919:13Not ApplicableSP1
Wsmres.dll6.0.6001.2243213,31213-May-200912:42x86SP1
Wsmsvc.dll6.0.6001.22432748,54413-May-200914:53x86SP1
Wsmtxt.xslNot Applicable2,17801-Apr-200919:13Not ApplicableSP1
Wsmwmipl.dll6.0.6001.22432176,12813-May-200914:53x86SP1
Winrm.cmdNot Applicable3503-Apr-200921:49Not ApplicableSP2
Winrm.vbsNot Applicable195,12203-Apr-200921:49Not ApplicableSP2
Wsmanhttpconfig.exe6.0.6002.2213530,72013-May-200912:28x86SP2
Wsmanmigrationplugin.dll6.0.6002.22135188,92813-May-200912:28x86SP2
Wsmauto.dll6.0.6002.22135123,90413-May-200912:28x86SP2
Wsmauto.mofNot Applicable4,43003-Apr-200921:49Not ApplicableSP2
Wsmcl.dll6.0.6002.221351,53613-May-200912:27x86SP2
Wsmprov.dll6.0.6002.2213555,29613-May-200912:28x86SP2
Wsmpty.xslNot Applicable1,55903-Apr-200921:49Not ApplicableSP2
Wsmres.dll6.0.6002.2213513,31213-May-200912:27x86SP2
Wsmsvc.dll6.0.6002.22135748,54413-May-200914:45x86SP2
Wsmtxt.xslNot Applicable2,17803-Apr-200921:49Not ApplicableSP2
Wsmwmipl.dll6.0.6002.22135176,12813-May-200912:28x86SP2
For all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Winrm.cmdNot Applicable3501-Apr-200916:43Not ApplicableSP1Not Applicable
Winrm.vbsNot Applicable195,12201-Apr-200916:43Not ApplicableSP1Not Applicable
Wsmanhttpconfig.exe6.0.6001.2243231,23213-May-200913:02x64SP1Not Applicable
Wsmanmigrationplugin.dll6.0.6001.22432252,92813-May-200915:09x64SP1Not Applicable
Wsmauto.dll6.0.6001.22432161,79213-May-200915:09x64SP1Not Applicable
Wsmauto.mofNot Applicable4,43001-Apr-200916:43Not ApplicableSP1Not Applicable
Wsmcl.dll6.0.6001.224321,53613-May-200915:09x64SP1Not Applicable
Wsmprov.dll6.0.6001.2243273,21613-May-200915:09x64SP1Not Applicable
Wsmpty.xslNot Applicable1,55901-Apr-200916:43Not ApplicableSP1Not Applicable
Wsmres.dll6.0.6001.2243213,31213-May-200913:02x64SP1Not Applicable
Wsmsvc.dll6.0.6001.224321,093,63213-May-200915:09x64SP1Not Applicable
Wsmtxt.xslNot Applicable2,17801-Apr-200916:43Not ApplicableSP1Not Applicable
Wsmwmipl.dll6.0.6001.22432284,67213-May-200915:09x64SP1Not Applicable
Winrm.cmdNot Applicable3501-Apr-200919:13Not ApplicableSP1WOW
Winrm.vbsNot Applicable195,12201-Apr-200919:13Not ApplicableSP1WOW
Wsmanhttpconfig.exe6.0.6001.2243230,72013-May-200912:42x86SP1WOW
Wsmanmigrationplugin.dll6.0.6001.22432188,92813-May-200914:53x86SP1WOW
Wsmauto.dll6.0.6001.22432123,90413-May-200914:53x86SP1WOW
Wsmauto.mofNot Applicable4,43001-Apr-200919:13Not ApplicableSP1WOW
Wsmcl.dll6.0.6001.224321,53613-May-200914:53x86SP1WOW
Wsmprov.dll6.0.6001.2243255,29613-May-200914:53x86SP1WOW
Wsmpty.xslNot Applicable1,55901-Apr-200919:13Not ApplicableSP1WOW
Wsmres.dll6.0.6001.2243213,31213-May-200912:42x86SP1WOW
Wsmsvc.dll6.0.6001.22432748,54413-May-200914:53x86SP1WOW
Wsmtxt.xslNot Applicable2,17801-Apr-200919:13Not ApplicableSP1WOW
Wsmwmipl.dll6.0.6001.22432176,12813-May-200914:53x86SP1WOW
Winrm.cmdNot Applicable3503-Apr-200921:08Not ApplicableSP2Not Applicable
Winrm.vbsNot Applicable195,12203-Apr-200921:08Not ApplicableSP2Not Applicable
Wsmanhttpconfig.exe6.0.6002.2213531,23213-May-200912:41x64SP2Not Applicable
Wsmanmigrationplugin.dll6.0.6002.22135252,92813-May-200914:47x64SP2Not Applicable
Wsmauto.dll6.0.6002.22135161,79213-May-200914:47x64SP2Not Applicable
Wsmauto.mofNot Applicable4,43003-Apr-200921:08Not ApplicableSP2Not Applicable
Wsmcl.dll6.0.6002.221351,53613-May-200912:41x64SP2Not Applicable
Wsmprov.dll6.0.6002.2213573,21613-May-200914:47x64SP2Not Applicable
Wsmpty.xslNot Applicable1,55903-Apr-200921:08Not ApplicableSP2Not Applicable
Wsmres.dll6.0.6002.2213513,31213-May-200912:41x64SP2Not Applicable
Wsmsvc.dll6.0.6002.221351,093,63213-May-200914:47x64SP2Not Applicable
Wsmtxt.xslNot Applicable2,17803-Apr-200921:08Not ApplicableSP2Not Applicable
Wsmwmipl.dll6.0.6002.22135284,67213-May-200914:47x64SP2Not Applicable
Winrm.cmdNot Applicable3503-Apr-200921:49Not ApplicableSP2WOW
Winrm.vbsNot Applicable195,12203-Apr-200921:49Not ApplicableSP2WOW
Wsmanhttpconfig.exe6.0.6002.2213530,72013-May-200912:28x86SP2WOW
Wsmanmigrationplugin.dll6.0.6002.22135188,92813-May-200912:28x86SP2WOW
Wsmauto.dll6.0.6002.22135123,90413-May-200912:28x86SP2WOW
Wsmauto.mofNot Applicable4,43003-Apr-200921:49Not ApplicableSP2WOW
Wsmcl.dll6.0.6002.221351,53613-May-200912:27x86SP2WOW
Wsmprov.dll6.0.6002.2213555,29613-May-200912:28x86SP2WOW
Wsmpty.xslNot Applicable1,55903-Apr-200921:49Not ApplicableSP2WOW
Wsmres.dll6.0.6002.2213513,31213-May-200912:27x86SP2WOW
Wsmsvc.dll6.0.6002.22135748,54413-May-200914:45x86SP2WOW
Wsmtxt.xslNot Applicable2,17803-Apr-200921:49Not ApplicableSP2WOW
Wsmwmipl.dll6.0.6002.22135176,12813-May-200912:28x86SP2WOW
For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Winrm.cmdNot Applicable3501-Apr-200916:43Not ApplicableSP1Not Applicable
Winrm.vbsNot Applicable195,12201-Apr-200916:43Not ApplicableSP1Not Applicable
Wsmanhttpconfig.exe6.0.6001.2243261,44013-May-200912:48IA-64SP1Not Applicable
Wsmanmigrationplugin.dll6.0.6001.22432528,89613-May-200914:52IA-64SP1Not Applicable
Wsmauto.dll6.0.6001.22432343,55213-May-200914:52IA-64SP1Not Applicable
Wsmauto.mofNot Applicable4,43001-Apr-200916:43Not ApplicableSP1Not Applicable
Wsmcl.dll6.0.6001.224321,53613-May-200914:52IA-64SP1Not Applicable
Wsmprov.dll6.0.6001.22432156,67213-May-200914:52IA-64SP1Not Applicable
Wsmpty.xslNot Applicable1,55901-Apr-200916:43Not ApplicableSP1Not Applicable
Wsmres.dll6.0.6001.2243213,31213-May-200912:48IA-64SP1Not Applicable
Wsmsvc.dll6.0.6001.224322,303,48813-May-200914:52IA-64SP1Not Applicable
Wsmtxt.xslNot Applicable2,17801-Apr-200916:43Not ApplicableSP1Not Applicable
Wsmwmipl.dll6.0.6001.22432532,99213-May-200914:52IA-64SP1Not Applicable
Winrm.cmdNot Applicable3501-Apr-200919:13Not ApplicableSP1WOW
Winrm.vbsNot Applicable195,12201-Apr-200919:13Not ApplicableSP1WOW
Wsmanhttpconfig.exe6.0.6001.2243230,72013-May-200912:42x86SP1WOW
Wsmanmigrationplugin.dll6.0.6001.22432188,92813-May-200914:53x86SP1WOW
Wsmauto.dll6.0.6001.22432123,90413-May-200914:53x86SP1WOW
Wsmauto.mofNot Applicable4,43001-Apr-200919:13Not ApplicableSP1WOW
Wsmcl.dll6.0.6001.224321,53613-May-200914:53x86SP1WOW
Wsmprov.dll6.0.6001.2243255,29613-May-200914:53x86SP1WOW
Wsmpty.xslNot Applicable1,55901-Apr-200919:13Not ApplicableSP1WOW
Wsmres.dll6.0.6001.2243213,31213-May-200912:42x86SP1WOW
Wsmsvc.dll6.0.6001.22432748,54413-May-200914:53x86SP1WOW
Wsmtxt.xslNot Applicable2,17801-Apr-200919:13Not ApplicableSP1WOW
Wsmwmipl.dll6.0.6001.22432176,12813-May-200914:53x86SP1WOW
Winrm.cmdNot Applicable3503-Apr-200921:09Not ApplicableSP2Not Applicable
Winrm.vbsNot Applicable195,12203-Apr-200921:09Not ApplicableSP2Not Applicable
Wsmanhttpconfig.exe6.0.6002.2213561,44013-May-200912:36IA-64SP2Not Applicable
Wsmanmigrationplugin.dll6.0.6002.22135528,89613-May-200914:39IA-64SP2Not Applicable
Wsmauto.dll6.0.6002.22135343,55213-May-200914:39IA-64SP2Not Applicable
Wsmauto.mofNot Applicable4,43003-Apr-200921:08Not ApplicableSP2Not Applicable
Wsmcl.dll6.0.6002.221351,53613-May-200912:36IA-64SP2Not Applicable
Wsmprov.dll6.0.6002.22135156,67213-May-200914:39IA-64SP2Not Applicable
Wsmpty.xslNot Applicable1,55903-Apr-200921:09Not ApplicableSP2Not Applicable
Wsmres.dll6.0.6002.2213513,31213-May-200912:36IA-64SP2Not Applicable
Wsmsvc.dll6.0.6002.221352,303,48813-May-200914:39IA-64SP2Not Applicable
Wsmtxt.xslNot Applicable2,17803-Apr-200921:09Not ApplicableSP2Not Applicable
Wsmwmipl.dll6.0.6002.22135532,99213-May-200914:39IA-64SP2Not Applicable
Winrm.cmdNot Applicable3503-Apr-200921:49Not ApplicableSP2WOW
Winrm.vbsNot Applicable195,12203-Apr-200921:49Not ApplicableSP2WOW
Wsmanhttpconfig.exe6.0.6002.2213530,72013-May-200912:28x86SP2WOW
Wsmanmigrationplugin.dll6.0.6002.22135188,92813-May-200912:28x86SP2WOW
Wsmauto.dll6.0.6002.22135123,90413-May-200912:28x86SP2WOW
Wsmauto.mofNot Applicable4,43003-Apr-200921:49Not ApplicableSP2WOW
Wsmcl.dll6.0.6002.221351,53613-May-200912:27x86SP2WOW
Wsmprov.dll6.0.6002.2213555,29613-May-200912:28x86SP2WOW
Wsmpty.xslNot Applicable1,55903-Apr-200921:49Not ApplicableSP2WOW
Wsmres.dll6.0.6002.2213513,31213-May-200912:27x86SP2WOW
Wsmsvc.dll6.0.6002.22135748,54413-May-200914:45x86SP2WOW
Wsmtxt.xslNot Applicable2,17803-Apr-200921:49Not ApplicableSP2WOW
Wsmwmipl.dll6.0.6002.22135176,12813-May-200912:28x86SP2WOW

↑ 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, click the following article number to view the article in the Microsoft Knowledge Base:
970875 Large Kerberos tokens cause WinRM requests to fail
For more information, 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 Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Package_for_kb971244_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36714-May-200901:29Not Applicable
Package_for_kb971244_client_2~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69314-May-200901:29Not Applicable
Package_for_kb971244_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71314-May-200901:29Not Applicable
Package_for_kb971244_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42114-May-200901:29Not Applicable
Package_for_kb971244_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69014-May-200901:29Not Applicable
Package_for_kb971244_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,70114-May-200901:29Not Applicable
Package_for_kb971244_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42514-May-200901:29Not Applicable
Package_for_kb971244_server_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69414-May-200901:29Not Applicable
Package_for_kb971244_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71314-May-200901:29Not Applicable
X86_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.0.6001.22432_none_cad0a8acc63bea15.manifestNot Applicable97,02313-May-200917:53Not Applicable
X86_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.0.6002.22135_none_ccba1b72c35f8b3e.manifestNot Applicable97,02313-May-200917:50Not Applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Package_for_kb971244_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36714-May-200901:29Not Applicable
Package_for_kb971244_client_2~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69314-May-200901:29Not Applicable
Package_for_kb971244_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71314-May-200901:29Not Applicable
Package_for_kb971244_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42114-May-200901:29Not Applicable
Package_for_kb971244_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69014-May-200901:29Not Applicable
Package_for_kb971244_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,70114-May-200901:29Not Applicable
Package_for_kb971244_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42514-May-200901:29Not Applicable
Package_for_kb971244_server_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69414-May-200901:29Not Applicable
Package_for_kb971244_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71314-May-200901:29Not Applicable
X86_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.0.6001.22432_none_cad0a8acc63bea15.manifestNot Applicable97,02313-May-200917:53Not Applicable
X86_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.0.6002.22135_none_ccba1b72c35f8b3e.manifestNot Applicable97,02313-May-200917:50Not Applicable
Additional files for all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.0.6001.22432_none_cad24ca2c639f311.manifestNot Applicable97,04813-May-200917:42Not Applicable
Ia64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.0.6002.22135_none_ccbbbf68c35d943a.manifestNot Applicable97,04813-May-200917:31Not Applicable
Package_for_kb971244_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42514-May-200901:29Not Applicable
Package_for_kb971244_sc_1~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,52914-May-200901:29Not Applicable
Package_for_kb971244_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,70614-May-200901:29Not Applicable
Package_for_kb971244_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42914-May-200901:29Not Applicable
Package_for_kb971244_server_1~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,53314-May-200901:29Not Applicable
Package_for_kb971244_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,71714-May-200901:29Not Applicable
Wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.0.6001.22432_none_3143ee82b2fa1d46.manifestNot Applicable105,33213-May-200917:48Not Applicable
Wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.0.6002.22135_none_332d6148b01dbe6f.manifestNot Applicable105,33213-May-200917:44Not Applicable

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseadvanced, kbfix, kbsurveynew, kbqfe, KB971244

↑ Back to the top

Article Info
Article ID : 971244
Revision : 4
Created on : 6/21/2014
Published on : 6/21/2014
Exists online : False
Views : 746