
USB 2.0 issues in Windows 8 on motherboards with Intel 6 Series Chipset
After upgrading to Windows 8, I noticed a strange problem: after sleep mode, and sometimes during a cold start, I could not log in because neither the mouse nor the keyboard functioned! I hasten to disappoint those who are faced with this problem, there is no clear solution yet.
So, the reason was found quite quickly. It turns out that sometimes when the system starts, one or both of the USB 2.0 controllers simply do not function. If you look at the device manager, then one or both of the following devices are stopped (yellow exclamation mark):
Accordingly, none of the connected devices does not function. Interestingly, the problem disappears by itself upon reboot.
At first, I thought that the problem was in the motherboard (ASUS P8P67 Pro), but google suggested that the problem arose not only with me . What is noteworthy, in Windows 7 there is no such problem.
Scrolling through the topic, I found the following solutions to the problem.
I have an additional USB 3.0 controller on my motherboard. Accordingly, the simplest solution is to transfer critical devices to its ports. I personally tried this method, everything works. Unfortunately, USB 3.0 ports are significantly smaller than 2.0.
It is advised to disable USB Legacy Mode in the BIOS. Judging by the topic, not everyone helps, the problem may come back. It didn’t help me.
Or not with everything manually, but with the help of the task scheduler for the inclusion event. To do this, use the devcon tool. The launch line will be something like this:
Adjusted for device ID from device manager.
It is proposed to delete the “LowerFilters” and “UpperFilters” parameters in the registry at.
I have not been tested.
The glitch is unpleasant, although you can live with it. I was about to change the motherboard, but it turned out that the problem is still software. Unfortunately, it is not known whether we will wait for any reaction from Intel or Microsoft, for several driver revisions have already passed, but things are still there.
Problem
So, the reason was found quite quickly. It turns out that sometimes when the system starts, one or both of the USB 2.0 controllers simply do not function. If you look at the device manager, then one or both of the following devices are stopped (yellow exclamation mark):
- Intel® 6 Series / C200 Series Chipset Family USB Enhanced Host Controller - 1C2D
- Intel® 6 Series / C200 Series Chipset Family USB Enhanced Host Controller - 1C26
Accordingly, none of the connected devices does not function. Interestingly, the problem disappears by itself upon reboot.
At first, I thought that the problem was in the motherboard (ASUS P8P67 Pro), but google suggested that the problem arose not only with me . What is noteworthy, in Windows 7 there is no such problem.
Scrolling through the topic, I found the following solutions to the problem.
Use additional controller
I have an additional USB 3.0 controller on my motherboard. Accordingly, the simplest solution is to transfer critical devices to its ports. I personally tried this method, everything works. Unfortunately, USB 3.0 ports are significantly smaller than 2.0.
Disable USB Legacy Mode
It is advised to disable USB Legacy Mode in the BIOS. Judging by the topic, not everyone helps, the problem may come back. It didn’t help me.
Manual restart of the controller
Or not with everything manually, but with the help of the task scheduler for the inclusion event. To do this, use the devcon tool. The launch line will be something like this:
devcon.exe restart "@PCI\VEN_8086&DEV_1C26&SUBSYS_04A91028&REV_04\3&11583659&0&E8"
Adjusted for device ID from device manager.
Registry hack
It is proposed to delete the “LowerFilters” and “UpperFilters” parameters in the registry at.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}
I have not been tested.
Total
The glitch is unpleasant, although you can live with it. I was about to change the motherboard, but it turned out that the problem is still software. Unfortunately, it is not known whether we will wait for any reaction from Intel or Microsoft, for several driver revisions have already passed, but things are still there.