A USB descriptor error occurs during device identification. This guide helps Windows 11 users isolate the connection, accessory and host safely, without confusing the error with ordinary storage or application configuration problems.
What USB Device Descriptor Request Failed Means
When a USB device appears as Unknown USB Device with the explanation Device Descriptor Request Failed, Windows has encountered a problem while trying to identify the connected accessory. You may also see a Code 43 notification in Device Manager. The error affects the connection before ordinary software can use the device reliably. It is particularly confusing when an external drive, webcam or controller lights up as soon as you connect it but remains unavailable to applications.
A USB connection involves a physical connection, power where applicable and an exchange of information between the device and host computer. The host needs basic identifying information before it can configure the accessory properly. A USB device descriptor supplies information such as a vendor identifier, product identifier and supported USB version. Microsoft’s USB device descriptor documentation explains how Windows uses that information. If the required exchange fails, the system may be unable to establish the identity necessary for the normal device configuration.
Consequently, an accessory light does not prove that its data connection is functioning. Similarly, the presence of an unknown USB entry does not establish that the accessory’s usual driver is missing. This guide focuses on the specific descriptor request failure, rather than every possible USB symptom. For a broader investigation, see USB Device Not Recognized Windows 11.
Distinguish Code 43 From Other USB Errors
Code 43 is a general Windows device problem code. It is not exclusive to USB devices and does not identify a particular broken component. The accompanying description, device location and circumstances are important. Microsoft’s Device Manager error reference describes Code 43 as indicating a reported device failure. The descriptor-specific label helps narrow the investigation to a particular stage of USB identification.
| Observation | What To Investigate First |
|---|---|
| Device Descriptor Request Failed | Physical connection, available power, device identification and host communication. |
| Code 43 without a descriptor message | The particular device and complete error description. |
| Code 28 | Whether appropriate device drivers have been installed. |
| Drive appears in Disk Management but not File Explorer | Storage configuration or access issues, rather than assuming identification failed. |
| No response to connection | Connector, cable, port, power and basic detection. |
A recognized storage device that cannot open a volume presents a different problem from an accessory whose identity cannot be established. Likewise, a connected microphone that Windows recognizes but an application cannot access may have a privacy or input-selection problem. Avoid choosing a repair solely because it mentions USB or the same generic error number. Record the complete wording and behavior for the device in question.
Protect Data And Avoid Unsafe Connection Tests
First decide whether your accessory contains information that cannot be replaced. A USB keyboard and an external drive holding the only copy of a business archive warrant different levels of caution. If a drive becomes intermittent, produces abnormal mechanical noises or has suffered impact or liquid damage, avoid repeated experiments. A qualified recovery service may be a better option than attempting a general device repair.
When an accessible storage device contains valuable data, prioritize copying important files to an independent destination before more disruptive work. Confirm that the destination files open correctly. Our Windows backup software comparison discusses independent recovery copies. Do not approve an initialization, formatting or partition deletion prompt merely because an unfamiliar disk entry has appeared. These storage operations do not fix the underlying USB identification exchange and can make recovery harder.
Inspect equipment for damaged connectors, unusual heating, burning smells or possible liquid exposure. Disconnect unsafe equipment when it is safe to do so and stop testing it. Do not connect an obviously damaged cable to another computer just to see whether it produces the same error. Avoid force, improvised adapters and attempts to bridge electrical contacts. The following steps assume that your equipment is safe to operate and that you own it or have authorization to manage it.
Check The Cable, Device And Direct USB Port
Start with the shortest practical connection chain. A USB accessory can be separated from the computer by several components, such as an extension cable, docking station, adapter or hub. Each introduces another possible failure. A simple direct connection often provides better diagnostic evidence than changing software while all of those components remain in use.
- Save active work. Safely eject any recognized external storage before disconnecting it.
- Disconnect the affected accessory and inspect its visible connector and cable.
- Where the cable is removable, select a known-good cable that supports the required data transfer and is compatible with the device.
- Connect the accessory directly to an appropriate working port on the computer.
- Allow Windows to detect the device and inspect its status before opening the intended application.

