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.

Cause

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

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 system

Update

All supported x86-based versions of Windows 8.1

Download 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 R2

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

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.

Status

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

References

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

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.

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.3.960 0.18 xxx

    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

    RTM

    GDR

  • 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 name

File version

File size

Date

Time

Platform

Usbd.sys

6.3.9600.18088

23,896

11-Oct-2015

06:39

x86

Usbehci.sys

6.3.9600.18191

75,096

09-Jan-2016

01:42

x86

Usbhub.sys

6.3.9600.18088

378,712

11-Oct-2015

06:39

x86

Usbohci.sys

6.3.9600.18088

22,016

10-Oct-2015

17:36

x86

Usbport.sys

6.3.9600.18088

382,808

11-Oct-2015

06:39

x86

Usbuhci.sys

6.3.9600.18088

26,112

10-Oct-2015

17:36

x86

Windows RT 8.1

File name

File version

File size

Date

Time

Platform

Usbd.sys

6.3.9600.18088

25,440

11-Oct-2015

06:45

Not applicable

Usbehci.sys

6.3.9600.18191

73,056

09-Jan-2016

01:48

Not applicable

Usbhub.sys

6.3.9600.18088

321,888

11-Oct-2015

06:45

Not applicable

Usbport.sys

6.3.9600.18088

369,504

11-Oct-2015

06:45

Not applicable

x64 Windows 8.1 and Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Usbd.sys

6.3.9600.18088

27,992

11-Oct-2015

06:34

x64

Usbehci.sys

6.3.9600.18191

91,992

09-Jan-2016

01:38

x64

Usbhub.sys

6.3.9600.18088

462,168

11-Oct-2015

06:34

x64

Usbohci.sys

6.3.9600.18088

30,208

10-Oct-2015

18:41

x64

Usbport.sys

6.3.9600.18088

443,224

11-Oct-2015

06:34

x64

Usbuhci.sys

6.3.9600.18088

37,376

10-Oct-2015

18:41

x64


x86 Windows 8.1

File property

Value

File name

Update.mum

File version

Not applicable

File size

1,798

Date (UTC)

09-Jan-2016

Time (UTC)

01:49

Platform

Not applicable

File name

X86_usbport.inf_31bf3856ad364e35_6.3.9600.18191_none_525421d41f323f74.manifest

File version

Not applicable

File size

6,164

Date (UTC)

09-Jan-2016

Time (UTC)

01:52

Platform

Not applicable

Windows RT 8.1

File property

Value

File name

Arm_usbport.inf_31bf3856ad364e35_6.3.9600.18191_none_5256942c1f2f5e3a.manifest

File version

Not applicable

File size

4,538

Date (UTC)

09-Jan-2016

Time (UTC)

01:49

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,797

Date (UTC)

09-Jan-2016

Time (UTC)

01:49

Platform

Not applicable

x64 Windows 8.1 and Windows Server 2012 R2

File property

Value

File name

Amd64_usbport.inf_31bf3856ad364e35_6.3.9600.18191_none_ae72bd57d78fb0aa.manifest

File version

Not applicable

File size

6,168

Date (UTC)

09-Jan-2016

Time (UTC)

01:56

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,028

Date (UTC)

09-Jan-2016

Time (UTC)

01:49

Platform

Not applicable


More Information

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×