How to Fix USB Code 43 on Android

Troubleshooting Windows USB Code 43 for an Android phone

Windows Device Manager Code 43 means that a driver controlling the device reported a failure, so Windows stopped the device. With an Android phone, the entry may appear as Unknown USB Device, Device Descriptor Request Failed, an MTP device, or an Android interface with a yellow warning symbol.

Code 43 is not automatically an Android Studio, Flutter, or ADB problem. Windows must first communicate with the phone at the USB hardware level. The most efficient fix is to test the physical connection, determine whether Windows can enumerate the device, then repair the appropriate driver or ADB layer.

Identify the Exact Failure

Disconnect other unnecessary USB devices.
Connect the unlocked Android phone directly to the computer.
Right-click the Windows Start button and open Device Manager.
Check Universal Serial Bus controllers, Portable Devices, Android Device, and Other devices.
Open the affected entry's Properties.
Read the message under Device status and confirm that it actually says Code 43.

Write down the device name and when the warning appears. Unknown USB Device (Device Descriptor Request Failed) usually points to failure during early USB communication. An Android or ADB interface with Code 43 may indicate that basic enumeration succeeded but a later driver or device operation failed.

Use a Simple Isolation Matrix

Before reinstalling software, compare the problem using equipment you already trust:

Test	Result	Likely area
Same phone, another known-good data cable	Works	Original cable
Same phone and cable, another PC port	Works	Original port, hub, or controller path
Another phone, same cable and port	Works	Original phone or its connector
Problem phone, known-good cable, another computer	Still fails	Phone connector, contamination, firmware, or hardware
Several phones fail on the same PC	All fail	PC port, Windows driver, chipset, or USB controller

This matrix is more useful than repeatedly installing drivers because it separates the phone side from the computer side.

Step 1: Replace the Cable

Many USB cables supply power but do not carry data, and a damaged data contact can allow charging while communication fails. Use a short cable that has already transferred files successfully. Avoid an adapter, extension, monitor port, keyboard port, dock, or unpowered hub during diagnosis.

If the connector feels loose, works only at an angle, or disconnects when moved slightly, stop repeatedly stressing the port. That behavior suggests a worn cable plug or phone connector.

Step 2: Change the USB Port

Connect directly to another port on the computer. On a desktop, try a rear motherboard port instead of a front-panel connector. On a laptop, test ports on different sides if available because they may use different controller paths.

If the phone works through USB 2.0 but fails through a faster port, update the computer manufacturer's chipset, USB, firmware, and BIOS packages through its official support page. Do not install a generic “USB booster” or driver pack.

Step 3: Restart the Phone and Windows

Disconnect the phone, restart it, and restart Windows. Reconnect only after both have fully started. This clears temporary device and controller state without changing data or settings.

If a normal restart does not help and the PC supports it, perform a complete Windows shutdown, remove external power where practical, wait briefly, and start it again. Do not open a laptop or remove an internal battery merely for this test.

Step 4: Check the Android USB Mode

Unlock the phone after connecting it. Tap the Android USB notification and choose the mode needed for the task, commonly File transfer / Android Auto for MTP or USB debugging for development.

A phone that stays on Charging only may not appear as portable storage, but that alone should not normally produce a descriptor failure. If Windows cannot enumerate the device at all, changing the Android USB mode or reinstalling ADB will not repair the underlying connection.

For ordinary document and photo transfers, continue with How to Transfer Files Between Android and Windows after Device Manager reports that the device is working.

Step 5: Inspect the Phone's USB Port

Turn the phone off and inspect the port under bright light. Pocket lint, dust, moisture, corrosion, or a damaged center tongue can interfere with data contacts. Do not insert a pin, needle, paper clip, or other metal tool. Do not pour liquid or spray cleaner into the connector.

If the phone shows a moisture warning, disconnect it and follow the manufacturer's drying instructions. If the connector is visibly damaged, becomes hot, smells unusual, or repeatedly disconnects with several known-good cables, seek qualified hardware service.

Step 6: Remove the Failed Entry from Device Manager

Microsoft's official Code 43 guidance recommends uninstalling the affected device and scanning for hardware changes so Windows can reinstall it.

Disconnect the phone.
Open Device Manager.
Locate the exact failed entry you identified earlier.
Right-click it and select Uninstall device.
Do not select a driver-removal option unless you already have the correct replacement and know which package is affected.
Restart Windows or select Action > Scan for hardware changes.
Reconnect the phone with the known-good cable and port.

Do not uninstall every USB controller at once. A broad removal can temporarily disable the keyboard, mouse, storage, network adapters, or other essential devices and makes the original fault harder to isolate.

Step 7: Install the Correct Driver

Use drivers only from Windows Update, the computer manufacturer, the Android device manufacturer, or official Android developer resources.

For a Google device

Android Studio provides the Google USB Driver on Windows:

Open Tools > SDK Manager.
Select the SDK Tools tab.
Select Google USB Driver.
Apply the installation.