Not every cable with matching connectors offers the same data capabilities. This matters especially for USB-C equipment: some cables are intended primarily for charging or support different data rates. Use the accessory manufacturer’s specified cable or another suitable equivalent. Microsoft’s USB-C troubleshooting guidance explains why device, cable and port capabilities must be considered together. For an accessory powered through the connection, follow its approved power requirements rather than trying an improvised power supply.
Use A Controlled Comparison To Narrow The Failure
When a direct connection fails, change one variable at a time. If you exchange the cable, move to another port and reboot simultaneously, a successful result will not tell you which change mattered. Write down the outcome of each connection. Use ordinary trusted accessories and your own authorized equipment for the tests. Do not plug unknown storage or other untrusted USB devices into a computer that contains sensitive information.
| Comparison | Possible Interpretation |
|---|---|
| Affected device works with another compatible cable | The original cable or connector arrangement deserves attention. |
| Affected device works on another direct port | Investigate the first port or its connection path. |
| Known-good accessories also fail on one port | The host port or its supporting hardware may be involved. |
| Affected device fails on two compatible hosts | The accessory, its cable or its own power becomes a stronger suspect. |
| Several devices fail through one hub but work directly | Investigate the hub, its upstream cable and power arrangement. |
These comparisons narrow possibilities rather than establish a component-level diagnosis. A device can work with one system and fail with another due to a compatibility difference. If possible, keep the connection method and accessory power source consistent across comparable tests. Skip any experiment that risks valuable data or unsafe equipment.
Inspect The Exact Unknown Device In Device Manager
Open Device Manager by right-clicking Start and choosing its entry. Expand Universal Serial Bus controllers and look for an entry that corresponds to the reported problem. An unknown device may have a warning symbol. On a computer with built-in USB accessories and several connected peripherals, there may be multiple similar entries, so take care to identify the affected one.
For a safely removable non-storage accessory, compare the device list before and after unplugging and reconnecting it. For recognized storage, follow the appropriate safe removal procedure. Observe which entry changes. Do not disconnect internal devices or interfere with a working input connection simply to prove which entry is associated with it.
Open Properties for the identified item and inspect the General tab for the full device status. If available, use Details to review hardware IDs or the device instance path, and note any relevant existing events. An unknown identifier may reflect the absence of a successful device identity exchange; it is not necessarily the accessory’s actual vendor and product information. Do not search for an arbitrary driver using a placeholder hardware ID.
Record identifying information privately because device instance data can contain unique identifiers. An exact device status, a time and the result of a direct connection will be more useful to support than a photograph of every entry in Device Manager. Microsoft’s unknown USB device case study is a useful technical explanation of failures during identification, although its example uses older Windows diagnostic tooling.
Restart Windows And Reconnect The Accessory
A normal restart can clear a temporary host state that persists after disconnecting an accessory. Save your documents and close open applications before restarting. Disconnect the affected external device if it is safe to remove, restart Windows using the ordinary Restart command, and reconnect the device after Windows has loaded. Observe Device Manager again.
A restart is a reasonable comparison, especially when the problem appears after connecting or removing a dock. It is not proof that the device itself is healthy. If restarting restores recognition only briefly, record when the failure returns and investigate that trigger. Does it recur after sleep, when another peripheral is connected or when the cable is moved? A reproducible trigger can help distinguish a power-state problem from an intermittent physical connection.
If a manufacturer provides an approved power-reset procedure for a particular dock or laptop, follow its exact instructions and disconnect only the equipment specified. Do not remove an internal laptop battery, open a power supply or apply a generic electrical discharge procedure. Such steps depend on the hardware design and may be inappropriate for a given model.
When several USB input devices fail together, prepare an alternative means of accessing the computer. An external keyboard is not a useful fallback if it depends on the same failing controller. Our laptop keyboard troubleshooting guide describes comparison testing for input devices.
Uninstall Only The Confirmed Affected Device Entry
After physical connection and restart tests, a targeted device reinstallation can allow Windows to attempt fresh recognition. It does not repair an electrically damaged port or accessory. If the device is functional in another comparable setting but remains incorrectly configured on your PC, the supported uninstall and redetection procedure may be worth trying.
- Save work and make sure you have working input controls.
- Open Device Manager and identify the specific unknown USB device that corresponds to the failure.
- Use the Uninstall device action for that entry. Review the confirmation and do not request deletion of driver packages as a routine step.
- Use Scan for hardware changes or restart as appropriate to let Windows recognize connected devices again.
- Reconnect the accessory if necessary, then inspect the new device status and test the intended function.
Microsoft documents this general recovery route in its Device Manager reference and driver update and reinstallation instructions. Administrative permission may be required. If your computer is managed by a school or employer, obtain authorized assistance before removing device entries or changing configuration.
Do not uninstall every USB host controller or root hub at once. Such an action can interrupt keyboards, mice, network adapters, storage and other equipment that is not part of the original fault. If a controller itself is identified as faulty, use the computer manufacturer’s troubleshooting procedure and prepare an alternative means of operating the system before any controller-specific work.
Review Supported Windows, Chipset And Device Updates
Check whether the problem began after a significant system change. Record the version of Windows and the exact computer and accessory models. A driver update may resolve a known compatibility problem, but a device identification failure does not establish that a new application-specific driver is available or appropriate. The first communication between the host and accessory is still essential.
Use Windows Update to check for relevant supported updates. Windows may also offer optional driver updates through its advanced update settings. Review the package description before choosing it. Obtain device-specific drivers only from the accessory manufacturer or the authorized computer support channel, and verify that the package supports your hardware and Windows architecture. Microsoft’s recommended driver update guidance explains the supported distribution paths.
If a particular driver update immediately preceded the issue and the manufacturer identifies the earlier driver as an appropriate alternative, consider the documented rollback procedure for that driver. Avoid rolling back a security update without considering its consequences. Do not install a generic USB driver bundle from an unrelated download site. Our Windows device driver guide provides additional context for selecting trusted packages.
For a manufacturer-supported firmware or BIOS update, verify the exact affected hardware and documented reason for updating. Maintain reliable power and protect important data first. Firmware is not interchangeable with an ordinary driver; see What Is Firmware. Do not flash firmware merely because a USB device has produced Code 43.
Investigate Failures That Begin After Sleep Or Through A Dock
When a device works after startup but fails following sleep, reproduce the normal conditions once if it is safe to do so. Compare startup and resume behavior with the accessory attached directly and without an optional hub. A difference may indicate an interaction involving the accessory, dock or host power-state transition. Check for relevant documented fixes for those particular models.
USB selective suspend allows individual idle ports to enter a reduced power state. It is an important part of Windows power management, and Microsoft recommends retaining selective suspend. Disabling it throughout the computer is not an appropriate default repair for a descriptor failure. If qualified support recommends a targeted and reversible power-management test for your specific device, record the original configuration and restore it if the test does not help.
For a dock or hub with a separate power supply, verify that the approved adapter is connected and that your combination of devices stays within its documented operating capabilities. A collection of separately functioning accessories may behave differently when connected together. Remove nonessential equipment using safe procedures and compare the affected device alone. Do not assume that a higher-rated adapter or an arbitrary charger is compatible with the hub.
Use Read-Only Command-Line Diagnostics When Needed
Device Manager is sufficient for most home troubleshooting. A command-line inventory can help if you want to document repeated failures or send concise technical evidence to support. On Windows 11, PnPUtil includes a device enumeration command. Open Windows Terminal or Command Prompt with the permissions appropriate to your computer, then run the following read-only query:
pnputil /enum-devices /connected /problem 43This lists connected device instances reporting the specified problem code when supported by the installed Windows version. It may include devices unrelated to USB. Compare names and details with the affected Device Manager entry rather than assuming every result belongs to the accessory. A different query may be needed if the problem code changes or the device disappears entirely. The official PnPUtil command syntax reference documents supported arguments and version requirements.
You can also record the time when the failure occurred and review existing Windows logs around that time. Event Viewer may contain related Plug and Play or device installation events, but the names and available information vary. Correlate a relevant event with the observed failure; an older unrelated warning is not evidence of the present cause.
The command shown here lists device information rather than removing or disabling a device. Avoid copying command-line examples that delete driver packages, restart a broad device class or change the registry unless a qualified support procedure identifies the precise need. Device inventory output may contain unique identifiers, so share only the relevant information privately.
Decide Whether The Accessory Or Computer Needs Service
After completing the comparisons, review the pattern rather than continuing to change settings indefinitely. An accessory that consistently fails on multiple compatible computers with appropriate cables and power deserves assessment by its manufacturer. Multiple known-good accessories that fail on the same physical host port suggest investigating the computer’s port or its supporting hardware. If the failure occurs only through a particular dock, contact that dock’s provider with the successful direct-connection result.
For an external storage device with essential unrecovered files, ask about data recovery before accepting a warranty exchange. Replacing a failed accessory can restore functionality without restoring its contents. A manufacturer may require a defective unit to be returned, so understand the consequences before sending it away. Avoid dismantling sealed devices, attempting solder repairs or replacing components without the necessary qualifications.
Record your symptoms in concrete terms: the exact unknown-device label, code, cable and ports tested, whether the accessory works on another system, and whether the fault recurs after sleep. Mention relevant updates and the result of targeted reinstallation. This information helps a technician reproduce the problem and choose a proportionate next step without repeating unnecessary tests.
Verify Stable Recognition And The Actual Device Function
When Windows identifies the accessory again, inspect its status and verify that it performs the function you need. For a microphone, make a brief local recording. For a keyboard, type a known sequence in a local editor. For a printer, send a simple authorized test page. For storage containing valuable information, prioritize a verified backup instead of repeatedly stressing the device. Do not make an experimental write to a drive whose contents you have not protected.
Test an ordinary disconnect and reconnect if appropriate for the accessory, using safe removal for storage. If the original problem occurred after sleep or through a dock, repeat that normal situation only when necessary and safe. A single successful identification does not establish a lasting repair. Monitor routine use and document any recurrence. Restore temporary settings that did not improve the result, retain supported security protections and avoid keeping questionable equipment in service.
Frequently Asked Questions
What Does USB Device Descriptor Request Failed Mean?
Windows was unable to complete a required exchange of identifying information with the USB accessory. It does not identify the precise failing component.
Does Code 43 Always Mean A Broken USB Device?
No, Code 43 is a general device error. Connection, host configuration and compatibility can also be involved.
Can A USB Cable Charge A Device But Fail To Transfer Data?
Yes, power delivery does not establish that a working compatible data path exists.
Should I Uninstall Every USB Controller?
No, target the confirmed affected device first. Removing controllers can interrupt unrelated input and storage devices.
Will Formatting A USB Drive Fix A Descriptor Request Failure?
No, formatting is a storage operation and does not resolve the required identification exchange. Protect valuable data first.
Should I Disable USB Selective Suspend?
No, not as a general fix. Microsoft recommends retaining it. Use supported targeted diagnostics for a documented power-state problem.
Can A Descriptor Failure Require Hardware Repair?
Yes, persistent failures after controlled compatible connection tests may warrant qualified hardware assessment.
Official References And Technical Review
Reviewed November 16, 2026. References: Device Manager Error Codes, USB-C Connection Problems, Unknown USB Device Case Study, USB Device Descriptors, USB Selective Suspend, Device Manager Driver Updates, PnPUtil Syntax, Recommended Hardware Driver Updates. The illustrations are conceptual rather than captured Windows screens. Troubleshooting steps and command syntax were checked against Microsoft documentation; no physical device or Windows command execution was performed. The comparison examples are proposed tests, not measured results.



