USB Device Not Recognized on Windows 11 (“Device Descriptor Request Failed” Code 43) or USB Port Not Working on Mac? 7 Verified Power, Hub & Driver Fixes (2026)

Verdict: When Windows 11 pops up “The last USB device you connected to this computer malfunctioned” (Unknown USB Device — Device Descriptor Request Failed, Code 43) or a Mac ignores a plugged-in drive, the USB host controller detected voltage on the port but failed to read the accessory’s 18-byte identification packet. Bypass unpowered hubs and desktop front-panel jacks, swap out charge-only cables, drain motherboard flea power, uninstall the stuck Code 43 entry in Device Manager, and approve macOS lock-screen accessory prompts.

Every time you plug a flash drive, external NVMe SSD, mouse receiver, audio interface, or keyboard into a computer, a multi-stage hardware conversation happens in under 100 milliseconds. First, the accessory pulls the D+ or D- data line high using a 1.5 kΩ resistor so the computer’s Extensible Host Controller Interface (xHCI) knows something physical was inserted. Next, the host resets the port and issues a standard GET_DESCRIPTOR request asking the accessory for its Vendor ID (VID), Product ID (PID), and power budget.

If voltage sags mid-startup, if dirty contacts scramble the differential data pins while the longer power pins still make contact, or if Windows Fast Startup leaves the root hub in a suspended state, the host hears electrical noise instead of a valid descriptor. Windows flags USB\VID_0000&PID_0002, logs Error Code 43, and shuts down the port to protect the bus.

Editorial basis: This guide synthesizes official diagnostics from Microsoft Learn (CM_PROB_FAILED_POST_START / Error Code 43), Microsoft Device Manager Error Reference, and Apple Support Mac USB Power & Accessory Documentation.

Symptom-to-Cause Diagnostic Matrix

Fix 1: Bypass Unpowered USB Hubs & Desktop Front-Panel Case Jacks

When an external NVMe SSD enclosure, mechanical portable hard drive, capture card, or RGB gaming keyboard triggers Device Descriptor Request Failed, insufficient port current (VBUS sag) is the number-one culprit.

A standard USB 2.0 port is rated for only 500 mA (2.5W) at 5V, and a standard USB 3.0 Type-A port is rated for 900 mA (4.5W). When you plug an unpowered 4-port USB dongle into a single laptop port and connect a bus-powered NVMe SSD alongside a mouse and headset, all three accessories must split that single 900 mA ceiling. The moment the SSD controller spins up its flash channels during enumeration, voltage dips below 4.35V, the SSD controller browns out mid-handshake, and Windows flags Code 43.

1. Unplug all USB hubs, docks, and extension cables: Connect the problem device directly into a built-in port on the side of your laptop or the back of your desktop PC.
2. On a desktop tower, move from the top/front case ports to the rear motherboard I/O shield: Front-panel USB ports on desktop cases travel through 50–70 cm of thin internal ribbon wire plugged into a bottom motherboard header. Over time, loose header pins and wire resistance cause severe signal attenuation and voltage drop on 5 Gbps / 10 Gbps USB 3.x drives. Rear ports soldered directly onto the motherboard PCB deliver clean power and short signal traces.
3. Switch between USB 3.0 (blue/teal) and USB 2.0 (black) ports to test: If a legacy USB 2.0 audio interface, printer, or microcontroller fails on a SuperSpeed USB 3.2 port, try a black USB 2.0 port—or conversely, if an external SSD browns out on a USB 2.0 port, move it to a higher-amperage USB-C or USB 3.2 port. As Apple’s Mac USB power documentation notes, bus-powered drives that exceed port current limits must either plug directly into the computer or use a self-powered hub with its own AC wall adapter.

Fix 2: Eliminate “Charge-Only” Cables & Oxidized Connector Pins

Not all USB cables carry data, and even full-featured cables fail in a specific way that mimics a dead motherboard port. Look closely inside any standard USB-A or USB-C plug: the outermost pins (VBUS +5V power and GND ground) are physically slightly longer or engage earlier than the center differential data pins (D+, D-, and SuperSpeed TX/RX lanes).

• The charge-only cable trap: Thin USB-C and Micro-USB cords bundled with desk lamps, rechargeable fans, vape batteries, and budget wireless earbuds contain only two copper wires (red +5V and black ground) and zero data wires. Plugging an external SSD or controller in with a charge-only cord powers on the device’s LED while the computer sees nothing at all (for a full pinout breakdown, see how USB-C charging, data, and video cables differ).
• Half-inserted or lint-packed USB-C ports: If pocket lint or dust compacts at the bottom of a USB-C port, the plug stops half a millimeter short—making solid contact on the power pins while the high-speed data pins intermittently drop out, producing instant Code 43 descriptor errors. Power off the device and inspect the port with a flashlight.

