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. "STATUS_DEVICE_POWER_FAILURE" status for a USB CD/DVD drive in Windows Multipoint Server 2012

"STATUS_DEVICE_POWER_FAILURE" status for a USB CD/DVD drive in Windows Multipoint Server 2012

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a server that is running Windows Multipoint Server 2012 with one or more user stations.
  • You connect a USB CD/DVD drive to one of the stations. The drive can be a self-powered drive or a USB-powered drive.

In this scenario, the drive is not displayed in Windows Explorer. Instead, the drive has exclamation point (!) next to it in Device Manager and shows a status of "STATUS_DEVICE_POWER_FAILURE."

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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 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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
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 have Update Rollup 2  for Windows Multipoint Server 2012 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

File information
The English (United States) 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 and Windows Server 2012 file information and notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • 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.2.920 0.16 xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows 8 and Windows Server 2012RTMLDR
  • 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 and Windows Server 2012" 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 nameFile versionFile sizeDateTimePlatform
Cdrom.sys6.2.9200.16860136,19203-Mar-201423:17x86
Cdrom.sys6.2.9200.20978134,65601-Mar-201407:12x86
Rdpclip.exe6.2.9200.16862258,04805-Mar-201423:42x86
Rdpclip.exe6.2.9200.20981258,04805-Mar-201423:34x86
For all supported x64-based versions of Windows 8 and Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Cdrom.sys6.2.9200.16860173,05603-Mar-201423:18x64
Cdrom.sys6.2.9200.20978173,05601-Mar-201407:31x64
Rdpclip.exe6.2.9200.16862315,90405-Mar-201423:56x64
Rdpclip.exe6.2.9200.20981315,90405-Mar-201423:33x64
For all supported ARM-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Cdrom.sys6.2.9200.16860119,12806-Mar-201400:01Not applicable
Rdpclip.exe6.2.9200.16862233,98405-Mar-201423:31Not applicable

Additional file information for Windows 8 and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File nameX86_07726672ed713221dbc03ab025358168_31bf3856ad364e35_6.2.9200.16862_none_f9bf6e8779fa3634.manifest
File versionNot applicable
File size725
Date (UTC)06-Mar-2014
Time (UTC)11:34
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_cdrom.inf_31bf3856ad364e35_6.2.9200.16862_none_5c681085751fb63e.manifest
File versionNot applicable
File size2,092
Date (UTC)06-Mar-2014
Time (UTC)00:32
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_cdrom.inf_31bf3856ad364e35_6.2.9200.20981_none_5cdb0d2e8e4e7493.manifest
File versionNot applicable
File size2,092
Date (UTC)06-Mar-2014
Time (UTC)00:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_fd3ba28f8022ffd64184fb084c1d4200_31bf3856ad364e35_6.2.9200.20981_none_629139fcc9c00a3f.manifest
File versionNot applicable
File size725
Date (UTC)06-Mar-2014
Time (UTC)11:34
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-t..lipboardredirection_31bf3856ad364e35_6.2.9200.16862_none_fe94c545dc7a76a9.manifest
File versionNot applicable
File size4,426
Date (UTC)05-Mar-2014
Time (UTC)23:56
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-t..lipboardredirection_31bf3856ad364e35_6.2.9200.20981_none_ff07c1eef5a934fe.manifest
File versionNot applicable
File size4,426
Date (UTC)06-Mar-2014
Time (UTC)00:18
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported x64-based versions of Windows 8 and Windows Server 2012
File nameAmd64_136269c02343d68ae065f0d95151e299_31bf3856ad364e35_6.2.9200.20981_none_1cf1c24114a50359.manifest
File versionNot applicable
File size729
Date (UTC)06-Mar-2014
Time (UTC)11:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_4da6a9b1bdfd45cfb7518e0c5d8cee29_31bf3856ad364e35_6.2.9200.16862_none_c31a37588aac2ac7.manifest
File versionNot applicable
File size729
Date (UTC)06-Mar-2014
Time (UTC)11:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_cdrom.inf_31bf3856ad364e35_6.2.9200.16862_none_b886ac092d7d2774.manifest
File versionNot applicable
File size2,096
Date (UTC)06-Mar-2014
Time (UTC)02:37
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_cdrom.inf_31bf3856ad364e35_6.2.9200.20981_none_b8f9a8b246abe5c9.manifest
File versionNot applicable
File size2,096
Date (UTC)06-Mar-2014
Time (UTC)01:55
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-t..lipboardredirection_31bf3856ad364e35_6.2.9200.16862_none_5ab360c994d7e7df.manifest
File versionNot applicable
File size4,430
Date (UTC)06-Mar-2014
Time (UTC)02:37
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-t..lipboardredirection_31bf3856ad364e35_6.2.9200.20981_none_5b265d72ae06a634.manifest
File versionNot applicable
File size4,430
Date (UTC)06-Mar-2014
Time (UTC)02:12
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported ARM-based versions of Windows 8
File nameArm_cdrom.inf_31bf3856ad364e35_6.2.9200.16862_none_5c6a82dd751cd504.manifest
File versionNot applicable
File size2,092
Date (UTC)06-Mar-2014
Time (UTC)01:52
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameArm_d9dc7322715a29283a4e2ae69ca6457b_31bf3856ad364e35_6.2.9200.16862_none_27faa4b4113e0d62.manifest
File versionNot applicable
File size725
Date (UTC)06-Mar-2014
Time (UTC)11:21
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameArm_microsoft-windows-t..lipboardredirection_31bf3856ad364e35_6.2.9200.16862_none_fe97379ddc77956f.manifest
File versionNot applicable
File size4,426
Date (UTC)06-Mar-2014
Time (UTC)02:02
SHA-1 hashNot applicable
MD5 hashNot applicable

↑ 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

Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug, kb

↑ Back to the top

Article Info
Article ID : 2934106
Revision : 1
Created on : 1/7/2017
Published on : 5/27/2014
Exists online : False
Views : 255