The Google USB Driver is for Google devices. It is not a universal replacement for Samsung, Xiaomi, Motorola, OnePlus, or every other Android manufacturer.

For another manufacturer

Use the official OEM driver page linked from Android's documentation or the phone manufacturer's support site. Confirm the exact model and Windows architecture. Avoid third-party driver download portals, modified INF files, automatic driver updaters, and unsigned packages.

Update the computer side

Install applicable Windows updates and the current chipset, USB-controller, firmware, and BIOS packages offered for the exact PC model. Create a recovery plan and connect reliable power before a firmware update. Do not flash firmware from another model.

Step 8: Separate MTP from ADB

An Android phone can appear in Windows for file transfer but remain unavailable to ADB, or it can be visible to ADB while MTP is not selected. Diagnose the layer you actually need:

Device Manager: Can Windows enumerate the hardware without Code 43?
File Explorer: Does the phone appear after selecting File transfer?
ADB: Does adb devices -l list the phone?
Android Studio or Flutter: Does the tool see the ADB device as a run target?

Do not troubleshoot Flutter until Windows and ADB are working. For the complete development connection, see How to Connect an Android Phone to Flutter.

Step 9: Repair ADB After Code 43 Is Gone

Once Device Manager recognizes the phone without Code 43:

Enable Developer Options and USB debugging.
Connect the unlocked phone to your own computer.
Approve the RSA fingerprint prompt only if you recognize the workstation.
Run adb devices -l.

If ADB is still empty, restart its local server:

adb kill-server
adb start-server
adb devices -l

If the state is unauthorized, unlock the phone and check for the authorization prompt. You can revoke old ADB authorizations in Developer options, reconnect, and approve the new fingerprint.

Use How to Enable Developer Options on Android 16 for the safe setup and revocation steps.

Use Wireless Debugging as a Temporary Alternative

If USB data is unavailable but the phone otherwise works, Android 11 and later can pair with Android Studio or ADB over a trusted Wi-Fi network. This can keep development moving, but it does not repair the USB fault and should not be used to ignore signs of connector damage.

Follow How to Debug an Android Phone Using Wi-Fi. Turn Wireless debugging off or forget the workstation when finished.

What Not to Do

Do not download random “universal Android drivers.”
Do not run registry cleaners or paste unexplained registry edits.
Do not disable driver-signature checks merely to install an unknown package.
Do not uninstall every USB controller without a recovery plan.
Do not insert metal tools or liquid into the phone connector.
Do not factory-reset the phone before testing cable, port, another phone, and another computer.
Do not assume that enabling USB debugging repairs a descriptor failure.
Do not continue using a connector that becomes hot, smells unusual, or is visibly damaged.

When the Problem Is Probably Hardware

Hardware service becomes more likely when:

The same phone fails on multiple computers with multiple proven data cables.
Another phone works immediately on the original computer, port, and cable.
The connector is loose, corroded, damaged, or works only at an angle.
Data fails after impact, liquid exposure, or connector repair.
The phone cannot maintain a stable USB connection even outside Windows.
The port overheats or shows other electrical warning signs.

Back up important data over Wi-Fi or cloud services before service if the phone remains usable. Choose an authorized or reputable repair provider and describe the comparison tests already completed.

Frequently Asked Questions

Can the phone charge normally and still show Code 43?

Yes. USB power and data use different contacts and signalling. A charging-only cable, damaged data conductor, contamination, or connector fault can allow power while data communication fails.

Will reinstalling Android Studio fix Code 43?

Usually not when Windows reports an Unknown USB Device or descriptor failure. Fix hardware enumeration and the Windows driver layer before reinstalling development tools.

Should I install the Google USB Driver for every Android phone?

No. Google's official driver is for Google devices. Other manufacturers supply their own Windows drivers when a specific ADB driver is required.

Does Code 43 mean the phone port is broken?

Not necessarily. A cable, PC port, hub, Windows driver, USB controller, firmware, or phone connector can produce similar symptoms. Use comparison tests to isolate the side that consistently fails.

Should I factory-reset the phone?

Not as an early step. A factory reset erases user data and cannot repair a damaged cable, port, connector, or Windows USB controller. Consider software reset only after evidence points to the phone's software and after completing a verified backup.

Final Diagnostic Checklist

Confirm the exact Device Manager message and Code 43.
Use a known-good data cable.
Connect directly to a different PC USB port.
Compare another phone on the same cable and port.
Test the problem phone on another computer.
Restart the phone and Windows.
Inspect the phone connector safely.
Uninstall only the failed Device Manager entry and rescan.
Install drivers only from official sources.
Test ADB only after Windows recognizes the phone correctly.
Seek hardware service when the fault follows the phone across cables and computers.

The key to Code 43 is identifying the failing layer. Begin with cable, connector, and USB enumeration; then move to MTP, the OEM driver, ADB authorization, and development tools. That order avoids destructive resets and unnecessary driver changes.

Official References

Device names, driver packages, and Windows menus can change. This guide was reviewed against official Microsoft and Android documentation available on 23 August 2026.