A long time delay occurs when you reconnect an IPSec connection from a computer that is running Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

Article translations Article translations
Article ID: 980915 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenarios.

Scenario 1
  • You have a Windows Server based cluster that uses Windows Network Load Balancing, Failover Clustering, a hardware load balancer, or a hardware cluster product.
  • You establish an Internet Protocol Security (IPsec) connection to the cluster virtual IP from a computer that is running one of the following operating systems:
    • Windows Server 2003
    • Windows Vista
    • Windows Server 2008
    • Windows 7
    • Windows Server 2008 R2
  • One node fails in the cluster, or you manually restart the node, or you fail the node so that another node picks up the client connection.
Scenario 2
  • A non-cluster Windows Server 2003-based operating system restarts in less than 6 minutes (such as a virtual machine), or restarts automatically within 6 minutes after a Stop error occurs.
  • You establish an IP security (IPsec) connection to the operating system from another computer that is running one of the following operating systems:
    • Windows Server 2003
    • Windows Vista
    • Windows Server 2008
    • Windows 7
    • Windows Server 2008 R2
In these scenarios, you experience a long time delay (about two or three minutes) when the client computer reestablishes the IPsec connection to the cluster in scenario 1 and the non-cluster computer in scenario 2.

CAUSE

This issue occurs because IPsec is not optimally designed for reconnection scenarios. A large time-out value is associated with the current IPSec security association (SA). We also try an additional negotiation which has to time out.

RESOLUTION

After you install the hotfix package, you must create the following registry subkeys on the Windows Server 2003-based client computer:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPSec\NlbsIdleTime

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\Oakley\NlbsIdle
Or, create the following registry subkeys on the client computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IKEEXT\Parameters\NlbsIdleTime

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IKEEXT\Parameters\NlbsQMRetransmitDuration
To do this, follow the steps that are described in the Registry information section.

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 Web site:
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 one of the following operating systems:
  • Windows Server 2003 Service Pack 2 (SP2)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, 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
For more information about how to obtain a Windows 7 or 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

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
After you install the hotfix package, you must create the following two registry subkeys on the Windows Server 2003-based client computer:
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPSec\NlbsIdleTime
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\Oakley\NlbsIdle
To do this, follow these steps:
  1. Click Start, click Run, type Regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPSec
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type NlbsIdleTime, and then press ENTER.
  5. Right-click NlbsIdleTime, and then click Modify.
  6. In the Value data box, type 5, and then click OK.

    Note
    The range of values is from 5 to 60.
  7. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\Oakley
  8. On the Edit menu, point to New, and then click DWORD Value.
  9. Type NlbsIdle, and then press ENTER.
  10. Right-click NlbsIdle, and then click Modify.
  11. In the Value data box, type 1, and then click OK.
  12. Exit Registry Editor.
After you install the hotfix package, you must create the following registry subkey on the client computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IKEEXT\Parameters\NlbsIdleTime
To do this, follow these steps:
  1. Click Start, click Run, type Regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IKEEXT\Parameters\
  3. In the Edit menu, point to New, and then click DWORD Value.
  4. Type NlbsIdleTime, and then press ENTER.
  5. Right-click NlbsIdleTime, and then click Modify.
  6. In the Value data box, type a value between five and 60, and then click OK.


Note This value governs the quick mode SA idle time-out limit for SAs to cluster peers that are identified by the Network Load Balancing (NLB) vendor ID. This value also determines whether the hotfix is enabled or not. Without this registry entry setting, the changes in the hotfix are not enabled.

After the quick mode SA times out, the client computer tries another quick mode negotiation two times in a period of three seconds. If the quick mode negotiations fail, a main mode negotiation is tried. This behavior works for usual cluster node migration scenarios, and the failover time is about 15 seconds. However, the Server node may not actually crash. For example, the server node may be busy, or there may be heavy network traffic. Therefore, the Server node cannot respond. In these situations, a fresh main mode negotiation is an additional overhead. If you encounter this issue, you may increase the duration of the quick mode negotiation attempts to a value greater than the default three seconds. To do this, configure the following registry entry. Without the following registry entry, the default value of three seconds is applied.

To create the following registry entry if you have to increase the QM retransmission duration, follow these steps:
  1. Click Start, click Run, type Regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IKEEXT\Parameters\
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type NlbsQMRetransmitDuration, and then press ENTER.
  5. Right-click NlbsQMRetransmitDuration, and then click Modify.
  6. In the Value data box, type a value between three and 60 and then click OK.


