Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a
reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation.
Read full disclaimer for more details.
- Home
- USB 3.0 hub is indefinitely powered on and then off after a device causes an overcurrent condition in Windows 8
USB 3.0 hub is indefinitely powered on and then off after a device causes an overcurrent condition in Windows 8
View products that this article applies to.
Assume that you connect a USB 3.0 hub to the downstream port of a USB 3.0 root hub on a computer that is running Windows 8. Then, you connect a broken device to the downstream USB 3.0 hub. When the device causes an overcurrent condition, the downstream USB 3.0 hub is indefinitely powered on and then off.
Notes- This issue continues until you disconnect the device.
- The power cycle repeats in a short time interval. Therefore, the device always seems to be powered on.
↑ Back to the top
This issue occurs because the USB 3.0 xHCI driver automatically repowers the USB 3.0 port.
↑ Back to the top
Update information
To resolve this issue, install update rollup 2889784. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:
2889784 Windows RT, Windows 8, and Windows Server 2012 update rollup: November 2013
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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 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 Windows 8.
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You may be prompted to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 8 file information notes
- The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
| Version | Product | Milestone | Service branch |
|---|
| 6.2.920 0.16 xxx | Windows 8 | RTM | GDR |
| 6.2.920 0.20 xxx | Windows 8 | RTM | LDR |
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8
| File name | File version | File size | Date (UTC) | Time (UTC) | Platform |
|---|
| Usbhub3.sys | 6.2.9200.16728 | 362,840 | 2-Oct-13 | 0:38 | x86 |
| Usbhub3.sys | 6.2.9200.20839 | 362,840 | 2-Oct-13 | 0:37 | x86 |
For all supported x64-based versions of Windows 8
| File name | File version | File size | Date (UTC) | Time (UTC) | Platform |
|---|
| Usbhub3.sys | 6.2.9200.16728 | 447,320 | 2-Oct-13 | 2:50 | x64 |
| Usbhub3.sys | 6.2.9200.20839 | 447,320 | 2-Oct-13 | 2:53 | x64 |
↑ Back to the top
Additional file information
Additional file information for Windows 8
Additional files for all supported x86-based versions of Windows 8
| File property | Value |
|---|
| File name | X86_usbhub3.inf_31bf3856ad364e35_6.2.9200.16728_none_f2d074311e38437c.manifest |
| File version | Not applicable |
| File size | 2,104 |
| Date (UTC) | 02-Oct-2013 |
| Time (UTC) | 00:43 |
| Platform | Not applicable |
| File name | X86_usbhub3.inf_31bf3856ad364e35_6.2.9200.20839_none_f350415a375d188e.manifest |
| File version | Not applicable |
| File size | 2,104 |
| Date (UTC) | 02-Oct-2013 |
| Time (UTC) | 00:46 |
| Platform | Not applicable |
Additional files for all supported x64-based versions of Windows 8
| File property | Value |
|---|
| File name | Amd64_usbhub3.inf_31bf3856ad364e35_6.2.9200.16728_none_4eef0fb4d695b4b2.manifest |
| File version | Not applicable |
| File size | 2,108 |
| Date (UTC) | 02-Oct-2013 |
| Time (UTC) | 02:54 |
| Platform | Not applicable |
| File name | Amd64_usbhub3.inf_31bf3856ad364e35_6.2.9200.20839_none_4f6edcddefba89c4.manifest |
| File version | Not applicable |
| File size | 2,108 |
| Date (UTC) | 02-Oct-2013 |
| Time (UTC) | 02:57 |
| Platform | Not applicable |
↑ Back to the top
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
↑ Back to the top
Keywords: kb, kbqfe, kbhotfixserver, kbfix, kbautohotfix, kbexpertiseadvanced, kbsurveynew
↑ Back to the top