After DoD Wipe Cannot Install OS

The correct answer is Post #52. Install the Intel Rapid Storage Driver.

Okay, one more idea. If you still want to pursue this, maybe we can look at Windows installation logs to try to figure out exctly what is happening. I'm not really too up on Windows installation logs so I need to research this further, but here is an article with some very basic information:


Let me dig further and see if I can come up with something resembling a logical plan .

Please bear with me, this might take me a day or so. Right now, I'm not even in front of a good machine for testing, any from main machine at a laptop for now.

I'll report back when I have more. If anyone else thoughts in this regard, please do share!

One more thought: If you have another system to which that SSD could be connected, you might try connecting it and running a utility that can read the SMART data from that drive to see if the drive itself is reporting any errors.

Okay, if you still want to see if we can figure out what went wrong, let's see if can gather any info from the log files.

Try connecting that SSD to another system, or, if you get Windows installed on a different drive in this same system, it's okay to connect it there as well. The point is simply that we want to access that drive and see if we can get to the log files.

Navigate to whatever drive letter the \Windows folder is on for that drive and go into \Windows\Panther. Grab any files with a .log extension.

Next, go to that same drive \Windows\inf and grab the file Setupapi.log

ZIP all these files and attach to this thread.

NOTE: It is possible that Windows may not let you access the drive due to NTFS security. If that happens, take note of the drive letter for that drive. Use that drive letter with a colon after the letter in place of x: in the below commands.

Open an elevated command prompt to run these commands:

C:\windows\system32\takeown /f "x:\*.*" /r /d y icacls "x:\*.*" /T /grant %username%:F

Hopefully this will allow you to get access.

Why did you wiped the SSD using that DoD program? Did you had any issues before?
For what I have seen on this thread, I would say that your drive has a problem.

As your ENVY Phoenix 860-180st is a 6th gen, to install Win 11 you need to tweak the Win 11 installation files. Did you followed Brink tutorial I've posted?

I just wonder, if too many people try to treat their SSD like an old standard hard drive. ???
SSD's are NOT hard drives! They are a totally electronic device, and require totally different care.
The first thing I ever learned about SSD's, it that you NEVER try to Defragment one. Most have their own built in data management logic.
And the life of an SSD is rated in the number of Writes that you do to the drive.

There have been some really good articles written, mostly by drive manufacturers, about the care and feeding of the SSD.
I would have to guess that a DOD Wipe is NOT recommended. And why would you?

When I'm installing Windows to any drive, I let the installer delete all the partitions on the drive, and then perform its own format and partition creation. That insures that the drive is properly partitioned and formatted for the new OS.
Out of 50+ installs, I've never had one fail, whether writing to an HD or SSD.

Happy 2024, Mates!
TM

I'm still not buying that the drive has "failed". First of all, it was failing at a consistent point in time so we for sure that it is not one specific area of the drive that has a problem. I'm still highly interested in seeing if we could pull logs from that disk, assuming that the OP still has any interest in pursuing this further.

hsehestedt said:

I'm still not buying that the drive has "failed". First of all, it was failing at a consistent point in time so we for sure that it is not one specific area of the drive that has a problem. I'm still highly interested in seeing if we could pull logs from that disk, assuming that the OP still has any interest in pursuing this further.

Click to expand...

The last post from the OP was installing to one of his HDDs and so far was installing fine. We'll have to wait for him to report back success or not. I'm opposite of you and think he toasted the SSD running the wipe utility. Inquiring minds are still curious.

BamaInArk said:

Inquiring minds are still curious.

Click to expand...

Ditto! Dying to know. You may be right, there could be some problem with the SSD, but usually when data can be copied to an SSD just fine and it fails at a very specific point, as is the case here, where it fails right as it is setting the SSD as the boot device, that is typically something other than a hardware failure. It's usually a problem with how the drive was configured, a problem with the driver, etc.

But, you could be right, it may be some really odd issue. I want those logs to see exactly what it was doing when it went belly up.