Microsoft KB Archive Search

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.

  1. Home
  2. "Code 10 Device Cannot Start" error for EHCI USB Controller devices in Device Manager in Windows Server 2012 R2

"Code 10 Device Cannot Start" error for EHCI USB Controller devices in Device Manager in Windows Server 2012 R2

View products that this article applies to.

This article describes an issue in which you receive a "Code 10 Device Cannot Start" error message for Enhanced Host Controller Interface (EHCI) USB Controller devices in Device Manager in Windows Server 2012 R2. An update is available to fix this issue. Before you install this update, see the Prerequisites section.

↑ Back to the top

Cause

This issue occurs because a time-out occurs during EHCI hardware initialization.

↑ Back to the top

How to get this update

Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.

Method 1: Windows Update

This update is provided as a Recommended update on Windows Update. For more information on how to run Windows Update, see How to get an update through Windows Update.

Method 2: Microsoft Download Center

The following files are available for download from the Microsoft Download Center:

Operating systemUpdate
All supported x86-based versions of Windows 8.1Download Download the package now.
All supported x64-based versions of Windows 8.1 Download Download the package now.
All supported x64-based versions of Windows Server 2012 R2Download Download the package now.
Note The update for Windows RT 8.1 can be got only from Windows Update.

For more information about how to download Microsoft support files, select the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

↑ Back to the top

Update detail information

Prerequisites

To install this update, install April 2014, update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) in Windows 8.1 or Windows Server 2012 R2.

Registry information

To apply this update, you don't have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this update.

Update replacement information

This update doesn't replace a previously released update.

↑ Back to the top

Status

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

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.
Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2
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:
    VersionProductMilestoneService branch
    6.3.960 0.18 xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.
x86 Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Usbd.sys6.3.9600.1808823,89611-Oct-201506:39x86
Usbehci.sys6.3.9600.1819175,09609-Jan-201601:42x86
Usbhub.sys6.3.9600.18088378,71211-Oct-201506:39x86
Usbohci.sys6.3.9600.1808822,01610-Oct-201517:36x86
Usbport.sys6.3.9600.18088382,80811-Oct-201506:39x86
Usbuhci.sys6.3.9600.1808826,11210-Oct-201517:36x86
Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Usbd.sys6.3.9600.1808825,44011-Oct-201506:45Not applicable
Usbehci.sys6.3.9600.1819173,05609-Jan-201601:48Not applicable
Usbhub.sys6.3.9600.18088321,88811-Oct-201506:45Not applicable
Usbport.sys6.3.9600.18088369,50411-Oct-201506:45Not applicable
x64 Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Usbd.sys6.3.9600.1808827,99211-Oct-201506:34x64
Usbehci.sys6.3.9600.1819191,99209-Jan-201601:38x64
Usbhub.sys6.3.9600.18088462,16811-Oct-201506:34x64
Usbohci.sys6.3.9600.1808830,20810-Oct-201518:41x64
Usbport.sys6.3.9600.18088443,22411-Oct-201506:34x64
Usbuhci.sys6.3.9600.1808837,37610-Oct-201518:41x64
Additional file information
x86 Windows 8.1
File propertyValue
File nameUpdate.mum
File versionNot applicable
File size1,798
Date (UTC)09-Jan-2016
Time (UTC)01:49
PlatformNot applicable
File nameX86_usbport.inf_31bf3856ad364e35_6.3.9600.18191_none_525421d41f323f74.manifest
File versionNot applicable
File size6,164
Date (UTC)09-Jan-2016
Time (UTC)01:52
PlatformNot applicable
Windows RT 8.1
File propertyValue
File nameArm_usbport.inf_31bf3856ad364e35_6.3.9600.18191_none_5256942c1f2f5e3a.manifest
File versionNot applicable
File size4,538
Date (UTC)09-Jan-2016
Time (UTC)01:49
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,797
Date (UTC)09-Jan-2016
Time (UTC)01:49
PlatformNot applicable
x64 Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_usbport.inf_31bf3856ad364e35_6.3.9600.18191_none_ae72bd57d78fb0aa.manifest
File versionNot applicable
File size6,168
Date (UTC)09-Jan-2016
Time (UTC)01:56
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,028
Date (UTC)09-Jan-2016
Time (UTC)01:49
PlatformNot applicable

↑ Back to the top

More Information

This issue occurs because time-out occurs in usbehci.sys when EHCI USB devices call KeQuerySystemTime routine.

↑ Back to the top

Keywords: kbsurveynew, kbfix, kbexpertiseadvanced, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3133924
Revision : 2
Created on : 4/9/2020
Published on : 4/9/2020
Exists online : False
Views : 291