0XC000016A

0XC000016A Disk Error – Fix When Retries Fail

Your disk throws this error when a read or write keeps failing even after retrying. It's a physical or driver problem, not a corrupt file.

When This Error Hits

You're copying a big file from your external drive, or maybe Windows is loading a program from your secondary hard drive. Suddenly it freezes. Then a popup: STATUS_DISK_OPERATION_FAILED (0XC000016A). The message says the system tried again and again, but the disk didn't cooperate. This isn't a random glitch. It means the drive physically couldn't complete the command.

I've seen this most often on USB external drives that are about 5 years old, or on internal SATA drives in laptops that get knocked around. One specific trigger: you're using a Western Digital My Passport drive on Windows 10 version 22H2, and you try to cut a folder instead of copy. The error shows up right after the progress bar stalls at 99%.

What's Actually Happening Here

The operating system sends a command to the drive controller. The controller tries to read or write the data. If it fails, it retries automatically—Windows' storage stack does this a few times. After those retries fail, the system gives you this error code. The number 0XC000016A is a status code meaning “the operation failed, and retries didn't help either.”

There are three possible causes, in order of likelihood: 1) physical bad sectors on the disk, 2) a failing SATA or USB cable/port, 3) a buggy or outdated driver. Notice I didn't list “corrupt files” or “virus.” Those can cause other errors, but not 0XC000016A. This is a hardware-level failure, not a software mess.

The Fix – Step by Step

Step 1: Check the Cable and Port

I skip the fancy tools first. Unplug the drive. If it's internal, open your case and reseat the SATA cable at both ends—drive and motherboard. If it's external, swap the USB cable with a known good one. Plug it into a different USB port, preferably on the back of the PC (directly on the motherboard, not a front panel hub). I've fixed this error more than once just by using a different cable. The reason: a loose connection makes the drive drop out mid-operation, and retries can't fix broken electrical contact.

Step 2: Run the Built-in Disk Check

Open Command Prompt as admin. Type: chkdsk X: /f /r — replace X with your drive letter. The /r flag tells it to find bad sectors and recover readable data. This can take an hour or more on large drives. Let it finish. If it hangs or takes more than 12 hours, the drive is dying—move on to Step 4.

Step 3: Update the Storage Driver

Go to Device Manager. Expand Disk drives. Right-click your drive, choose Update driver > Browse my computer > Let me pick from a list. Choose the “Standard NVM Express Controller” if it's an NVMe drive, or the “Standard SATA AHCI Controller” for SATA drives. This replaces the vendor- specific driver with Microsoft's generic one. Why? Because third-party drivers (especially from OEMs like Dell or Lenovo) sometimes have bugs that cause retry loops. Microsoft's generic driver is boring but stable.

If that doesn't help, go to your motherboard manufacturer's site (or the PC maker's support page) and download the latest chipset and storage drivers. Install them. Reboot.

Step 4: Check S.M.A.R.T. Data

Download a free tool like CrystalDiskInfo. Open it and look at your drive's S.M.A.R.T. status. If it shows Caution or Bad, especially with a high value for Reallocated Sectors Count or Current Pending Sector Count, your drive is physically failing. You can't fix that with software. Copy off any data you care about immediately. Then replace the drive.

If It Still Fails

If you did all four steps and the error still shows up on the same drive, the drive is dead. I'm sorry. There's no magic command to fix physical damage. Your next move: buy a new drive, restore from backup. If the error is on a system drive (C:) and Windows won't boot, boot from a Windows installation USB and run chkdsk C: /f /r from the recovery command prompt. If that fails too, you're looking at a drive replacement and reinstall—or a fresh backup restore.

One last thing: if the error only occurs on one specific file or folder, not the whole drive, the file itself might be stored on a bad sector. Copy everything else off, then let the drive go. Don't trust it again for important data.

Related Errors in Hardware – Hard Drives
0XC00D0065 Fix NS_E_BAD_FSMAJOR_VERSION (0XC00D0065) on Windows 10/11 0XC000007F Fix STATUS_DISK_FULL (0XC000007F) – Simple Steps That Work 0XC01E051E Fix 0xC01E051E: Display Driver Internal Error on Windows blk_update_request: I/O error, dev sda, sector ... Disk IO Scheduler Failure on Ubuntu 22.04 – Quick Fix

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.