USB 2.0 high-speed devices are recognized as full-speed after you hibernate and then resume a computer that is running Windows Vista or Windows Server 2008

Assume you connect a high-speed USB 2.0 device to a computer that is running Windows Vista or Windows Server 2008. After you put the computer into hibernation and then resume the computer, the USB 2.0 device is recognized incorrectly as a full-speed device instead of a high-speed device. Therefore, the transmission speed over the USB connection is significantly reduced.

This problem occurs occasionally.

A race condition in the host controller startup sequence causes a short reset signal that a USB 2.0 device may interpret incorrectly. This behavior causes the high-speed handshake for the device to fail. Therefore, the device stops trying to make a high-speed connection.

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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: 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 on a computer that is running Windows Vista, you must have Windows Vista Service Pack 1 or Windows Vista Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base: No prerequisites are required for computers that are running Windows Server 2008.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The global 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 Vista and Windows Server 2008 file information notes

• 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.
  Collapse this tableExpand this table

  Version	Product	SR_Level	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista and Windows Server 2008	SP1	GDR
  6.0.6001.22xxx	Windows Vista and Windows Server 2008	SP1	LDR
  6.0.6002.18xxx	Windows Vista and Windows Server 2008	SP2	GDR
  6.0.6002.22xxx	Windows Vista and Windows Server 2008	SP2	LDR

• Service Pack 1 is integrated into the original release of Windows Server 2008.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

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

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

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

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