Chkdsk Deleted My Files? How to Recover Them from FOUND.000 (2026)

If you ran a disk check and your files seemed to vanish, take a breath: chkdsk almost certainly did not delete them. The confusing part is real, but the fix is usually straightforward. Here is what actually happened, and how to get your data back.

What chkdsk really did

When you run chkdsk /f or chkdsk /r, Windows repairs the file system's bookkeeping. Along the way it often finds clusters of data that no longer have a valid directory entry - orphaned fragments, or pieces of files that were cross-linked. Instead of deleting them, chkdsk collects them into a hidden folder at the root of the drive called FOUND.000 (then FOUND.001, and so on), saving each fragment as a file named FILE0000.CHK, FILE0001.CHK and upward.

So your files are not gone. They have been renamed to anonymous .chk fragments and tucked into a folder that Windows hides by default. That combination - hidden folder, stripped filenames - is exactly why it looks like a deletion.

Step 1: reveal the FOUND.000 folder

Because FOUND.000 is both hidden and a protected system folder, you have to unhide it:

• In File Explorer, open Options > View, enable Show hidden files, folders and drives, and uncheck Hide protected operating system files.
• Look at the root of the affected drive, for example C:\FOUND.000.
• From a command prompt you can also run dir /a C:\ to list hidden and system entries.

Inside, you will see the .chk files. That is your recovered data, waiting to be re-identified.

Step 2: turn .chk fragments back into real files

A .chk file is a block of your data with its name and extension removed. To make it usable again:

• If you know what a fragment should be, rename the extension (for example FILE0000.CHK to photo.jpg) and try to open it.
• If you are not sure, use a file-type identifier that reads the file's header signature and tells you whether it is a JPEG, PDF, DOCX and so on, then rename accordingly.
• Expect a mix: some fragments open perfectly, while others are incomplete because the original file spanned clusters chkdsk could not stitch back together.

Step 3: when FOUND.000 is not enough, recover the originals

Sometimes the folder is empty, or the .chk fragments are unusable. In that case, switch to standard deleted-file recovery, which reads the raw disk and rebuilds files by their signatures rather than relying on chkdsk's fragments.

The single most important thing here is to stop writing to the affected drive. Every new write risks overwriting the very data you want back. Then scan with recovery software: the free, open-source PhotoRec carves files out by type and costs nothing, while commercial tools add file previews and a friendlier workflow. We compare the free options in our TestDisk vs PhotoRec guide, and the paid ones in our best data recovery software roundup.

The one time to be cautious with chkdsk

There is an important exception. If the drive is behaving like it is physically failing - clicking, vanishing from the system, or throwing repeated read errors - then running chkdsk /f or /r on it can do real harm. A disk repair forces a struggling drive to work hard, and that stress can push a recoverable disk over the edge. On suspected hardware failure, do not run chkdsk on the original. Image the drive first (for example with ddrescue) and do all your recovery work on the clone. That way, chkdsk's fragments and any recovery attempt come out of a safe copy, not the failing disk itself.

The bottom line: chkdsk is a repair tool, not a shredder. Nine times out of ten, "chkdsk deleted my files" means "chkdsk moved my files into a hidden folder", and a few minutes of unhiding and renaming - or a signature scan when that falls short - gets them back.