Note You must make sure that the following registry subkeys exist on all Windows Server based cluster nodes and that the value of the registry subkey is 1 when you create an IPSec connection to a cluster node. This enables the client computers to identify the connection to a cluster resource.

For Windows Server 2003-based cluster nodes or non-cluster servers:

Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\Oakley\

Name: nlbsflags

Type: REG_DWORD

Value: 1

For Windows Server 2008-based or Windows Server 2008 R2-based cluster nodes or non-cluster servers:

Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IKEEXT\Parameters\

Name: nlbsflags

Type: REG_DWORD

Value: 1

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 Server 2003 file information notes
  • In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipsec.sys5.2.3790.479882,94412-Nov-201014:57x86SP2SP2QFE
Oakley.dll5.2.3790.4798352,76815-Nov-201008:55x86SPSP2QFE
For all supported x64-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipsec.sys5.2.3790.4798157,18415-Nov-201006:41x64SP2SP2QFE
Oakley.dll5.2.3790.4798394,75215-Nov-201006:41x64SPSP2QFE
Woakley.dll5.2.3790.4798352,76815-Nov-201006:41x86SP2SP2QFE\WOW
For all supported IA-64-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipsec.sys5.2.3790.4798259,58415-Nov-201006:41IA-64SP2SP2QFE
Oakley.dll5.2.3790.4798550,40015-Nov-201006:41IA-64SPSP2QFE
Woakley.dll5.2.3790.4798352,76815-Nov-201006:41x86SP2SP2QFE\WOW
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and 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 Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.0.6002.22643334,84816-May-201114:55x86
Fwpkclnt.sys6.0.6002.2264398,19216-May-201120:20x86
Fwpuclnt.dll6.0.6002.22643596,48016-May-201114:57x86
Ikeext.dll6.0.6002.22643439,29616-May-201114:57x86
Wfp.mofNot applicable81415-Mar-201106:00Not applicable
Wfp.tmfNot applicable208,96616-May-201113:14Not applicable
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.0.6002.22643458,24016-May-201115:27x64
Fwpkclnt.sys6.0.6002.22643165,26416-May-201120:17x64
Fwpuclnt.dll6.0.6002.22643781,82416-May-201115:28x64
Ikeext.dll6.0.6002.22643455,68016-May-201115:28x64
Wfp.mofNot applicable81415-Mar-201105:02Not applicable
Wfp.tmfNot applicable207,58316-May-201113:52Not applicable
Fwpuclnt.dll6.0.6002.22643596,48016-May-201114:57x86
Wfp.mofNot applicable81415-Mar-201106:00Not applicable
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.0.6002.22643781,31216-May-201115:24IA-64
Fwpkclnt.sys6.0.6002.22643261,00816-May-201120:17IA-64
Fwpuclnt.dll6.0.6002.226431,124,35216-May-201115:26IA-64
Ikeext.dll6.0.6002.22643927,74416-May-201115:26IA-64
Wfp.mofNot applicable81415-Mar-201105:52Not applicable
Wfp.tmfNot applicable207,99716-May-201114:04Not applicable
Fwpuclnt.dll6.0.6002.22643596,48016-May-201114:57x86
Wfp.mofNot applicable81415-Mar-201106:00Not applicable
Windows 7 and Windows Server 2008 R2 file information notes
  • 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:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.16xxxWindows 7 and Windows Server 2008 R2RTMGDR
    6.1.760 0.20xxxWindows 7 and Windows Server 2008 R2RTMLDR
    6.1.760 1.17xxxWindows 7 and Windows Server 2008 R2SP1GDR
    6.1.760 1.21xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7600.20967495,61614-May-201106:31x86
