How to Fix ERROR_NO_MORE_FILES (0X00000012) on Windows

Cause 1: Corrupted directory structure — run chkdsk

This is the most common reason you see 0X00000012. Windows tries to read a folder, finds garbage in the index, and gives up. I've seen this happen after a blue screen, a power outage, or even a bad USB drive eject. The fix is simple: run chkdsk on the drive.

1. Open Command Prompt as administrator (right-click Start, choose Command Prompt Admin or Terminal Admin).
2. Type: chkdsk c: /f (replace c: with your drive letter).
3. Hit Enter. If it's the system drive, it'll ask to schedule at next reboot — type Y and restart.
4. Let it run. Could take 10–30 minutes depending on drive size.

Had a client last month whose entire print queue died because of this. Turns out their shared folder on the server had a corrupted index. One chkdsk later, everything worked again. If chkdsk finds bad sectors, run it again with /r to recover readable data.

Cause 2: Old or buggy software with broken file enumeration

Some programs don't handle large folders well. I've seen this with old backup tools, poorly written file managers, and even some media players from 2015. They use the FindFirstFile/FindNextFile API and when a folder has thousands of files, they trip over their own logic.

Quick test: open the folder in File Explorer. If Explorer also shows the error or hangs, it's a file system issue — go back to Cause 1. If Explorer works fine but your program doesn't, the app is buggy. Check if the program has an update or a patch.

• Right-click the program's shortcut and go to Properties → Details to see the version.
• Search the vendor's site for a newer version.
• If it's some old legacy app, try running it in compatibility mode for Windows 7 or Vista.

Cause 3: File system filter driver conflict

Less common, but I've nailed this down a few times. Antivirus software, backup agents, or cloud sync clients (Dropbox, OneDrive) install file system filters. When they misbehave, they intercept file enumeration calls and return junk — which triggers 0X00000012.

To test this, temporarily disable real-time protection in your antivirus — or better, boot into Safe Mode with Networking. If the error goes away, you've found the culprit.

Fix: uninstall the conflicting software, or check for updates. For cloud sync clients, pause sync and try again. Had a client whose Dropbox desktop app was causing this on a Windows 10 machine — a reinstall fixed it immediately.

Quick-reference summary table

If none of these work, run System File Checker (sfc /scannow) from an admin command prompt — it'll fix corrupted Windows system files. And if you're still stuck, check the Windows Event Viewer for more clues around the time the error popped up. Good luck.