I/O operations time out for files that are stored on offline storage in Windows 8 and Windows Server 2012

This hotfix is also available at Microsoft Update Catalog.

To resolve the issue, apply the hotfix on the SMB server. After you apply the hotfix, the I/O operations are processed asynchronously. You must modify the ExtendedSessTimeout registry entry on the SMB client to extend time-out for asynchronous requests. Additionally, we recommend that you increase the value of the AsynchronousCredits registry entry on the SMB server. For more information, see 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 Windows 8 or Windows Server 2012.

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

To modify the ExtendedSessTimeout registry entry on the SMB client, follow these steps:

1. Start Registry Editor.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
3. In the details pane, double-click the ExtendedSessTimeout entry.
4. In the Value data box, enter the time-out period for asynchronous operations.
   
   Type: DWORD
   Value: time-delay in seconds
   Default value: 240

 If the ExtendedSessTimeout registry entry does not exist, create it. You may start by doubling the default value.

To modify the AsynchronousCredits registry entry on the SMB server to which this hotfix has been applied, follow these steps:

1. Start Registry Editor.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
3. In the details pane, double-click the AsynchronousCredits entry.
4. In the Value data box, enter the maximum number of concurrent asynchronous operations.
   

The value type of this entry is REG_DWORD. The value data of this entry is decimal, and is the maximum number of concurrent SMB requests. If the AsynchronousCredits registry entry does not exist, create it. The default value is 512. This parameter limits the number of concurrent asynchronous SMB commands that are allowed on a single connection. Some file clients such as IIS servers require a large amount of concurrency, particularly with file change notification requests. The value of this entry can be increased to support these clients. You may start by doubling the default value.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.