“You need to format the disk”
The partition was found but the file system inside cannot be identified. Usually boot sector damage — and most file systems keep a backup copy elsewhere on the volume that a recovery can rebuild from.
Boot sector
Windows has looked at the volume, failed to make sense of the structure describing it, and offered the only thing it knows how to do — write a fresh one. Your files are almost certainly still there. What has failed is a few kilobytes describing where they live.
“Access is denied” is a permissions problem. “The parameter is incorrect” is file-system damage. “Not formatted” is a missing partition structure. Three different faults, and none of them is asking to be formatted.
Windows is telling you it cannot read a structure. It is not telling you the disk is empty.
“You need to format the disk before you can use it” sounds like advice. It is closer to an admission: the operating system has looked at the volume, failed to make sense of the structure describing it, and offered the only thing it knows how to do about that — write a fresh one.
Your files are almost certainly still there. What has failed is the small amount of data describing where they live: a partition table at the front of the disk, or a boot sector at the start of the volume. Between them those occupy a few kilobytes on a drive that may hold terabytes.
Click Format and Windows writes new, empty structures over the damaged ones. The files remain physically present, but the record of how they were arranged is replaced with a record of an empty disk. Still recoverable, and materially harder — usually as carved files with no names and no folders.
The exact wording narrows it considerably, so it is worth noting which you saw.
The partition was found but the file system inside cannot be identified. Usually boot sector damage — and most file systems keep a backup copy elsewhere on the volume that a recovery can rebuild from.
Shown in Disk Management, and it means the partition table at the very front of the drive has gone. The capacity is usually correct, which tells you the drive itself is responding normally.
Same underlying situation, phrased by a different tool. Structure damaged, contents intact.
Frequently permissions rather than damage, particularly on a drive moved between machines. Worth checking ownership before assuming corruption.
None of them involve clicking the button.
Not Format, not Repair, not Initialize. Cancel and unplug. Every one of those buttons writes to the disk.
Which message, and in which tool. It narrows the fault before anything is opened, and it is the first thing we ask on the phone.
If the message mentions access being denied rather than formatting, try taking ownership of the volume first. That costs nothing and occasionally resolves it entirely.
It makes a file system consistent by discarding what it cannot reconcile — which on a damaged volume means deleting the records a recovery would rebuild from.
Read-only tools on a healthy drive can rebuild a partition table successfully. Install to a different drive and recover to a third location.
The reconstruction depends on the fact that file systems announce themselves.
Every file system writes a recognisable signature where its volume begins — NTFS, exFAT, FAT32, APFS, HFS+ and ext all have distinctive boot sectors or superblocks. Scanning an image of the drive for those markers locates where each volume actually starts, regardless of what the missing table used to say.
From there the volume size is derived from the file system’s own records and a corrected partition structure rebuilt in the image. Where the boot sector itself is damaged, most file systems keep a backup copy — NTFS at the end of the volume, ext in its superblock copies — and the volume is rebuilt from that instead.
All of it happens against a read-only image, so the original is never written to. That is the difference between this and clicking Format: one rebuilds the map, the other replaces it. Single drives in Manchester are from £300 +VAT after a free 48-hour diagnostic, and these are usually among the quicker recoveries when the hardware is sound.
No. That message means Windows cannot read the structure describing the volume, not that the disk is empty. Formatting writes new empty structures over the damaged ones — the files remain but the record of how they were arranged is replaced.
Not immediately, but it makes recovery materially harder. Your files stay physically on the disk; what goes is the map. Recovery afterwards usually returns carved files with no names and no folder structure, which on a drive of documents is a much worse outcome.
Damage to a few kilobytes describing the volume — a partition table at the front of the disk or a boot sector at the start of the volume. Commonly from an interrupted write, a power cut, unplugging a drive mid-operation, or bad sectors landing in that region.
Closely related. Not initialized means the partition table has gone; needing to format means the file system inside a found partition cannot be read. Both are structural damage with the data intact underneath, and both offers should be declined.
Sometimes, if the drive is mechanically healthy. Read-only recovery tools can rebuild a partition table by scanning for file system signatures. Install the software to a different drive and recover to a third location — and stop if the drive is making any noise.
If the structure is rebuilt rather than carved, yes — the volume mounts as it was. That is only possible while the original structures survive, which is exactly what clicking Format destroys.