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\NlbsIdleOr, 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\NlbsQMRetransmitDurationTo 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=supportNote 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 WindowsAfter 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\NlbsIdleTimeTo 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

File name

File version

File size

Date

Time

Platform

SP requirement

Service branch

Ipsec.sys

5.2.3790.4798

82,944

12-Nov-2010

14:57

x86

SP2

SP2QFE

Oakley.dll

5.2.3790.4798

352,768

15-Nov-2010

08:55

x86

SP

SP2QFE

For all supported x64-based versions of Windows Server 2003

File name

File version

File size

Date

Time

Platform

SP requirement

Service branch

Ipsec.sys

5.2.3790.4798

157,184

15-Nov-2010

06:41

x64

SP2

SP2QFE

Oakley.dll

5.2.3790.4798

394,752

15-Nov-2010

06:41

x64

SP

SP2QFE

Woakley.dll

5.2.3790.4798

352,768

15-Nov-2010

06:41

x86

SP2

SP2QFE\WOW

For all supported IA-64-based versions of Windows Server 2003

File name

File version

File size

Date

Time

Platform

SP requirement

Service branch

Ipsec.sys

5.2.3790.4798

259,584

15-Nov-2010

06:41

IA-64

SP2

SP2QFE

Oakley.dll

5.2.3790.4798

550,400

15-Nov-2010

06:41

IA-64

SP

SP2QFE

Woakley.dll

5.2.3790.4798

352,768

15-Nov-2010

06:41

x86

SP2

SP2QFE\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.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    22xxx

    Windows Vista and Windows Server 2008

    SP2

    LDR

  • 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

File name

File version

File size

Date

Time

Platform

Bfe.dll

6.0.6002.22643

334,848

16-May-2011

14:55

x86

Fwpkclnt.sys

6.0.6002.22643

98,192

16-May-2011

20:20

x86

Fwpuclnt.dll

6.0.6002.22643

596,480

16-May-2011

14:57

x86

Ikeext.dll

6.0.6002.22643

439,296

16-May-2011

14:57

x86

Wfp.mof

Not applicable

814

15-Mar-2011

06:00

Not applicable

Wfp.tmf

Not applicable

208,966

16-May-2011

13:14

Not applicable

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

File name

File version

File size

Date

Time

Platform

Bfe.dll

6.0.6002.22643

458,240

16-May-2011

15:27

x64

Fwpkclnt.sys

6.0.6002.22643

165,264

16-May-2011

20:17

x64

Fwpuclnt.dll

6.0.6002.22643

781,824

16-May-2011

15:28

x64

Ikeext.dll

6.0.6002.22643

455,680

16-May-2011

15:28

x64

Wfp.mof

Not applicable

814

15-Mar-2011

05:02

Not applicable

Wfp.tmf

Not applicable

207,583

16-May-2011

13:52

Not applicable

Fwpuclnt.dll

6.0.6002.22643

596,480

16-May-2011

14:57

x86

Wfp.mof

Not applicable

814

15-Mar-2011

06:00

Not applicable

For all supported IA-64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Bfe.dll

6.0.6002.22643

781,312

16-May-2011

15:24

IA-64

Fwpkclnt.sys

6.0.6002.22643

261,008

16-May-2011

20:17

IA-64

Fwpuclnt.dll

6.0.6002.22643

1,124,352

16-May-2011

15:26

IA-64

Ikeext.dll

6.0.6002.22643

927,744

16-May-2011

15:26

IA-64

Wfp.mof

Not applicable

814

15-Mar-2011

05:52

Not applicable

Wfp.tmf

Not applicable

207,997

16-May-2011

14:04

Not applicable

Fwpuclnt.dll

6.0.6002.22643

596,480

16-May-2011

14:57

x86

Wfp.mof

Not applicable

814

15-Mar-2011

06:00

Not 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:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    0.16xxx

    Windows 7 and Windows Server 2008 R2

    RTM

    GDR

    6.1.760
    0.20xxx

    Windows 7 and Windows Server 2008 R2

    RTM

    LDR

    6.1.760
    1.17xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.21xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • 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

File name

File version

File size

Date

Time

Platform

Bfe.dll

6.1.7600.20967

495,616

14-May-2011

06:31

x86

Fwpuclnt.dll

6.1.7600.16385

216,576

14-Jul-2009

01:15

x86

Ikeext.dll

6.1.7600.20967

670,208

14-May-2011

06:32

x86

Networksecurity-ppdlic.xrm-ms

Not applicable

3,028

14-May-2011

06:40

Not applicable

Nshwfp.dll

6.1.7600.20967

657,920

14-May-2011

06:32

x86

Wfp.mof

Not applicable

822

10-Jun-2009

21:32

Not applicable

Bfe.dll

6.1.7601.21728

496,128

14-May-2011

07:38

x86

Fwpuclnt.dll

6.1.7601.17514

216,576

20-Nov-2010

12:19

x86

Ikeext.dll

6.1.7601.21728

674,816

14-May-2011

07:40

x86