Fix 3: Perform a Full Cold Shutdown & 30-Second Flea-Power Capacitor Drain

Wait—what if Windows 11 keeps chiming and displaying “USB device not recognized” even when every single external USB port on your laptop or desktop is completely empty?

That happens because motherboards wire several internal components onto the exact same USB 2.0 root hub as your external jacks: the Bluetooth half of your M.2 Wi-Fi card, your webcam above the screen, RGB lighting controllers, fingerprint readers, and liquid-cooler LCD pumps. Because Windows 11 uses Fast Startup (hybrid hibernation) by default and motherboards keep the +5VSB / 3.3V_AUX standby rail energized when shut down, a hung USB port state survives normal restarts indefinitely.

1. Unplug all external USB peripherals from the computer.
2. Open the Windows Start menu, click Power, hold down the Shift key on your keyboard, and click Shut down while keeping Shift held (forcing a full S5 cold shutdown instead of Fast Startup hibernation).
3. On a laptop: Unplug the AC power brick, then press and hold the physical power button continuously for 30 to 45 seconds to reset the Embedded Controller (EC) and drain motherboard capacitors. Reconnect AC power and turn the laptop on. (If you noticed your Bluetooth icon vanished at the exact same time the Unknown USB Device error appeared, that Code 43 entry is your internal Bluetooth radio—follow our dedicated guide on fixing missing Windows 11 Bluetooth toggles and Code 43/45 adapters.)
4. On a desktop PC: Flip the rear PSU switch to O (Off), unplug the AC power cable from the wall, hold the case power button for 30 seconds, plug the AC cord back in, and boot up.

Fix 4: Uninstall the Stuck Code 43 Device & Rebuild the USB Root Hub Stack

As documented in Microsoft Learn’s CM_PROB_FAILED_POST_START (Error Code 43) engineering guide, Windows stops communicating with a USB port once a driver reports a post-start enumeration failure (IRP_MN_QUERY_PNP_DEVICE_STATE). Clearing that cached failure flag in Device Manager forces Windows to re-enumerate the device from scratch.

1. Right-click the Start button and select Device Manager.
2. Scroll to the bottom and expand Universal Serial Bus controllers.
3. Right-click Unknown USB Device (Device Descriptor Request Failed)—or Unknown USB Device (Port Reset Failed)—and click Uninstall device, then confirm Uninstall.
4. Unplug the physical USB accessory from your PC and wait 5 seconds.
5. Back in Device Manager, right-click your USB Root Hub (USB 3.0) (or USB xHCI Compliant Host Controller) only if you have a laptop trackpad or secondary mouse available, or simply click Action > Scan for hardware changes on the top menu bar and restart your computer.
6. Once Windows finishes rebooting to the desktop, plug the USB device into a different direct port so Windows builds a fresh registry device node.

Fix 5: Disable Windows 11 USB Selective Suspend & Root Hub Power Saving

If your USB drive, audio DAC, or gaming mouse works fine for ten minutes and then randomly disconnects with Code 43 whenever your PC idles, Windows power management is cutting link power to the USB hub—and the accessory’s controller firmware is failing to wake from the U3 suspend state.

Step A: Turn Off Power Saving on All USB Root Hubs in Device Manager

1. In Device Manager > Universal Serial Bus controllers, double-click the first USB Root Hub (USB 3.0) or Generic USB Hub entry.
2. Click the Power Management tab at the top.
3. Uncheck the box labeled “Allow the computer to turn off this device to save power” and click OK.
4. Repeat this for every USB Root Hub and Generic USB Hub in the list.

Step B: Disable USB Selective Suspend in Control Panel Power Options

1. Press Win + R, type control powercfg.cpl,,1 (or open Control Panel > Power Options > Change plan settings > Change advanced power settings), and press Enter.
2. Expand USB settings > USB selective suspend setting.
3. Set both On battery and Plugged in to Disabled, then click Apply > OK.

Fix 6: Fix USB Ports & Drives Not Recognizing on a Mac (Allow Accessories to Connect & SMC/Port Reset)

If a USB-C flash drive, SD card reader, or hub works on a Windows PC yet seems completely dead when plugged into a MacBook Air or MacBook Pro running macOS Sonoma, Sequoia, or newer, check Apple’s port-security gate first.

