This is a very good answer, although it does not actually erase all the data on it.
Recently a Seagate drive (1.5tb) was showing bad sectors, and was still under warranty, so I backed it all up to a new replacement drive. Then I zeroed out the old drive.
When I put in the new drive again (data only drive, one partition already initialized and formatted NTFS) windows 7 64 pro thought it was a new drive and in disk management did not give it a drive letter, and asked to initialize the drive.
I was not positive if this would wipe out the drive, but since it was asking if I wanted to initialize it MBR or GPT then I assumed it was basically creating a new MFT.
I cancelled out of that and ran the free EaseUS Partition recovery program and it immediately found the "missing" partition and all the data is there and fully recoverable. It was recovered pretty quickly, within a few hours with no issues. I am not sure
in any way shape or form why Windows 7 would suddenly want to initialize a perfectly good disk drive but it seems like some kind of error/bug to me. I am a computer tech and experienced with computers and just thought I would share this experience since it
is related to the initialize disk question. I am sure I am not the only one who will run into this problem.
FTR: I am using a newer Asrock z77-extreme4 chipset motherboard with Intel Core I7-3770k CPU, the drive in question was plugged into a SATA III port on the motherboard (no external drives or enclosures used) - Intel RST driver up to date as of today's
date.