0X000010E3

ERROR_MEDIUM_NOT_ACCESSIBLE (0x10E3): Real Fixes for Transport Medium Access Failure

EP
Erropedia Team
📅 May 26, 2026 📅 Updated Aug 1, 2026 👁 10 views Windows Errors Intermediate
Windows can't access the transport medium. Usually a bad USB drive, missing driver, or corrupted system file. Here's how to fix it fast.

What's actually happening here

Error 0x000010E3 means the transport layer—the USB controller, SATA host adapter, or external enclosure bridge—can't talk to the storage medium. It's not a file system error. The drive is physically there, but Windows can't establish a reliable data path. I've seen this most often with cheap USB 3.0 hubs, worn-out cables on external SSDs, and after a Windows Update that clobbered the storage controller driver.

Work through these in order. Stop when the error goes away.

30-second fix: Check the physical connection

Half the time this error is mechanical. The USB port has tiny pins that bend, or the cable's internal wire has broken near the connector. Different enclosures and cables use different pinouts—what works for a flash drive might not work for your external HDD.

  1. Unplug the device completely.
  2. Try a different USB port. Use a port on the back of the PC (directly on the motherboard) if you're on a desktop. Front-panel ports lose signal through the internal header cable.
  3. Swap the cable if you're using an external drive. USB-C to USB-C cables are notorious for going bad after 6 months.
  4. Plug the device directly into the PC, not through a hub. USB hubs have their own controller chips that can fail silently.

If the error goes away, you're done. The medium was accessible, just not through that port or cable. If it persists, move on.

5-minute fix: Reinstall the storage controller driver

What's actually happening here is that Windows cached a bad driver state or the driver itself got corrupted. I've traced this to Windows Update pushing a generic Microsoft driver over the manufacturer's specific one. The fix is to force Windows to re-enumerate the device with a clean driver.

  1. Press Win + X and select Device Manager.
  2. Expand Universal Serial Bus controllers. You'll see entries like "Standard Enhanced PCI to USB Host Controller" or "AMD USB 3.10 eXtensible Host Controller".
  3. Right-click each entry that says Host Controller or xHCI and select Uninstall device. Check "Delete the driver software for this device" if prompted.
  4. Also check Disk drives in Device Manager. You'll see your external drive listed there. Uninstall it too.
  5. Restart the PC. Windows will reinstall the drivers during boot.

Why this works: by removing the host controller driver, Windows is forced to treat the USB bus as a new device. The chipset driver (which handles the transport layer) gets reinitialized from scratch. I've fixed dozens of these errors with just this step.

Test your device. If the error returns, it's a deeper driver issue or a hardware problem.

15+ minute fix: Clear the drive's SCSI reservation and rebuild the transport stack

This targets a specific scenario: you're using an external enclosure that presents as a SCSI device (most USB-to-SATA bridges do). The drive's transport layer can lock up if a previous session left a SCSI reservation active. Windows sees the hardware but can't send commands through the transport.

  1. Open Command Prompt as Administrator. Search for cmd, right-click, and select Run as administrator.
  2. Run diskpart and press Enter.
  3. Type list disk. Identify your external drive by its size. It'll show as Disk X (X being a number). If the error prevents listing, skip to step 6.
  4. Type select disk X (replace X with the number).
  5. Type clean and press Enter. This erases all data on the drive. Back up anything important first.
  6. Type exit to close diskpart.

If diskpart itself gives the 0x10E3 error (I've seen it hang there for 30 seconds before timing out), the transport is truly stuck. Here's the nuclear option:

  1. Open Device Manager, expand Portable Devices (if present) and Universal Serial Bus controllers.
  2. Uninstall every device under both categories. Yes, every single one, including the generic USB Root Hub entries.
  3. Shut down the PC. Not restart—shut down completely. Wait 15 seconds.
  4. Unplug the external drive.
  5. Boot Windows. After the desktop loads, plug the drive into a different port.

What this does: by removing all USB driver entries and fully powering off, you flush any stuck PCIe state on the motherboard's chipset. The transport layer gets a clean initialization.

If the drive still fails after this, plug it into another PC. If it works there, your motherboard's USB controller is failing. If it fails everywhere, the enclosure's bridge chip is dead—replace the enclosure. I've had three cheap Sabrent enclosures fail exactly this way after 14 months of use.

Pro tip: For internal SATA drives hitting this error, check the SATA cable first. SATA cables fail more often than people realize—the locking tab breaks, the connector loosens, and the transport layer sees intermittent connection. Swap it with a new one from a reputable brand (Startech or Monoprice).

Related Errors in Windows Errors
0x80042308 System Restore Service Disabled – Fix It in 3 Steps 0xc000021a BSOD 0xc000021a: Critical System Process Failure Fix 0X00001075 Fix ERROR_WMI_READ_ONLY (0x00001075) – WMI Data Item Is Read-Only 0X80280015 Fix TPM_E_RESOURCES 0X80280015: TPM Runs Out of Memory
ERROR_MEDIUM_NOT_ACCESSIBLE 0x000010E3 transport cannot access the medium Windows 10 error code 0x10E3 Windows 11 error code 0x10E3 USB device not accessible medium not accessible fix Windows storage error 0x10E3 transport medium error Windows removeable storage access denied fix 0x000010e3 Windows 10

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.