1. Approve Locked-Mac USB & Thunderbolt Security Prompts

According to Apple’s Mac port and accessory security documentation, Apple Silicon Macs (M1, M2, M3, M4, and newer) block new USB and Thunderbolt data connections by default if the accessory is plugged in while the screen is locked—or if you accidentally clicked “Don’t Allow” on the initial popup.

1. Open Apple menu () > System Settings > Privacy & Security.
2. Scroll all the way to the bottom and locate Allow accessories to connect (under the Security heading).
3. Change the dropdown from Ask every time or Ask for new accessories to Always (or the automatic signed-in option), then unplug and replug your USB device while signed in to the Mac.

2. Check Disk Utility for Unmounted or Unformatted Drives (Both Mac & Windows)

Sometimes the USB port and handshake work 100% cleanly, yet the external SSD or thumb drive never appears in Finder or Windows File Explorer because its partition table is uninitialized, lacks a drive letter, or uses an incompatible file system (such as an Apple APFS drive plugged into Windows, or an unmounted drive on macOS):

• On Windows 11: Right-click Start > Disk Management. If the drive appears at the bottom as Online / Healthy with no drive letter (D:, E:), right-click the volume and choose Change Drive Letter and Paths > Add.
• On macOS: Open Applications > Utilities > Disk Utility and press Cmd + 2 (View > Show All Devices). If the drive appears greyed out in the left sidebar, select its volume and click Mount in the top toolbar. If you need the drive to work on both platforms without errors, follow our guide on formatting an external SSD for both Mac and Windows using exFAT and GUID Partition Map.

Fix 7: Update Chipset / USB4 Drivers & Cross-Test the Accessory on Another Host

If an external device still throws USB\VID_0000&PID_0002 (Code 43) after a cold capacitor drain, direct rear-port connection, and new cable, isolate whether the computer’s host controller or the USB peripheral itself has failed:

• Update AMD / Intel Chipset & USB4 Host Drivers: On AMD Ryzen (AM4/AM5) and Intel Core systems, install the latest motherboard Chipset Driver package and UEFI BIOS update directly from AMD, Intel, or your laptop manufacturer—BIOS AGESA and Intel Management Engine updates frequently patch USB 3.2/USB4 enumeration dropouts.
• Plug the USB device into a second computer or smartphone: Plug your flash drive, mouse, or headset into another laptop—or even into your smartphone using an adapter (see how to test and fix USB flash drives and SSDs on a phone). If a USB thumb drive throws the exact same “Device Descriptor Request Failed” error on a second computer, the thumb drive’s internal NAND controller or quartz crystal oscillator has suffered a hardware failure.

Frequently Asked Questions

Can I recover files from a USB flash drive that says “Device Descriptor Request Failed (Code 43)” on every computer?

If a USB flash drive fails with Code 43 (VID_0000&PID_0002) across multiple computers and shows 0 MB or does not appear in Disk Management at all, consumer file-recovery software (like Recuva or Disk Drill) cannot read it because the USB controller chip inside the stick is not communicating with the bus. Gently cleaning the gold USB contacts with 99% isopropyl alcohol sometimes revives oxidized plugs; otherwise, only a professional chip-off data recovery lab that desolders the NAND flash chip can extract the files.

Why do my USB 3.0 ports disconnect whenever my Wi-Fi or Bluetooth acts up?

Poorly shielded USB 3.0 cables and hubs emit broadband radio-frequency noise in the 2.4 GHz–2.5 GHz spectrum, and conversely, overloaded motherboard 5V rails can glitch internal USB hubs shared by wireless modules. Keeping unshielded USB 3.0 dongles away from wireless receivers and using a powered hub resolves both issues.

What is the difference between Code 43 and Code 28 in Windows Device Manager?

Code 43 means the hardware handshake or post-start initialization failed at the electrical or firmware level (Device Descriptor Request Failed). Code 28 (“The drivers for this device are not installed”) means the USB hardware connected cleanly and reported its exact Vendor and Product IDs, and only needs you to install its manufacturer driver software.

Editorial basis: Research-based troubleshooting synthesis referencing Microsoft Learn (CM_PROB_FAILED_POST_START / Code 43), Microsoft Device Manager Error Reference, and Apple Support (HT204377 / 102282), verified November 9, 2026. GadgetsFocus did not perform hardware USB bus-analyzer captures for this article. The featured image is a studio macro concept photograph.