Applies ToWindows 7 Enterprise Windows 7 Professional Windows 7 Ultimate Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Standard Windows Server 2008 R2 Web Edition

Symptoms

You have a computer that is running Windows 7 or Windows Server 2008 R2. On this computer, you try to open a Microsoft Office 2003 document from a network share. However, the computer may take four minutes to open the document.This issue occurs only in the first attempt to open an Office 2003 document from the network share during one day. Successive attempts to open Office 2003 documents from that share work fine. Additionally, this issue occurs when the following conditions are true:

  • The Office 2003 document is hosted in a network share on a domain controller.

  • You keep the computer connected to the network share for a long time before you open the Office 2003 document.

Note To reproduce this issue, see the "More information" section.

Resolution

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

There are no prerequisites.

Registry information

To use the hotfix in this package, you do not have to make any changes to the

Restart requirement

You may have to 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 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

Mrxsmb20.sys

6.1.7600.20714

95,744

17-May-2010

22:28

x86

Mrxsmb.sys

6.1.7600.20714

123,904

17-May-2010

22:28

x86

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

File name

File version

File size

Date

Time

Platform

Mrxsmb20.sys

6.1.7600.20714

126,464

17-May-2010

22:53

x64

Mrxsmb.sys

6.1.7600.20714

157,696

17-May-2010

22:53

x64

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

File name

File version

File size

Date

Time

Platform

Mrxsmb20.sys

6.1.7600.20714

305,664

17-May-2010

21:53

IA-64

Mrxsmb.sys

6.1.7600.20714

366,080

17-May-2010

21:53

IA-64

Workaround

Workaround for Windows 7 and for Windows Server 2008 R2

To work around this issue, disable the Server Message Block (SMB) signing through registry keys. To do this, follow these steps:

  • Click Start Start button , type regedit in the Search programs and files box, and then press ENTER.

    • On a server, locate and then click the following registry entry:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters

    • On a client computer, locate and then click the following registry entry:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters

  • Under the registry entry, disable these two registry keys:

    • Right-click Enablesecuritysignature, and then click Modify. Type 0 in the Value data box and then click OK.

    • Right-click Requiresecuritysignature, and then click Modify. Type 0 in the Value data box and then click OK.

Status

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

More Information

Reproduce steps

For example, you may encounter the issue if you follow these steps:

  1. On a computer that is running Windows 7, connect to a network share on a file server. This file server also works as a domain controller.

  2. Open a Microsoft Office Excel 2003 file from the file server.

  3. Close the Excel 2003 file and lock the computer. Keep the computer in running overnight.

  4. Log on to the computer the next morning.

  5. Try to open any Office 2003 file.

In this example, you experience four-minute delay to open the Office 2003 file.For more information about examples about message signing, visit the following Microsoft website:

Message signing examplesFor 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

Additional file information

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

X86_18613395a86229d09e1295e2e80fcaba_31bf3856ad364e35_6.1.7600.20714_none_7f13f9c1c77f1307.manifest

File version

Not applicable

File size

698

Date (UTC)

18-May-2010

Time (UTC)

16:15

Platform

Not applicable

File name

X86_ab0ed5ad8223e31af1ad03694281c339_31bf3856ad364e35_6.1.7600.20714_none_e0a873196f594bcd.manifest

File version

Not applicable

File size

701

Date (UTC)

18-May-2010

Time (UTC)

16:15

Platform

Not applicable

File name

X86_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7600.20714_none_8b859d6603ff30b8.manifest

File version

Not applicable

File size

4,035

Date (UTC)

18-May-2010

Time (UTC)

04:31

Platform

Not applicable

File name

X86_microsoft-windows-smbminirdr_31bf3856ad364e35_6.1.7600.20714_none_803c14ffcb56bee5.manifest

File version

Not applicable

File size

4,757

Date (UTC)

18-May-2010

Time (UTC)

04:16

Platform

Not applicable

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

File name

Amd64_83a422539e29d0f41bea07fa8bfa2085_31bf3856ad364e35_6.1.7600.20714_none_b292d208980befdd.manifest

File version

Not applicable

File size

702

Date (UTC)

18-May-2010

Time (UTC)

16:15

Platform

Not applicable

File name

Amd64_9faac1c9c226641843cf13140e2bf798_31bf3856ad364e35_6.1.7600.20714_none_8b6624ba659459ea.manifest

File version

Not applicable

File size

705

Date (UTC)

18-May-2010

Time (UTC)

16:15

Platform

Not applicable

File name

Amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7600.20714_none_e7a438e9bc5ca1ee.manifest

File version

Not applicable

File size

4,039

Date (UTC)

18-May-2010

Time (UTC)

09:00

Platform

Not applicable

File name

Amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.1.7600.20714_none_dc5ab08383b4301b.manifest

File version

Not applicable

File size

4,761

Date (UTC)

18-May-2010

Time (UTC)

08:51

Platform

Not applicable

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

File name

Ia64_6f715adabc87c2f97a44279053fa1b2f_31bf3856ad364e35_6.1.7600.20714_none_1873b495d284c2e0.manifest

File version

Not applicable

File size

700

Date (UTC)

18-May-2010

Time (UTC)

16:15

Platform

Not applicable

File name

Ia64_932de067902ca87c73235f9097960df8_31bf3856ad364e35_6.1.7600.20714_none_be35aaf898e7bada.manifest

File version

Not applicable

File size

703

Date (UTC)

18-May-2010

Time (UTC)

16:15

Platform

Not applicable

File name

Ia64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7600.20714_none_8b87415c03fd39b4.manifest

File version

Not applicable

File size

4,037

Date (UTC)

18-May-2010

Time (UTC)

04:26

Platform

Not applicable

File name

Ia64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.1.7600.20714_none_803db8f5cb54c7e1.manifest

File version

Not applicable

File size

4,759

Date (UTC)

18-May-2010

Time (UTC)

04:19

Platform

Not applicable

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.