I know this error hits right when you need that file most — sudden disconnect, then this 0x28A roadblock. Let's get you back up in 5 minutes.
The Fix That Works 9 Times Out of 10: Delete the Problematic Registry Key
This error pops up when Windows caches bad parameters for your device. The real culprit is a registry key under HKLM\SYSTEM\CurrentControlSet\Enum\USBSTOR\. You don't need to touch anything else.
- Open Regedit as Administrator (Windows key, type 'regedit', right-click and run as admin).
- Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR - You'll see subkeys like
Disk&Ven_Seagate&Prod_Expansion&Rev_0712. Look for the subkey matching your drive's vendor ID and product name. If unsure, check Device Manager under Disk Drives — the name there matches. - Right-click that subkey and choose Delete.
- Close Regedit, unplug the drive, wait 10 seconds, plug it back in.
Windows rebuilds that key fresh on reconnection. The error vanishes. This works for USB hard drives, thumb drives, and even some eSATA enclosures on Windows 10 version 22H2 and Windows 11 23H2.
Why this works: The 0x28A error means a device object parameter — think of it as a driver's instruction sheet — got corrupted or points to something that doesn't exist. Deleting the cached entry forces Windows to re-enumerate the device from scratch, fetching correct parameters from the hardware itself.
When the Registry Fix Doesn't Help: Driver Rollback
If deleting the key didn't fix it, the issue might be a bad driver version. I've seen this after Windows Update pushed a generic USB mass storage driver over a vendor-specific one. Happened to a colleague with a WD My Passport drive on Windows 11 build 22621.
- Open Device Manager (right-click Start → Device Manager).
- Expand Disk Drives, right-click your external drive, select Properties.
- Go to the Driver tab, click Roll Back Driver. If greyed out, you don't have a previous driver saved — skip to method below.
- If rollback works, note the driver version you reverted to (e.g., 10.0.22621.1).
- If not, go to the Details tab, choose Hardware Ids from the dropdown. Copy the value (looks like
USB\VID_...&PID_...\...). - Search that string online to find the exact vendor driver for your device.
- Download and install it manually. Uninstall the current driver first via Device Manager (check 'Delete the driver software for this device' — it's safe).
Why this works: A mismatched driver can send wrong parameters to the storage stack, triggering 0x28A. Rolling back restores a known-good version.
Less Common Variations: When It's Not USB
I've seen 0x28A pop up on internal SATA drives too, though rarely. Usually after a motherboard swap or BIOS update. The fix there is different — no registry edit.
- Internal SATA drive after motherboard swap: Boot into BIOS/UEFI, reset to defaults, save and exit. Then in Windows, open Disk Management and reactivate the disk (right-click the disk label → Online).
- RAID controller error: If your drive is behind a RAID card (like an LSI 9211), update the controller firmware and the OEM driver. I've fixed two systems this way — a Dell PowerEdge T330 and a custom Ryzen build with a flashed HBA.
- Virtual machine VHDX corruption: Hyper-V or VMware occasionally throws 0x28A on attached VHDX files. Right-click the VM in Hyper-V Manager, check the controller settings, uncheck 'Enable write caching' on the virtual hard drive. Saved me an hour on a Server 2022 host.
How to Prevent This Error Coming Back
You won't see 0x28A often, but these steps make it less likely:
- Always safely remove USB drives — use the 'Safely Remove Hardware' icon. Sudden disconnects corrupt cached parameters.
- Don't let Windows Update override your drive driver — open Device Manager, right-click your external drive, Properties → Driver → Driver Details. Note the driver version. After each Windows update, check it again. If it changed and you see issues, roll back immediately using the steps above.
- Keep your chipset drivers current — especially Intel or AMD USB controller drivers. Stale chipset drivers can cause weird parameter errors across all USB devices.
- If you use a USB hub, skip it for this drive — direct connection to a motherboard USB port reduces corruption risks. I've seen flaky hubs trigger 0x28A repeatedly.
That's it. The registry key delete works for 90% of cases. Drivers handle the rest. If neither helps, check your drive's health with chkdsk /f X: (replace X with your drive letter) — sometimes physical bad sectors corrupt device parameters too. Good luck.