Fix ERROR_INVALID_TARGET_HANDLE (0x00000072) in Windows

What triggers this error?

You're working on a file, maybe a large Excel sheet or a project file in Visual Studio, and suddenly Windows throws a 0x00000072. The full message: "The target internal file identifier is incorrect." I've seen this most often when copying files between drives, during program installations, or when opening a corrupted document. The error means Windows lost track of a file's internal handle—think of it like a library misplacing a book's catalog card. The book's there, but the system can't find it.

Before you panic, let's get this sorted. I'll start with the quickest fix (under 30 seconds), then a medium one (5 minutes), then the deep stuff (15+ minutes). Stop when the problem's gone.

Fix 1: Restart and retry (30 seconds)

I know what you're thinking: "Really? Reboot?" Yes, really. This error often happens when a program holds a corrupted handle after a crash or a bad read. A restart clears all handles, flushes memory, and gives the file system a clean slate.

1. Save your work in any other open programs.
2. Restart your PC (Start > Power > Restart). Not Shutdown, not Hibernate. A full restart.
3. Try the operation that triggered the error again.

If it works, you're done. If not, move on.

Fix 2: Run Check Disk and System File Checker (5 minutes)

This is the sweet spot. The error often hides in file system corruption or a bad system file. Let's hammer both.

Check Disk (chkdsk)

Open Command Prompt as Administrator. Press Windows Key + X, select "Terminal (Admin)" or "Command Prompt (Admin)". Then type:

chkdsk C: /f /r

Replace C: with the drive where the error appears (e.g., D: for external drives). The /f flag fixes errors, /r locates bad sectors and recovers data. You'll get a prompt to schedule the scan on next reboot. Type Y and restart. Wait—this can take a while on large drives (30 minutes to hours). Let it run.

System File Checker (SFC)

After chkdsk finishes, open Command Prompt as Admin again and run:

sfc /scannow

This checks Windows system files for corruption. If it finds problems, it'll try to fix them. If you get a "Windows Resource Protection found corrupt files but was unable to fix some of them," run DISM /Online /Cleanup-Image /RestoreHealth next, then repeat SFC. Yes, it's a chain, but it works.

I've seen this combo fix 80% of 0x00000072 errors on systems with failing hard drives or from improper shutdowns (thanks, power outages). Restart and test your operation again.

Fix 3: Advanced — Check RAM and drive health (15+ minutes)

If the error persists, the problem is deeper. Corrupt RAM can mangle file handles before they even reach the disk. Failing drives can produce bad metadata. Let's rule both out.

Test your RAM with Windows Memory Diagnostic

1. Press Windows Key + R, type mdsched.exe, hit Enter.
2. Select "Restart now and check for problems (recommended)".
3. Your PC will reboot into a blue memory diagnostic screen. Let it run (may take 30+ minutes).
4. When done, it reboots to Windows. Check the results in Event Viewer: open Event Viewer, go to Windows Logs > System, filter by source "MemoryDiagnostics-Results". If you see errors, your RAM is bad—replace it.

I had a client whose PC crashed twice a day with this error. Turned out one RAM stick had a single bad cell. Swapped it, problem vanished.

Check drive health with SMART data

Download a free tool like CrystalDiskInfo (portable version). Open it and check your drive's "Health Status." If it says "Caution" or "Bad," the drive is failing. Backup your data immediately and replace the drive. If the status is "Good" but you see high "Reallocated Sectors" or "Current Pending Sector" counts (over 10), that drive is on its way out anyway.

Alternatively, use WMIC in Command Prompt (Admin):

wmic diskdrive get status

If any drive returns "Bad" or "Unknown," replace it.

What if nothing works?

If you've done all three and the error still shows up, you're likely dealing with a specific software bug. Update the program that triggers the error (especially if it's a game or heavy app). Check the vendor's support forums for a patch or workaround. Worst case: backup your data, format the drive, and reinstall Windows. But that's a last resort—I'd only go there if you're also seeing other errors like 0x0000003B or frequent BSODs.

I've been in support for years, and this error is a pain, but it's almost always solvable with the steps above. You've got this.