Fwpuclnt.dll6.1.7600.16385216,57614-Jul-200901:15x86
Ikeext.dll6.1.7600.20967670,20814-May-201106:32x86
Networksecurity-ppdlic.xrm-msNot applicable3,02814-May-201106:40Not applicable
Nshwfp.dll6.1.7600.20967657,92014-May-201106:32x86
Wfp.mofNot applicable82210-Jun-200921:32Not applicable
Bfe.dll6.1.7601.21728496,12814-May-201107:38x86
Fwpuclnt.dll6.1.7601.17514216,57620-Nov-201012:19x86
Ikeext.dll6.1.7601.21728674,81614-May-201107:40x86
Networksecurity-ppdlic.xrm-msNot applicable3,02814-May-201107:54Not applicable
Nshwfp.dll6.1.7601.21728657,92014-May-201107:43x86
Wfp.mofNot applicable82210-Jun-200921:32Not applicable
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7600.20967705,02414-May-201107:32x64
Fwpuclnt.dll6.1.7600.16385324,09614-Jul-200901:40x64
Ikeext.dll6.1.7600.20967848,89614-May-201107:34x64
Networksecurity-ppdlic.xrm-msNot applicable3,02814-May-201107:54Not applicable
Nshwfp.dll6.1.7600.20967832,00014-May-201107:37x64
Wfp.mofNot applicable82210-Jun-200920:51Not applicable
Bfe.dll6.1.7601.21728706,56014-May-201107:11x64
Fwpuclnt.dll6.1.7601.21728324,09614-May-201107:11x64
Ikeext.dll6.1.7601.21728854,01614-May-201107:11x64
Networksecurity-ppdlic.xrm-msNot applicable3,02814-May-201107:20Not applicable
Nshwfp.dll6.1.7601.21728832,00014-May-201107:11x64
Wfp.mofNot applicable82210-Jun-200920:51Not applicable
Fwpuclnt.dll6.1.7600.20967216,57614-May-201106:31x86
Nshwfp.dll6.1.7600.20967657,92014-May-201106:32x86
Wfp.mofNot applicable82222-Jul-200923:17Not applicable
Fwpuclnt.dll6.1.7601.21728216,57614-May-201107:40x86
Nshwfp.dll6.1.7601.21728657,92014-May-201107:43x86
Wfp.mofNot applicable82212-Nov-201023:57Not applicable
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7600.209671,074,17614-May-201106:19IA-64
Fwpuclnt.dll6.1.7600.20967566,27214-May-201106:19IA-64
Ikeext.dll6.1.7600.209671,475,07214-May-201106:19IA-64
Networksecurity-ppdlic.xrm-msNot applicable3,02814-May-201106:28Not applicable
Nshwfp.dll6.1.7600.209671,114,11214-May-201106:19IA-64
Wfp.mofNot applicable82210-Jun-200920:57Not applicable
Bfe.dll6.1.7601.217281,074,17614-May-201106:14IA-64
Fwpuclnt.dll6.1.7601.21728566,27214-May-201106:14IA-64
Ikeext.dll6.1.7601.217281,485,31214-May-201106:14IA-64
Networksecurity-ppdlic.xrm-msNot applicable3,02814-May-201106:23Not applicable
Nshwfp.dll6.1.7601.217281,114,11214-May-201106:14IA-64
Wfp.mofNot applicable82210-Jun-200920:57Not applicable
Fwpuclnt.dll6.1.7600.20967216,57614-May-201106:31x86
Nshwfp.dll6.1.7600.20967657,92014-May-201106:32x86
Wfp.mofNot applicable82222-Jul-200923:17Not applicable
Fwpuclnt.dll6.1.7601.21728216,57614-May-201107:40x86
Nshwfp.dll6.1.7601.21728657,92014-May-201107:43x86
Wfp.mofNot applicable82212-Nov-201023:57Not applicable

