FOUND.000 and CHK Files: Identify and Validate the Contents

Inspect CHK fragments on separate copies, identify likely formats and verify content instead of treating extension changes as file repair.
XAppSet Team
Published on November 14, 2026

Files in a FOUND.000 folder may contain data fragments saved during file-system checking. They are candidates to inspect, not automatically complete originals. Work on copies on another device, identify the actual content, and validate it before renaming or discarding anything.

External drive, USB flash drive and an M.2 SSD beside a laptop

Preserve the folder and the surrounding context

Copy the existing FOUND.000 folder to healthy separate storage if the disk reads normally. Retain the original .chk names and record the source path and repair event. If the drive is unstable, stop ordinary copying and consider an appropriate preservation route instead.

Microsoft’s CHKDSK documentation describes saving lost allocation chains as .chk files in applicable file-system checks. That establishes a possible origin; it does not guarantee that a fragment represents a whole photo, document or video, nor that every Windows version and file system produces identical output.

Do not delete the folder merely to tidy the disk while files remain missing. Do not rerun CHKDSK to try to generate a more useful set of fragments.

Inspect before changing extensions

Enable filename-extension display so you can distinguish a real rename from changing a visible label. Keep an untouched destination copy, and perform identification on another working copy. Do not batch-rename all .chk files to .jpg or .zip based on the file types you hope to recover.

Start with size and content clues. A very small fragment is unlikely to contain an entire large original, but size alone cannot identify the format. A trusted file-identification utility or a read-only hex viewer can reveal a recognizable header in a copy. Treat that as a clue: a header can survive without the file’s end or internal structure.

Do not execute an unidentified fragment. If it appears to be a document, archive or image, open only the working copy with an appropriate application, using normal security precautions for files of uncertain origin.

Rename one candidate and test the result

If a candidate’s content supports a likely extension, rename only its working copy and try the matching application. Keep a mapping such as FILE0001.CHK → possible-photo-01.jpg alongside the original fragment. A successful open is a useful first check, not the final one.

For an image, inspect full dimensions and look for missing or distorted areas. For a document, check the needed pages and embedded content. For an archive, extract the important entries to a separate folder. A file that opens only partially should remain labeled as partial.

When a known original exists elsewhere, compare SHA-256 hashes. Equality establishes identical bytes; a mismatch may mean a different version, extra fragment data or corruption. Without a trusted original, a hash identifies your candidate but cannot prove its completeness.

If the fragments do not contain the needed files

Renaming changes a filename, not the content. It cannot join arbitrary fragments in the right order or restore absent bytes. Repeatedly trying extensions does not overcome that limit.

Check backups, application recovery copies and the original storage for surviving files. XRecovery supports finding remaining content on readable sources with file-system abnormalities; that is a separate source-scan route, not a promise to reconstruct every .chk fragment. Export any useful results elsewhere and compare them with the fragment candidates.

Keep validated files, uncertain candidates and untouched fragments separate until the missing-data task is resolved. Only then decide whether the original folder is redundant. A folder that looks like repair debris can still be the only remaining copy of useful content.

Hard drive recovery guide

Privacy Overview
XAppSet

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.