I accidentally deleted a partition on a GPT drive while managing disks, and now Windows shows the space as unallocated. I haven’t formatted or written new files to it yet. What reliable GPT partition data recovery software can scan the drive and restore the deleted partition or recover the files safely?
First thing: don’t write anything else to that drive. If Windows is showing it as “Unallocated” or “RAW,” it may treat the space like it’s empty, even though your files may still be there. Any new writes, temp files, updates, or repair attempts can overwrite data you still have a chance to recover.
If this is the drive you boot from, I’d take it out and connect it to another computer as a secondary drive. Running the OS from the problem disk just adds more risk.
GPT problems are scary, but they’re not always a disaster. GPT disks keep a backup header at the end of the drive, so in some cases the partition layout can be found or rebuilt. The key is to recover the files first, then worry about repairing the partition table later.
For most people, Disk Drill is probably the easiest practical option for this kind of situation. It does not just depend on the damaged partition table. It can scan the whole disk for lost data and file signatures, which is useful when Windows has given up and marks the volume as RAW. It also supports common filesystems like NTFS, exFAT, and HFS+, and the preview feature is helpful because you can check whether your files look intact before recovering them.
One rule that really matters: do not recover files back onto the same drive. Save them to a separate healthy drive with enough free space.
If you’re comfortable with command-line tools, TestDisk is worth looking at. It’s been around forever and is made for finding lost partitions and rebuilding partition entries. The scan itself is non-destructive, but it’s not exactly beginner-friendly, and you need to pay attention to what you’re doing.
gdisk is another option if the issue is specifically GPT-related. Its recovery and transformation menu can sometimes use the backup GPT header at the end of the disk to restore the primary one. Again, useful tool, but not something I’d click through blindly.
Also, if the disk shows up as a “GPT Protective Partition,” be careful. That can happen when moving drives between older 32-bit systems and newer 64-bit systems, or when a USB dock/enclosure reports sector sizes differently. If you see that, don’t run Diskpart’s “clean” command. That wipes the partition table. Pull the data off first with a recovery scanner, then decide whether to reformat or rebuild anything.
Basically, treat the drive like evidence. Don’t “fix” it first. Scan it, recover what you can to another disk, then deal with the partition repair afterward. If the drive itself is still physically healthy, there’s a decent chance your files are still recoverable.
1 Like
If the partition was only deleted and nothing has been written since, your odds are decent, but they drop fast once you start “repairing” things. Before running Disk Drill, TestDisk, or anything else, I’d make a full sector-by-sector image of the drive to another disk if the data matters. Then scan the image, not the original. That way if a recovery program hangs, misdetects the old partition, or you accidentally click the wrong write option, you still have the untouched source. Disk Drill is fine for a user-friendly file recovery pass, while TestDisk is better when you’re trying to restore the actual partition entry, but I would not let any tool write changes back until the important files are copied somewhere safe.
Your chances are much better if this is a hard drive than if it’s an SSD, even if you personally haven’t saved anything to it. On an SSD, TRIM can sometimes make “deleted but untouched” space unrecoverable pretty quickly, depending on how Windows, the controller, and the enclosure handled the delete. So don’t take “unallocated” as automatically meaning “all files are still sitting there waiting.”
For software, I’d separate two goals. If you want the partition back as a partition, TestDisk is usually the right kind of tool, but only if it finds the old boundaries cleanly. If you mainly want the files, use a file recovery tool like Disk Drill or R-Studio and recover to another disk. Disk Drill is easier to read for a normal user, but don’t judge success just by whether it lists filenames. Preview a few real files first, especially large ones like videos, archives, PST files, VM images, or project files.
A detail people often forget: if that partition was BitLocker-encrypted, most generic scans are going to look disappointing unless you still have the BitLocker recovery key and the tool can see enough of the original volume structure. In that case, cloning the disk first matters even more, because rebuilding the wrong partition entry by a few sectors can turn a recoverable encrypted volume into a bigger headache. If the data is irreplaceable, stop at imaging and scanning. Don’t let anything “fix” the GPT until you’ve copied out what matters.
The filesystem type and whether this was a plain basic disk or something like Storage Spaces, dynamic disk, or RAID matters a lot. A deleted NTFS partition on a normal GPT disk is one situation. A pooled or spanned volume is a different mess, and some “easy recovery” tools will show fragments that look promising but won’t rebuild the actual folder tree correctly.
I agree with the image-first advice, but I’d be cautious about trying to “restore the partition” as the first win. If the partition boundaries are detected perfectly, TestDisk can be great. If they’re off, you can make a clean recovery job uglier. For a normal user, I’d scan the entire physical disk, not a drive letter and not just whatever Windows shows as unallocated. In Disk Drill or similar tools, pick the disk device itself so it can look for the old volume metadata and file signatures.
Small practical warning: don’t let Windows “initialize,” “format,” “repair,” or run chkdsk on it if it suddenly offers. Those dialogs are not recovery steps. Recover the important files to a separate drive first, verify they open, then decide whether you want to recreate the partition. Getting the partition name back is nice, but getting the files back is the part that actually matters.