Networksecurity-ppdlic.xrm-ms

Not applicable

3,028

14-May-2011

07:54

Not applicable

Nshwfp.dll

6.1.7601.21728

657,920

14-May-2011

07:43

x86

Wfp.mof

Not applicable

822

10-Jun-2009

21:32

Not applicable

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Bfe.dll

6.1.7600.20967

705,024

14-May-2011

07:32

x64

Fwpuclnt.dll

6.1.7600.16385

324,096

14-Jul-2009

01:40

x64

Ikeext.dll

6.1.7600.20967

848,896

14-May-2011

07:34

x64

Networksecurity-ppdlic.xrm-ms

Not applicable

3,028

14-May-2011

07:54

Not applicable

Nshwfp.dll

6.1.7600.20967

832,000

14-May-2011

07:37

x64

Wfp.mof

Not applicable

822

10-Jun-2009

20:51

Not applicable

Bfe.dll

6.1.7601.21728

706,560

14-May-2011

07:11

x64

Fwpuclnt.dll

6.1.7601.21728

324,096

14-May-2011

07:11

x64

Ikeext.dll

6.1.7601.21728

854,016

14-May-2011

07:11

x64

Networksecurity-ppdlic.xrm-ms

Not applicable

3,028

14-May-2011

07:20

Not applicable

Nshwfp.dll

6.1.7601.21728

832,000

14-May-2011

07:11

x64

Wfp.mof

Not applicable

822

10-Jun-2009

20:51

Not applicable

Fwpuclnt.dll

6.1.7600.20967

216,576

14-May-2011

06:31

x86

Nshwfp.dll

6.1.7600.20967

657,920

14-May-2011

06:32

x86

Wfp.mof

Not applicable

822

22-Jul-2009

23:17

Not applicable

Fwpuclnt.dll

6.1.7601.21728

216,576

14-May-2011

07:40

x86

Nshwfp.dll

6.1.7601.21728

657,920

14-May-2011

07:43

x86

Wfp.mof

Not applicable

822

12-Nov-2010

23:57

Not applicable

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Bfe.dll

6.1.7600.20967

1,074,176

14-May-2011

06:19

IA-64

Fwpuclnt.dll

6.1.7600.20967

566,272

14-May-2011

06:19

IA-64

Ikeext.dll

6.1.7600.20967

1,475,072

14-May-2011

06:19

IA-64

Networksecurity-ppdlic.xrm-ms

Not applicable

3,028

14-May-2011

06:28

Not applicable

Nshwfp.dll

6.1.7600.20967

1,114,112

14-May-2011

06:19

IA-64

Wfp.mof

Not applicable

822

10-Jun-2009

20:57

Not applicable

Bfe.dll

6.1.7601.21728

1,074,176

14-May-2011

06:14

IA-64

Fwpuclnt.dll

6.1.7601.21728

566,272

14-May-2011

06:14

IA-64

Ikeext.dll

6.1.7601.21728

1,485,312

14-May-2011

06:14

IA-64

Networksecurity-ppdlic.xrm-ms

Not applicable

3,028

14-May-2011

06:23

Not applicable

Nshwfp.dll

6.1.7601.21728

1,114,112

14-May-2011

06:14

IA-64

Wfp.mof

Not applicable

822

10-Jun-2009

20:57

Not applicable

Fwpuclnt.dll

6.1.7600.20967

216,576

14-May-2011

06:31

x86

Nshwfp.dll

6.1.7600.20967

657,920

14-May-2011

06:32

x86

Wfp.mof

Not applicable

822

22-Jul-2009

23:17

Not applicable

Fwpuclnt.dll

6.1.7601.21728

216,576

14-May-2011

07:40

x86

Nshwfp.dll

6.1.7601.21728

657,920

14-May-2011

07:43

x86

Wfp.mof

Not applicable

822

12-Nov-2010

23:57

Not 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

File name

Update.mum

File version

Not applicable

File size

3,068

Date (UTC)

16-May-2011

Time (UTC)

20:32

Platform

Not applicable

File name

X86_9def770d6cb4d8fccd502f7ad77f2bf2_31bf3856ad364e35_6.0.6002.22643_none_4bed0c4d82185f58.manifest

File version

Not applicable

File size

704

Date (UTC)

16-May-2011

Time (UTC)

20:32

Platform

Not applicable

File name

X86_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_cf6c4efa40ec71f8.manifest

File version

Not applicable

File size

131,815

Date (UTC)

16-May-2011

Time (UTC)

20:33

Platform

Not applicable

Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008

File name

Amd64_43a65a9765004b8dbf7b2c684e0fd221_31bf3856ad364e35_6.0.6002.22643_none_870c77295a061cfb.manifest

File version

Not applicable

File size

1,058

Date (UTC)

16-May-2011

Time (UTC)

20:32

Platform

Not applicable

File name

Amd64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_2b8aea7df949e32e.manifest

File version

Not applicable

File size

131,861

Date (UTC)

16-May-2011

Time (UTC)

20:33

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

3,092

Date (UTC)

16-May-2011

