This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I just did a clean install of Windows 7 Professional. This was to install it on one of two new identical 500 gb hard drives.
Upon getting it running, I went to disk management to format the drive I didn't install windows on. It seemed to work fine. I began copying files onto it, and while that was going I went to close the computer up, which I had left open in case I needed to tighten connections. As I did so, a cord pushed against a fan, making a noise. I canceled the file transfer, waited for it to finish canceling, then cut the power to the computer so I could get the cord off the fan quickly.
Upon reset, the drive no longer appeared on the My Computer screen. I went to disk management, and it showed as present and partitioned, but had no volume letter or name. When I tried to assign, I recieved the error message "The operation failed to complete because the Disk Management console view is not up-to-date. Refresh the view by using the refresh task. If the problem persists close the Disk Management consol, then restart Disk Management or restart the computer." So I refreshed. The problem persisted, so I restarted. Still had the problem, so I deleted the partition (which works) then tried to create a new one, and got the message again. This resulted in an apparent partition with no drive letter. I then deleted the partition and restarted the computer.
Thinking that maybe I should have done a complete rather than quick format, I told disk manager to create a new volume while leaving the "quick format" box unchecked. It processed for a few minutes, then gave me the error message again, and once again displayed an unnamed partition on the disk.
"Mark partition as active" has no apparent effect, "change drive letters and paths" gives the not up to date message, "format" give the "an unexpected error has ocurred. CHeck the System Event Log for more information on the error" message.
"Delete partition" seems to work fine, "properties" gives the not up to date error message.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hey in case it helps anyone, I was finally able to resolve this simply by writing zeros to the drive, uninstalling it in Device Manager, and then restarting the computer. After that, Windows recognized the drive as new hardware, and I was able to partition and format it easily in Disk Management.
I have precisely the problem described and have been thus far unable to find a solution. In my case, I transferred the entire contents of my C: drive to a new SSD, then deleted the partitions from the old drive using Disk Management. When trying to create a new primary partition, I got the error described by Benjmn above, with exactly the same subsequent results.
Using diskpart was no more fruitful. I'm able to create the partition, but not assign a drive letter. When trying to assign a drive letter, it says "no volume specified," but since the volume isn't listed in "list volume," I cannot select the volume.
In my case the drive was perfectly healthy until I deleted the old partitions, so I doubt that this is a hardware error (though at this point I'm starting to wonder if the firmware of the drive or a setting on it has been corrupted).
Does anyone have a solution for this problem? Everything I've been able to find online just says to use diskpart.
RMA the drive to the manufacturer. You state it was new in December, so there's a 3 or 5 year guarantee on the drive (but not the data!). Cutting the power to the computer probably produced a spike which could well have killed the drive.