STATUS

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

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, click the following article number to view the article in the Microsoft Knowledge Base:
306677 IPsec failover can take up to six minutes in Windows 2000

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot applicable
File size3,068
Date (UTC)16-May-2011
Time (UTC)20:32
PlatformNot applicable
File nameX86_9def770d6cb4d8fccd502f7ad77f2bf2_31bf3856ad364e35_6.0.6002.22643_none_4bed0c4d82185f58.manifest
File versionNot applicable
File size704
Date (UTC)16-May-2011
Time (UTC)20:32
PlatformNot applicable
File nameX86_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_cf6c4efa40ec71f8.manifest
File versionNot applicable
File size131,815
Date (UTC)16-May-2011
Time (UTC)20:33
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_43a65a9765004b8dbf7b2c684e0fd221_31bf3856ad364e35_6.0.6002.22643_none_870c77295a061cfb.manifest
File versionNot applicable
File size1,058
Date (UTC)16-May-2011
Time (UTC)20:32
PlatformNot applicable
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_2b8aea7df949e32e.manifest
File versionNot applicable
File size131,861
Date (UTC)16-May-2011
Time (UTC)20:33
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,092
Date (UTC)16-May-2011
Time (UTC)20:32
PlatformNot applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_35df94d02daaa529.manifest
File versionNot applicable
File size71,155
Date (UTC)16-May-2011
Time (UTC)15:04
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameIa64_e4c1dfe5783f649a50627cfde2802502_31bf3856ad364e35_6.0.6002.22643_none_4572d09ea0e75408.manifest
File versionNot applicable
File size1,056
Date (UTC)16-May-2011
Time (UTC)20:32
PlatformNot applicable
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_cf6df2f040ea7af4.manifest
File versionNot applicable
File size131,838
Date (UTC)16-May-2011
Time (UTC)20:33
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,247
Date (UTC)16-May-2011
Time (UTC)20:32
PlatformNot applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_35df94d02daaa529.manifest
File versionNot applicable
File size71,155
Date (UTC)16-May-2011
Time (UTC)15:04
PlatformNot applicable

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot applicable
File size2,765
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameX86_1d330d07311cda794e4e6886774aeb14_31bf3856ad364e35_6.1.7601.21728_none_54cb5f0afa722f8c.manifest
File versionNot applicable
File size704
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameX86_b061f1001e89e7bfcab23756ab805ad4_31bf3856ad364e35_6.1.7600.20967_none_ef3318e16a28558a.manifest
File versionNot applicable
File size704
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameX86_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_cd9c0cc1a4e9f9d3.manifest
File versionNot applicable
File size158,590
Date (UTC)14-May-2011
Time (UTC)10:47
PlatformNot applicable
File nameX86_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_cfaea9c1a1ef0f52.manifest
File versionNot applicable
File size158,590
Date (UTC)14-May-2011
Time (UTC)10:47
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_19ffb0dc65bc45e2ca60ab390e6f1dc3_31bf3856ad364e35_6.1.7601.21728_none_bf5de1bd4f36e042.manifest
File versionNot applicable
File size1,058
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameAmd64_2a318c26d6d7b8ab96ed82d6f8436a0e_31bf3856ad364e35_6.1.7600.20967_none_e54a60f733b6887e.manifest
File versionNot applicable
File size1,058
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameAmd64_7d09f24a0a247e10b8702b8cadec128d_31bf3856ad364e35_6.1.7600.20967_none_5092f0f978bf8868.manifest
File versionNot applicable
File size708
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameAmd64_86f0c9fa804db97bfdedba81c2a7976f_31bf3856ad364e35_6.1.7601.21728_none_d923e6a7a003e821.manifest
File versionNot applicable
File size708
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_29baa8455d476b09.manifest
File versionNot applicable
File size158,596
Date (UTC)14-May-2011
Time (UTC)10:52
PlatformNot applicable
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_2bcd45455a4c8088.manifest
File versionNot applicable
File size154,588
Date (UTC)14-May-2011
Time (UTC)08:45
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,207
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_340f529791a82d04.manifest
File versionNot applicable
File size94,348
Date (UTC)14-May-2011
Time (UTC)06:49
PlatformNot applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_3621ef978ead4283.manifest
File versionNot applicable
File size94,348
Date (UTC)14-May-2011
Time (UTC)08:03
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_54f613158183e569de3e08468add89c0_31bf3856ad364e35_6.1.7601.21728_none_c16b8bdc86263972.manifest
File versionNot applicable
File size1,056
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameIa64_d600ab5e3f649d26bae79b6e37d10311_31bf3856ad364e35_6.1.7600.20967_none_1bc281fd28b20ae7.manifest
File versionNot applicable
File size1,056
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_cd9db0b7a4e802cf.manifest
File versionNot applicable
File size154,585
Date (UTC)14-May-2011
Time (UTC)07:56
PlatformNot applicable
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_cfb04db7a1ed184e.manifest
File versionNot applicable
File size154,585
Date (UTC)14-May-2011
Time (UTC)08:52
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,160
Date (UTC)14-May-2011
Time (UTC)10:39
PlatformNot applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_340f529791a82d04.manifest
File versionNot applicable
File size94,348
Date (UTC)14-May-2011
Time (UTC)06:49
PlatformNot applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_3621ef978ead4283.manifest
File versionNot applicable
File size94,348
Date (UTC)14-May-2011
Time (UTC)08:03
PlatformNot applicable

Properties

Article ID: 980915 - Last Review: July 4, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Windows Vista Business
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise
  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Ultimate
  • Windows Vista Ultimate 64-bit Edition
  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Foundation
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 Standard
  • Windows Server 2008 Standard without Hyper-V
  • Windows Web Server 2008
  • Windows Web Server 2008 R2
Keywords: 
kbqfe kbfix kbhotfixserver kbsurveynew kbexpertiseinter kbautohotfix KB980915

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com