Time (UTC)

20:32

Platform

Not applicable

File name

Wow64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_35df94d02daaa529.manifest

File version

Not applicable

File size

71,155

Date (UTC)

16-May-2011

Time (UTC)

15:04

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008

File name

Ia64_e4c1dfe5783f649a50627cfde2802502_31bf3856ad364e35_6.0.6002.22643_none_4572d09ea0e75408.manifest

File version

Not applicable

File size

1,056

Date (UTC)

16-May-2011

Time (UTC)

20:32

Platform

Not applicable

File name

Ia64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_cf6df2f040ea7af4.manifest

File version

Not applicable

File size

131,838

Date (UTC)

16-May-2011

Time (UTC)

20:33

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,247

Date (UTC)

16-May-2011

Time (UTC)

20:32

Platform

Not applicable

File name

Wow64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6002.22643_none_35df94d02daaa529.manifest

File version

Not applicable

File size

71,155

Date (UTC)

16-May-2011

Time (UTC)

15:04

Platform

Not applicable

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

Additional files for all supported x86-based versions of Windows 7

File name

Update.mum

File version

Not applicable

File size

2,765

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

X86_1d330d07311cda794e4e6886774aeb14_31bf3856ad364e35_6.1.7601.21728_none_54cb5f0afa722f8c.manifest

File version

Not applicable

File size

704

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

X86_b061f1001e89e7bfcab23756ab805ad4_31bf3856ad364e35_6.1.7600.20967_none_ef3318e16a28558a.manifest

File version

Not applicable

File size

704

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

X86_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_cd9c0cc1a4e9f9d3.manifest

File version

Not applicable

File size

158,590

Date (UTC)

14-May-2011

Time (UTC)

10:47

Platform

Not applicable

File name

X86_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_cfaea9c1a1ef0f52.manifest

File version

Not applicable

File size

158,590

Date (UTC)

14-May-2011

Time (UTC)

10:47

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_19ffb0dc65bc45e2ca60ab390e6f1dc3_31bf3856ad364e35_6.1.7601.21728_none_bf5de1bd4f36e042.manifest

File version

Not applicable

File size

1,058

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

Amd64_2a318c26d6d7b8ab96ed82d6f8436a0e_31bf3856ad364e35_6.1.7600.20967_none_e54a60f733b6887e.manifest

File version

Not applicable

File size

1,058

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

Amd64_7d09f24a0a247e10b8702b8cadec128d_31bf3856ad364e35_6.1.7600.20967_none_5092f0f978bf8868.manifest

File version

Not applicable

File size

708

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

Amd64_86f0c9fa804db97bfdedba81c2a7976f_31bf3856ad364e35_6.1.7601.21728_none_d923e6a7a003e821.manifest

File version

Not applicable

File size

708

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

Amd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_29baa8455d476b09.manifest

File version

Not applicable

File size

158,596

Date (UTC)

14-May-2011

Time (UTC)

10:52

Platform

Not applicable

File name

Amd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_2bcd45455a4c8088.manifest

File version

Not applicable

File size

154,588

Date (UTC)

14-May-2011

Time (UTC)

08:45

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

3,207

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

Wow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_340f529791a82d04.manifest

File version

Not applicable

File size

94,348

Date (UTC)

14-May-2011

Time (UTC)

06:49

Platform

Not applicable

File name

Wow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_3621ef978ead4283.manifest

File version

Not applicable

File size

94,348

Date (UTC)

14-May-2011

Time (UTC)

08:03

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_54f613158183e569de3e08468add89c0_31bf3856ad364e35_6.1.7601.21728_none_c16b8bdc86263972.manifest

File version

Not applicable

File size

1,056

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

Ia64_d600ab5e3f649d26bae79b6e37d10311_31bf3856ad364e35_6.1.7600.20967_none_1bc281fd28b20ae7.manifest

File version

Not applicable

File size

1,056

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

Ia64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_cd9db0b7a4e802cf.manifest

File version

Not applicable

File size

154,585

Date (UTC)

14-May-2011

Time (UTC)

07:56

Platform

Not applicable

File name

Ia64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_cfb04db7a1ed184e.manifest

File version

Not applicable

File size

154,585

Date (UTC)

14-May-2011

Time (UTC)

08:52

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,160

Date (UTC)

14-May-2011

Time (UTC)

10:39

Platform

Not applicable

File name

Wow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.20967_none_340f529791a82d04.manifest

File version

Not applicable

File size

94,348

Date (UTC)

14-May-2011

Time (UTC)

06:49

Platform

Not applicable

File name

Wow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21728_none_3621ef978ead4283.manifest

File version

Not applicable

File size

94,348

Date (UTC)

14-May-2011

Time (UTC)

08:03

Platform

Not applicable

¿Necesita más ayuda?

Ampliar sus conocimientos
Explorar los cursos
Obtener nuevas características primero
Unirse a Microsoft Insider

¿Le ha sido útil esta información?

¿Qué ha afectado a tu experiencia?

¡Gracias por sus comentarios!

×