Windows Error 799: Orphaned Files Recovery Directory Full
Why This Error Happens
Error 799 occurs when NTFS Self-Healing (or CHKDSK) detects orphaned files—file fragments that have lost their parent directory reference—and attempts to relocate them to the \FOUND.000 recovery directory (or subsequent FOUND.XXX folders) for manual review. This error specifically triggers when the recovery directory already contains the maximum number of auto-generated filenames (typically named FILE0000.CHK through FILE9999.CHK), leaving no available naming slots for newly recovered orphans. This is usually a symptom of severe or repeated file system corruption on the volume, often caused by improper shutdowns, failing storage hardware, or bad sectors that have generated a large backlog of unrecovered fragments over time.
Step-by-Step Resolution Guide
-
Open File Explorer and locate the recovery directories. Navigate to the root of the affected drive (e.g.,
C:\) and enable hidden/system files via View > Show > Hidden items to locate folders namedFOUND.000,FOUND.001, etc. -
Move existing recovered files out of the recovery directory. Cut the contents of
FOUND.000(and any otherFOUND.XXXfolders) and paste them into a temporary folder, such asC:\CHKDSK_Recovered\, on a different volume if possible. This frees up naming slots for the next scan. -
Delete the now-empty FOUND.XXX folders. Once contents are moved, delete the empty recovery folders to ensure a clean slate for the file system repair tool.
-
Run CHKDSK with repair flags via elevated Command Prompt. Open Command Prompt as Administrator and run:
chkdsk C: /f /r /x
This forces a dismount, fixes errors (/f), locates bad sectors and recovers readable data (/r), and forces the volume to dismount if needed (/x). Confirm the scan on next restart if the volume is in use.
- Review recovered .CHK files after the scan completes. Use a file identification tool (or manually inspect via a hex editor/appropriate app) on the
.CHKfiles in the temporary folder to determine if any contain recoverable user data; rename with the correct extension or discard corrupted fragments.
Alternative or Verification Steps
- Verify the fix: Re-run
chkdsk C: /scan(read-only mode) after the repair completes—if it reports no further orphaned file errors or Error 799 messages, the issue is resolved. - Alternative approach: If CHKDSK repeatedly regenerates massive numbers of orphaned files, run a full hardware health check (e.g.,
wmic diskdrive get statusor manufacturer diagnostic tools like CrystalDiskInfo) to rule out a failing physical disk, and consider backing up data immediately and replacing the drive if SMART errors are present.