Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| The same USB device fails on every computer | The device or cable is probably faulty |
| It works directly but not through a hub | The hub lacks power, bandwidth or compatibility |
| Only one PC port fails | Inspect that port and its controller path |
| Unknown USB Device shows Code 43 | Check descriptor, power, cable and hardware before reinstalling |
Diagnose usb device not recognized before replacing drivers
Check Universal Serial Bus controllers and the device category in Device Manager. A descriptor failure, Code 43, or complete absence each point to different USB, cable, power, or device causes.
Test the USB device directly on another port and computer, and test a known-good USB device on the original port. Avoid hubs and front-panel extensions during diagnosis.
Use the symptom evidence to select the correct layer. “The same USB device fails on every computer” points toward the device or cable is probably faulty, while “It works directly but not through a hub” suggests the hub lacks power, bandwidth or compatibility. Also note what changed immediately before the failure: a Windows update, driver package, new dock, BIOS update, sleep or hibernation cycle, physical impact, liquid exposure or installation of device-management software.
Use chipset/USB controller drivers from the PC manufacturer and device-specific drivers from the accessory maker when required. Most standard USB devices should enumerate before a special driver is needed.
Fully restart Windows, disconnect unnecessary USB hardware, then test the problem device directly. This clears transient enumeration conflicts before controller or driver repair.
The remaining symptoms also narrow the search: “Only one PC port fails” means you should inspect that port and its controller path, while “Unknown USB Device shows Code 43” means you should check descriptor, power, cable and hardware before reinstalling. After each repair, verify the original function rather than accepting a successful installer message. A package can finish correctly while Windows still loads another driver or the hardware remains unavailable.
Prove the cable, port and power path
Disconnect the device, wait ten seconds and connect it directly to another compatible port. Remove extension cables, adapters and hubs for the test. For storage and high-power accessories, use the supplied cable and external power where supported.
USB-C shape does not guarantee identical capabilities. A port or cable may support charging but not data, or basic USB without video, Thunderbolt or USB4. Match the PC port, cable and device specifications before treating limited functionality as a Windows fault.
1Run a controlled cross-test
- Try the device with another known-good cable.
- Try it on another computer.
- Try a different known-good USB device in the original port.
2Reduce power and bandwidth load
- Disconnect unused devices.
- Plug the laptop into power.
- Use a powered hub for devices that exceed the PC port's available power.
Inspect the exact Device Manager failure
Look under Universal Serial Bus controllers and the device's normal category. Open Properties and record the code. Code 28 needs a driver; Code 43 means the device or driver reported a failure; Code 45 reports a disconnected device.
Use Action > Scan for hardware changes after reconnecting. If several ports on the same controller fail, install supported chipset, USB and dock firmware from the PC maker. Do not uninstall every USB controller when your only keyboard and mouse depend on them.
Handle storage, phones and docks correctly
A detected USB drive that lacks a drive letter belongs in the Files and Storage cluster; do not format it merely because File Explorer is empty. A phone may default to charging only and require an unlocked screen plus File transfer mode. Back up irreplaceable data before disk repair.
Docks combine USB, networking, audio, charging and display functions. Update dock firmware and the PC's USB-C or Thunderbolt stack, then test each function separately. A dock that works on one port but not another may be using capabilities the second port does not provide.
Verify the repair before making more changes
Restart Windows—not only the affected app—and confirm that Windows detects the accessory consistently and every required USB function works. Check Device Manager again: the device should remain present without a warning icon, and Device status should say it is working properly.
Reconnect the USB device, use it normally, restart Windows, then reconnect once more. Confirm recognition is consistent and not limited to one successful plug-in.
Technical order checked against Microsoft's current USB-C and USB device guidance. Device-specific menus and driver availability vary by manufacturer.
Frequently asked questions
Why does Windows say the last USB device malfunctioned?
Windows could not communicate with the device correctly because of hardware, cable, power, port or driver failure.
Should I uninstall USB controllers?
Only after safer tests and with another input method available. Start with the specific failed device and supported chipset drivers.
Why does my USB-C device charge but not transfer data?
The cable or port may be charge-only or lack the required USB data capability.