An updated Storport storage driver (version 5.2.3790.2630) is available for Windows Server 2003

When you use the Microsoft Storport storage driver for host bus adapter (HBA) removable storage, you may experience one or more of the following symptoms:

• Symptom 1
  The Storport storage driver incorrectly handles inquiry page 0x83 data. Therefore, the driver does not detect that a device has changed. You may eventually receive a Stop error message on a blue screen.
  
  Note For more information about when Symptom 1 occurs, see the "More Information" section.
• Symptom 2
  The Storport storage driver does not detect a new device that replaces a device that has been removed.
  
  Note For more information about when Symptom 2 occurs, see the "More Information" section.
• Symptom 3
  When you remove a cable from one of the HBA paths in a Microsoft Multipath I/O (MPIO) environment, a cleanup of the logical unit numbers (LUNs) that are associated with that HBA path may not occur. When a subsequent operation occurs to access the disconnected path, the computer may stop responding.
• Symptom 4
  A memory leak may occur when a new inquiry operation causes a new allocation to be created. The allocation is not freed, and a leak of 512 bytes per inquiry occurs. This leak can cause non-paged pool memory to become exhausted. When a memory leaks occurs, you may receive various error messages. Additionally, the computer may perform poorly or stop responding.

An updated Storport storage driver (version 5.2.3790.2630) is available to resolve these problems. This version of the Storport storage driver introduces new interfaces. Contact Microsoft directly for more information about the new interfaces and about other changes. For Windows Server 2003 Service Pack 1 or x64-based versions of Windows Server 2003, this hotfix is replaced by hotfix 916048 (version 5.2.3790.2723).

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Update 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 this specific problem. 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: 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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update replaces hotfix 908980.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

Symptom 1 scenario

The Storport storage driver incorrectly handles inquiry page 0x83 data. Therefore, the driver does not detect that a device has changed. The problem occurs in the following scenario:

1. Disk A is exposed as LUN 1 TARGET 1 BUS 1.
2. Disk A is replaced by Disk B.
3. Disk B also uses LUN 1 TARGET 1 BUS 1.

Symptom 2 scenario

The Storport storage driver does not detect a new device that replaces a device that has been removed. This problem occurs in the following scenario:

1. Disk A is replaced by Disk B.
2. Disk B uses the same LUN TARGET and BUS ID as Disk A used.
3. The Storport storage driver detects that Disk A has been removed. However, the driver may not detect Disk B until another rescan occurs.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Technical support for x64-based versions of Microsoft Windows

Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site: