Fixing ERROR_INVALID_DATA (0X0000000D) on Windows
You're getting this error when Windows or an app says the data is corrupt or malformed. It usually happens during file transfers, app installs, or registry access.
When This Error Hits
You're copying a large file over the network, installing a driver update, or running a system backup — and boom, you get the ERROR_INVALID_DATA (0X0000000D) message. The exact text reads: "The data is invalid." I've seen this most often on Windows 10 22H2 and Server 2019 when the USN journal gets corrupted after a dirty shutdown. Another common trigger: trying to read a registry key that was partially written by a failed installer.
Root Cause — Plain English
At the kernel level, this error means a device driver or system component handed back data that doesn't match its expected structure. Think of it like a ZIP file missing half its contents — Windows can't parse it, so it bails out. The culprit here is almost always one of three things: a corrupted MFT (Master File Table) or USN journal on an NTFS volume, a botched registry hive, or a failing hard drive that returns garbage reads. Don't bother reinstalling Windows first — that's overkill in 90% of cases.
Step-by-Step Fixes
Start with the easiest checks. None of these require a reinstall.
1. Check the Event Viewer for Clues
Open Event Viewer → Windows Logs → System. Filter by source Ntfs or disk. Look for event ID 55 (corruption in file system structure) or 57 (I/O error). If you see those, your drive has physical issues. If the event says 0x13A (USN journal corruption), the fix below works.
2. Run CHKDSK with Repair
Open Command Prompt as Administrator. Run:
chkdsk C: /f /rThe /f flag fixes logical errors, /r locates bad sectors. If the volume is in use (it always is on C:), it'll ask to schedule on next reboot — say yes. This repairs the MFT and USN journal. I've fixed this error on dozens of Server 2019 boxes with this single command.
3. SFC and DISM — Don't Skip DISM
Run these in order. SFC alone rarely fixes the root cause here.
sfc /scannowThen:
DISM /Online /Cleanup-Image /RestoreHealthDISM checks component store corruption, which can cause file reads to return malformed data. Wait for it to finish — can take 20 minutes on older hardware.
4. Reset the USN Journal (If Still Fails)
If CHKDSK didn't clear it, the USN journal itself might be stuck. Reboot into Safe Mode with Command Prompt. Then:
fsutil usn deletejournal /D C:Warning: This disables the USN journal, which slows down file change notifications. Reboot normally — Windows recreates the journal automatically. This is a nuclear option, but it works when the journal is wedged.
5. Check Registry Integrity
If the error pops up in a specific app (like a custom installer or database), open regedit and export the affected key before editing. Use reg.exe to validate:
reg query "HKLM\Software\YourApp" /sIf it returns access errors or weird hex output, that key is corrupt. Restore it from a backup or remove the key and let the app remake it.
What to Check If It Still Fails
If none of the above works, you're looking at hardware failure. Run a full SMART test with vendor tools (like SeaTools for Seagate, WD Dashboard for Western Digital). Use wmic diskdrive get status in CMD — if it returns "Bad", replace the drive. Also check RAM: bad memory can cause data corruption in transit between disk and CPU. Use MemTest86 for at least one full pass. I've seen a single bad stick cause this error intermittently for months before the machine finally blue-screened.
One more thing: if this happens only on a network share, it's probably not the local disk. Check the server's event logs for disk or file system errors. A flaky network cable can also cause partial data reads — replace the Ethernet cable before blaming software.
Was this solution helpful?