USB device not recognized in Windows

• Estimated time: 3 min
• Easy
• Low risk

Separate accessory type and risk before moving cables.

1. Record model, direct port/hub and exact message. For storage, do not accept initialization or formatting. Before moving it, close files and safely eject; if impossible, shut Windows down normally. If it is your only mouse/keyboard, prepare another input method before disconnecting it.

2. For damage, smell, abnormal heat or an overcurrent warning, stop testing that accessory and seek inspection. If safe, choose the branch by the result; do not uninstall all USB controllers.

• Estimated time: 5 min
• Easy
• Low risk

1. Following storage/input precautions, try the same device directly in another compatible port without a hub or extension. If it works only there, check another known accessory in the original port. If both fail there, prioritize that port or path; stop using it if damaged.

2. If the second accessory works but the first does not, keep the good port and try a known compatible data cable if detachable. If now recognized, the previous cable or its contact explains the difference; Windows reinstallation is unnecessary. If unchanged, keep that combination for another PC.

3. On another owned/trusted PC with required capabilities and official driver, try the accessory. If it also fails, review device/cable/power with the manufacturer. If it works, return to the first PC and compare capabilities and status code. Do not connect unknown storage or install untrusted software for the comparison.

• Estimated time: 5 min
• Easy
• Low risk
• Restart required

1. If several accessories fail through the same hub/dock, compare one directly through a compatible connection. If direct works, check hub power and capability rather than blaming every accessory. If only ports in one area fail, record which ones; they may share an internal path for the manufacturer to inspect.

2. If known devices fail in every port, retain an input method and check Device Manager. With work saved and storage closed, restart Windows once. If persistent, compare codes and recent chipset/USB changes with OEM support; do not bulk-uninstall controllers supporting keyboard or mouse.

• Estimated time: 5 min
• Easy
• Low risk

1. Check computer, cable and accessory specifications: USB data, charging, video output and Thunderbolt/USB4 are different capabilities. Charging a phone does not prove that cable transfers data; a working USB drive does not prove video output. USB-C ports on the same PC need not have identical features.

2. Connect directly to the port supporting the function and use a cable certified/supported for it. If it works, the difference is path/capability. If any part does not support the function, stop: a driver cannot add it. If all support it, follow status code or power.

• Estimated time: 5 min
• Easy
• Low risk

1. If the drive, interface or dock requires its own adapter, use the one specified for that model rather than one that merely fits. On a laptop, connect its supported power before comparing. Do not try Y-cables or improvised supplies.

2. If it becomes stable with correct power, investigate the previous supply. If unchanged, do not assume more power is needed: return to cable/port and status. For overcurrent, heat or repeated cutouts, stop and seek inspection rather than continuing to connect it to other PCs.

• Estimated time: 5 min
• Easy
• Low risk

1. If the drive appears in Windows but requests formatting or cannot open files, that is a storage branch rather than authorization to initialize. Cancel the prompt and preserve the exact state. Do not run write-based repairs on a drive with irreplaceable data before assessment.

2. If not recognized over USB, perform only safe external substitutions with compatible cable and power. Stop for repeated disconnections, unusual noises or unique data; give the history to data-recovery support. A working test allows backup rather than requiring further fault reproduction.

• Estimated time: 5 min
• Easy
• Low risk

1. In Device Manager open the affected entry’s Properties and read Device status. Code 43 means a driver reported a problem; Code 10 means it cannot start; Code 28 means drivers are missing. Follow the corresponding related guide rather than treating every USB alert as Code 43.

2. Without a useful code, record the name and whether it changes on safe connection/disconnection. If the accessory works on another compatible PC, seek its official model/Windows package or ask the OEM to review the port driver. Do not download a generic driver solely because it says unknown device.