NTFS is telling you it cannot read the record describing where something lives. The file’s actual contents are frequently untouched — which is why the standard fix is also the standard way people lose it.
Every file and folder on NTFS has an entry in the master file table. When that entry cannot be read, Windows reports corruption even though the contents are still sitting on the disk.
chkdsk rewrites the file table to make it internally consistent, and it achieves that by discarding entries it cannot reconcile — which is precisely the information a recovery would have used.NTFS keeps a master file table — the $MFT — holding a record for every file and folder: its name, its size, its permissions, and the list of disk locations where its contents actually sit. When Windows cannot read the record for something you have asked for, it reports that the file or directory is corrupted and unreadable.
Note what that does and does not say. It says the description could not be read. It says nothing about the contents, which in most cases are entirely intact and simply unreachable because the map pointing at them is damaged. That distinction is the whole reason recovery works on these.
The commonest cause on an external drive is removing it while Windows was still writing — the file table update is interrupted partway and left inconsistent. Power loss on an internal drive does the same. Neither necessarily indicates a hardware problem, and both are frequently fully recoverable.
The other cause is bad sectors: the region of the disk holding part of the $MFT can no longer be read reliably. That is a hardware problem and it tends to spread, which changes the urgency considerably. The pattern distinguishes them — a single folder affected after a bad unplug is one thing; several files failing, growing over days, on a drive that has become slow, is another.
chkdsk exists to produce a valid file system, not to preserve your data. Where it finds a record it cannot reconcile it will delete the entry, truncate the file, or move fragments into found.000 as numbered files with no names. On a healthy drive with minor damage that is an acceptable trade and usually works. On a drive with failing sectors it is not, for two reasons: the repair writes to a disk that is struggling, and /r forces a full surface scan — hours of exactly the wrong stress.
If the drive is slow, noisy or throwing multiple errors, chkdsk is the single most likely action to make the situation permanent.
Try reading the drive on another machine, and copy off whatever will copy — starting with what you would most hate to lose, and accepting that some files will fail. If it is an external, try a different cable and port first; a failing bridge produces this error on a perfectly healthy disk.
Where the drive is failing, recovery means imaging it read-only past the bad areas and rebuilding the file table from the copy, so the original is never written to. A single drive is from £300 +VAT after a free 48-hour diagnostic, and most jobs are no fix, no fee.
That NTFS could not read the master file table record describing that file or folder — its name, size and the locations holding its contents. It refers to the index entry, not the data, and the contents are frequently still intact on the disk.
Only if you are confident the drive is healthy. chkdsk aims at a consistent file system rather than your files, so it deletes or truncates entries it cannot reconcile, and /r forces a full surface scan. On a failing drive it is the likeliest single action to make the loss permanent.
Most often an external drive removed while Windows was writing, or a power loss mid-update, which leaves the file table inconsistent. The other cause is bad sectors in the region holding the master file table — that one is a hardware fault and tends to spread.
Usually. The drive is imaged read-only and the file table rebuilt from the copy, or files carved out by signature where the table is beyond repair. The original is never written to, so nothing that happens during recovery can make matters worse.
A single drive is from £300 plus VAT, fixed in a written quote after a free 48-hour diagnostic. Most jobs are no fix, no fee. Send external drives complete with their enclosure rather than removing the disk.