Delay in accessing a file server when a Windows 7-based computer connects to the file server

Applies to: Windows Server 2008 R2 Service Pack 1Windows Server 2008 R2 DatacenterWindows Server 2008 R2 Enterprise More

Symptoms


Consider the following scenario:
  • You have a client computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
  • You connect the client computer to a file server that is running Windows Server 2012 or Windows Server 2012 R2.
  • You connect the client computer to the file server again by using a different universal naming convention (UNC) path.
In this scenario, when other client computers try to access the same file server, they may encounter a delay.

Cause


This issue occurs because the Windows 7-based client computer uses the same client ID for the connections that use different UNC paths. Then, the file server cannot identify the appropriate connection to send an oplock break request.

Resolution


To resolve this issue, we have released a security update and a hotfix package for Windows 7 or Windows Server 2008 R2.

Note
You should only install this hotfix on the Windows 7-based client computer.

Before you install the hotfix, check the Prerequisites section in this article.

Get the update for Windows 7 and Windows Server 2008 R2

To resolve this issue, install the security update 3000483 that is documented in security bulletin MS15-011.

Get the hotfix for Windows 7 and Windows Server 2008 R2

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, go to the following Microsoft website: 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 Service Pack 1 for Windows 7 or for Windows Server 2008 R2.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

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.

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, see the standard terminology that is used to describe Microsoft software updates.