You open Disk Management looking for a drive that vanished from File Explorer. The disk is there. It’s listed as Basic and Online, and the capacity is correct — 2000 GB, or 4 TB, or whatever you bought.
But the bar representing it is one solid black block labeled Unallocated, and right-clicking offers you “New Simple Volume.”
Don’t take it up on that.
This is not the same as “not initialized”
Worth separating these, because they get confused constantly and the diagnosis differs.
Unknown, Not Initialized means Windows couldn’t read the partition table at all and thinks the disk has never been set up. Covered in detail here.
Basic, Online, Unallocated — what you’re looking at — means Windows read the partition table fine. The table is intact and valid. It just doesn’t contain an entry describing your partition anymore.
The second one is usually the better position to be in. The disk is communicating normally and reporting its correct size, which tells you the drive electronics and firmware are healthy. What’s missing is one small record.
What happened to the partition entry
A tool wrote a fresh partition table. Windows Setup pointed at the wrong disk, a Linux installer, a disk utility, a partition manager that was interrupted. This is the most common cause and the most recoverable.
Bad sectors in the first sectors of the disk. The partition table lives in a tiny region at the very front. Damage there is invisible to the other 99.99% of the drive but takes out the map to all of it.
Interrupted partition resize or conversion. Shrinking, expanding, or converting MBR to GPT rewrites the table. Power loss partway leaves it half-written.
A failed enclosure on a hardware-encrypted external. If you pulled a drive out of a WD or Seagate case and connected it directly, unallocated space is exactly what you’d expect to see — the data is encrypted and the key lives on the bridge board you just removed. This trap catches people regularly.
Why “New Simple Volume” is the wrong click
Creating a new volume writes a fresh partition entry and a new empty file system at the start of that partition — new boot sector, new MFT, new everything.
Your files are sitting in the middle of the disk, untouched, waiting for something to point at them again. A new volume doesn’t point at them. It overwrites the exact structures that a recovery tool would have used to find them, and replaces them with a blank index.
Before that click, this is one of the more straightforward recoveries there is. After it, it’s a much harder one.
Free evaluation. Firm quote before any work begins.
Why the odds here are good
A partition entry is a small record — a start point, a length, a type. The file system it pointed at is still fully intact somewhere on the disk.
NTFS volumes begin with a recognizable boot sector, and NTFS keeps a backup copy of it at the end of the volume. Scanning the disk for those signatures locates where the partition started and how long it ran, and from there the volume can be read normally: filenames, folders, timestamps, all of it.
These recoveries are frequently complete. It’s logical work — the lower end of my pricing — provided nothing has been written over the top.
What to do now
- Don’t create a volume, don’t initialize, don’t format.
- Power the drive down if the data matters. If it’s an internal disk in a machine that’s still running, shut the machine down.
- If it’s a shucked external, put it back in its enclosure before concluding anything. That alone resolves a fair number of these.
- Note what happened right before. An OS install, a partition tool, a power cut — that history points straight at the cause.
The bottom line
Unallocated on a disk that reports the right size means one small record is missing, not that your data is gone. The recovery is usually straightforward and often complete. The one thing that changes that is accepting Windows’ offer to make a new volume.
Disk showing unallocated? Start a case — and tell me what you were doing right before it happened. An interrupted resize and a mistargeted OS installer look identical in Disk Management but need different approaches.