0XC0000464

Fix STATUS_DEVICE_UNREACHABLE (0XC0000464) - Source Can't Talk to Dest

This error pops up when Windows can't move data between two devices—usually a USB drive and internal disk. Bad cable, corrupted storage, or driver issue.

You try to copy a file from your USB drive to your laptop, and boom—Windows throws up the STATUS_DEVICE_UNREACHABLE error (0XC0000464). The full message reads: "Data cannot be moved because the source device cannot communicate with the destination device."

I've seen this error hundreds of times on Windows 10 and 11. Usually happens when you're copying between an external USB hard drive and your internal SSD. Sometimes it's a thumb drive to your desktop. The core problem? Somewhere in that chain, the two devices lost the ability to talk to each other.

Let's walk through the three most common causes. I'll start with the one that fixes 80% of cases, then move on to the others.

Bad or Loose USB Cable (Most Common)

Nine times out of ten, this is a cable issue. The USB cable looks fine, feels fine, but internally the data lines are damaged. You've bent it one too many times, or a cat chewed on it, or it's just cheap manufacturing. The devices can power up through the cable—so the drive spins or the thumb drive lights up—but the data lines are broken. Windows can see the device exists, but can't actually move data across the broken wires.

What you'll see: The drive appears in File Explorer. You can even browse folders sometimes. But the second you try copying a file larger than a few KB, the error pops up.

How to confirm it's the cable: Try a different USB cable. The one that came with your phone is fine for testing. Don't use a charging-only cable—those don't have data lines. Look for a cable marked with the USB data symbol (the trident logo). If you're using a USB-C to USB-A cable, make sure it's rated for data, not just charging.

Fix it:

  1. Unplug the current cable completely.
  2. Plug in a known-good data cable. I keep a short Anker or Belkin cable in my bag for exactly this.
  3. Reconnect the drive. Wait 10 seconds for Windows to re-recognize it.
  4. Try the file copy again.

After the swap, if the copy works, you're done. Toss the old cable. Don't risk it again.

I once spent two hours debugging a user's "corrupted drive" only to find the cable had a frayed section near the connector. New cable, instant fix. Check the cable first—it's the cheapest and fastest test.

Corrupted USB Drive or External Hard Drive

If a different cable doesn't fix it, the drive itself might be the problem. This happens when the file system gets corrupted—maybe you yanked the drive without safely ejecting, or there was a power outage while writing data. The drive's file allocation table gets confused. Windows sees the drive, but when it tries to read or write data, the corruption causes the communication to fail with error 0XC0000464.

Scenario: You were copying a large video file to a 64GB USB 3.0 thumb drive. The copy seemed to hang, so you pulled the drive. Next time you plug it in, you get this error.

Fix it with CHKDSK:

  1. Open File Explorer. Note the drive letter of the problematic device. Let's say it's E:.
  2. Press Win + X, then select Windows Terminal (Admin) or Command Prompt (Admin). You'll get a UAC prompt—click Yes.
  3. In the terminal window, type:
    chkdsk E: /f /r
    Replace E: with your drive letter. The /f flag fixes errors, and /r locates bad sectors and recovers readable data.
  4. Press Enter. CHKDSK will run. It can take 10-30 minutes depending on the drive size and how corrupted it is. Let it finish. Do not close the window or unplug the drive.
  5. When it finishes, you'll see a summary. If it fixed errors, you'll see a message like "Windows has made corrections to the file system."
  6. Close the terminal. Try copying your file again.

CHKDSK fixes minor corruption about 70% of the time. If it can't repair, you might need to format the drive. But before you do that, try the third fix—driver conflicts can also cause this.

Stale or Conflicting USB Drivers

Sometimes the hardware is fine, but Windows has corrupted or outdated drivers for the USB controller. This is more common in Windows 11 after a feature update—the update can overwrite or break USB controller drivers. The result? Intermittent communication failures between devices.

Scenario: You just updated to Windows 11 23H2. Now every time you plug in a specific external drive, you get error 0XC0000464. But that drive works fine on a different computer. That points to a driver issue on your machine.

Fix it by reinstalling USB controllers:

  1. Right-click the Start button and select Device Manager.
  2. Scroll down and expand Universal Serial Bus controllers. You'll see a list of items like "USB Root Hub" and "Generic USB Hub."
  3. Right-click each entry that says USB Root Hub or Generic USB Hub and select Uninstall device. Do this for all of them. Don't worry—they'll reinstall automatically on reboot. Important: Don't uninstall anything marked "Host Controller"—that's your chipset driver. Just the Hubs.
  4. After you've uninstalled all the Hubs, restart your computer.
  5. When Windows boots back up, it will automatically reinstall the drivers. You don't need to do anything—just wait a minute after the desktop loads for the drivers to fully install.
  6. Try plugging the drive in and copying the file again.
  7. If that doesn't fix it, you can also try updating the chipset driver from your motherboard manufacturer's website (for desktops) or your laptop manufacturer's support page. For Windows 11, run Windows Update and check for optional driver updates under Settings > Windows Update > Advanced options > Optional updates.

    I've seen this fix work after a Windows 11 22H2 update broke USB communication entirely. Uninstalling the hubs and letting Windows rebuild them solved it.

    Quick-Reference Summary

    CauseWhat to CheckFix
    Bad USB cableCable visible damage, try another cableReplace cable with a known data cable
    Corrupted driveFile system errors, drive appears but read/write failsRun chkdsk X: /f /r in Admin Terminal
    Stale or conflicting USB driversError appears after Windows update, drive works on other PCUninstall USB Root Hubs in Device Manager, restart
Related Errors in Windows Errors
0XC01C0017 Fix STATUS_FLT_INVALID_CONTEXT_REGISTRATION (0xC01C0017) 0X00000160 ERROR_FAIL_RESTART (0X00000160): Fix Windows Restart Failure 0X80040010 OLE_E_NOT_INPLACEACTIVE (0x80040010) fix: object context mismatch 0XC00D105A Fix NS_E_WMR_PINNOTFOUND (0XC00D105A) on Windows 10/11

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.