STATUS_DELETE_PENDING (0xC0000056) – Quick Fixes

What's Actually Happening Here

You're getting 0xC0000056 (STATUS_DELETE_PENDING) when a program or the OS tries to open a file that's already been marked for deletion. The file isn't gone yet—Windows keeps it alive until every handle to it is closed. Something still has a reference. The error name says it all: a non-close operation has been requested of a file object that has a delete pending. Translation: something tried to read, write, or query a file that's scheduled for removal.

This usually pops up during installation failures, antivirus scans, game launchers, or when you're manually deleting temp files. It's not corrupt—it's a lock conflict.

Start Here: The 30-Second Fix (Works 60% of the Time)

Reboot. Not a shutdown-restart—a full reboot. In Windows 10/11, fast startup (Hybrid Shutdown) can leave file handles dangling. So go to Start → Power → Restart. That forces a clean kernel state. After reboot, try the operation again. If the file's still problematic, delete it normally—it'll be gone.

Why this works: Fast startup saves kernel memory to disk. A full restart clears that cache along with half-open file handles. It's the cheapest fix you'll get.

5-Minute Moderate Fix: Find the Lock with Process Explorer

If reboot didn't cut it, something specific is holding the handle. You need Sysinternals Process Explorer (free from Microsoft).

1. Download and run procexp64.exe (or procexp.exe for 32-bit). No install needed.
2. Press Ctrl+F to open the search dialog.
3. Type part of the file path or name. Hit Search.
4. In the results, every process with an open handle to that file appears. Look for anything with a status column showing DeletePending or File—that's your suspect.
5. Right-click the offending process and choose Close Handle. Confirm the warning.
6. Now delete the file normally. It should go.

Real-world scenario: A friend saw this when RiotClientServices.exe wouldn't let go of a temp file after a League of Legends patch. Process Explorer found it instantly. Closed the handle, file vanished.

15-Minute Advanced Fix: Handle from Command Line + Forced Removal

When Process Explorer isn't an option (remote server, headless, or you just love the terminal), use handle.exe (also Sysinternals).

1. Download handle64.exe (or handle.exe) to a folder, say C:\tools.
2. Open an Administrator Command Prompt or PowerShell.
3. Run: C:\tools\handle64.exe -a -u "C:\Path\To\File.txt"
   Replace the path with your actual file. The -a flag shows all handles, -u shows the owning user.
4. You'll see output like:
   

   GameOverlay32.exe  pid: 12345 type: File  148: C:\Path\To\File.txt

5. Note the PID (e.g., 12345). Now decide: close the handle (risky—can crash that app) or kill the process.
6. To close a specific handle by its hex value (the number after the colon, here 148):
   

   C:\tools\handle64.exe -c 148 -p 12345 -y

   
   The -y suppresses confirmation.
7. To kill the offending process outright:
   

   taskkill /PID 12345 /F

8. After either step, delete the file.

Why step 6 works: The -c flag sends a close request to that specific handle. It's surgical—less destructive than force-killing the process. But some apps (like anti-cheat drivers) ignore handle close requests; then you have to kill the process.

If Nothing Works: Force Delete on Next Boot

When every handle is locked by system-critical processes (looking at you, svchost.exe), schedule the delete for next boot:

1. Open an elevated Command Prompt.
2. Run:

   move /y "C:\Path\To\File.txt" "C:\Path\To\File.txt.deleted"

   
   (Optionally rename it so it's harmless.)
3. Then:

   del /f /s /q "C:\Path\To\File.txt.deleted"

   
   If that fails, use a boot-time deletion tool like MoveFile (Sysinternals) or schedule a task with schtasks /create /tn "DeletePending" /tr "cmd /c del /f /q \"C:\Path\To\File.txt\"" /sc onstart /ru SYSTEM

Don't waste time on chkdsk or sfc /scannow—this isn't filesystem corruption. It's a lock. The NTFS volume is fine, the handle table is not.

Prevention

If you see this repeatedly with a specific app (game launchers, Adobe updaters, antivirus), try:

• Updating the app to the latest version.
• Running the app as administrator (sometimes it can't close its own handles without elevation).
• Adding the app's folders to Windows Defender exclusions—real-time scanning sometimes holds handles open.

That's it. 0xC0000056 is a lock, not a bug. Find the handle, close it, move on.