A USB device may no longer work correctly after Windows Vista resumes from sleep or from hibernation

Support for Windows Vista without any service packs installed ended on April 13, 2010. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows


After you resume a Windows Vista-based computer from sleep or from hibernation, or after you restart the computer, some devices may no longer work correctly. For example, you may experience any of the following symptoms:
  • A device, such as a USB IR receiver, does not resume correctly. When this problem occurs, an associated device, such as the Windows Media Center IR remote control, is unavailable.
  • Windows Vista does not detect some USB devices. The USB devices do not work.
  • A USB device, such as a fingerprint reader, is not immediately available. For example, it may take 30 seconds for a device to become available after the Welcome screen appears.
  • USB docking stations that have multiple interfaces and that are connected through USB do not function correctly after Windows Vista resumes from sleep or from hibernation. This problem also occurs after you restart the computer. When this problem occurs, yellow exclamation points appear in Device Manager for the USB docking stations.


Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
Note After you apply the service pack, follow the instructions in the "Post-installation instructions" section. The registry information change may need to be added even after customers have applied Windows Vista Service Pack 1 (SP1). This registry change is not included in Windows Vista SP1 even though the hotfix is included in the service pack. Therefore, some customers may still see this issue after they apply the service pack.

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 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.

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 Vista, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Update.mumNot applicable2,03006-Mar-200721:22Not applicable
Usbd.sys6.0.6000.205505,88806-Mar-200702:08Not applicable
X86_usbport.inf_31bf3856ad364e35_6.0.6000.20550_none_bc2faa301fad4196.manifestNot applicable5,38606-Mar-200721:23Not applicable
Windows Vista, 64-bit versions
File nameFile versionFile sizeDateTimePlatform
Amd64_usbport.inf_31bf3856ad364e35_6.0.6000.20550_none_184e45b3d80ab2cc.manifestNot applicable5,38806-Mar-200721:32Not applicable
Update.mumNot applicable2,03006-Mar-200721:22Not applicable

Post-installation instructions

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
After you install this hotfix or a later USB-based hotfix, a different USB device may no longer work after Windows Vista resumes from sleep or from hibernation. For example, the different device might be an integrated USB device. To resolve this problem, you must first use Device Manager to determine the specific USB host controller that is controlling the integrated USB device that is failing. Then, you must add the ForceHCResetOnResume entry to the registry subkey that corresponds to the USB host controller.

Step 1: Determine the specific USB host controller

  1. Click Start, type
    devmgmt.msc in the Start Search box, and then click devmgmt.msc in the Programslist.
  2. On the View menu, click Devices by connection.
  3. Expand the processor node. For example, expand ACPI Multiprocessor PC.

    Note The node names in this procedure vary depending on the hardware.
  4. Expand Microsoft ACPI-Compliant System.
  5. Expand PCI Bus. Several USB host controllers will be listed.
  6. Expand each USB host controller node, and then expand successive subnodes until you find the name of the device that is failing. For example, the device entry may resemble the following:
    ACPI Multiprocessor PC\Microsoft ACPI-Compliant System\PCI Bus\Intel(R) ICH8 Family USB Universal Host Controller - 2830\USB Root Hub\fingerprint reader
    • The fingerprint reader is typically listed as a biometric device.
    • The specific USB host controller should not be used to control any externally available USB ports. For example, only internal integrated USB devices should be listed under the USB Root Hub node for the specific USB host controller.
  7. When you have located the device, right-click the associated USB host controller, and then click
    Properties. In the example that is listed in step 1.f, right-click Intel(R) ICH8 Family USB Universal Host Controller - 2830, and then click Properties.
  8. Click the Details tab.
  9. Select Driver key in the list.
  10. The driver key will resemble the following. Note the last four digits of this driver key.

Step 2: Add the ForceHCResetOnResume registry value for the USB host controller

  1. Click Start, type
    regedit in the Start Search box, and then click regedit.exe in the Programslist.
  2. Locate and then click registry subkeys that resemble the following:
    • In this step, Four-digit_number is a placeholder for the USB devices in the system.
    • In this step, you must locate the registry subkey by using the value that you noted in Step 1.j. For example, if the driver key from Step 1.j is {36fc9e60-c465-11cf-8056-444553540000}\0002, then you must look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0002
  3. On the Edit menu, point to
    New, and then click DWORD Value.
  4. Type ForceHCResetOnResume for the name of the DWORD, and then press ENTER.
  5. Right-click ForceHCResetOnResume, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.
  8. Restart the computer.


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 Vista Service Pack 1.

More Information

For more information, 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