Windows Installer Can't See Local Drive

[sapphirescales]

I just tried it again, and the output wasn't useful. I'm not sure why or how... but it doesn't work on this.

I just tried it and it works just fine. Extract all the files into a folder, then open the ".text" file in 7zip. The driver files are right there. They don't always keep the raw driver files in the .exe file itself. Sometimes there's an archive inside of an archive, like in the case of this one.

 

[Sky-Knight]

I just tried it and it works just fine. Extract all the files into a folder, then open the ".text" file in 7zip. The driver files are right there. They don't always keep the raw driver files in the .exe file itself. Sometimes there's an archive inside of an archive, like in the case of this one.

Yay for .zip files that aren't .zip.

That does get you the Optane driver set, but it's not all of them. The package has several driver sets, each with their own requirements. Still, that's the one that's the 80% use case, handy.

If you do what I did above, you'll see that's the content of the RAID sub folder. VMD, AHCI, and HSA are still in there too.

 

[fincoder]

In the past, we had an issue similar to this with computers that had an Intel processor, which we could fix by doing what you've described and using the "Load Driver" button to install Optane Memory drivers to get it to recognize the drive. Unfortunately, it doesn't work with this issue.

Probably a different driver needed this time. Various storage chipsets need the load driver technique, very occasionally it might even be needed for the NVMe driver.

 

[sapphirescales]

If you do what I did above, you'll see that's the content of the RAID sub folder. VMD, AHCI, and HSA are still in there too.

Interesting. I'm sure they're all in the archive somewhere but it is easier to use your method. I'm usually stuck using the .exe's from Dells or HPs website though, and as far as I know they don't always have this extraction command. Another method I use is I start the installer .exe on another computer and then find the files in the TEMP folder and copy them from there. I just tried that with this .exe we've been working with and it showed all the drivers.

 

[ComputerDave]

If you can boot into the factory Windows you can use Device Manager to get the info you need for the drive controller. On the machine I'm sitting next to now the storage controller is "Intel RST VND Controller 467F" and if I get the properties and go to Details then select Hardware IDs I see the Vendor is 8086 and device is 467F. Knowing those to bits makes it easy to find a driver that will work. The value is actually PCI\VEN_8086&DEV_467F&SUBSYS_0BE01028. But you only need the 4 digit vendor and device codes.

That's a good idea. I found what I needed using this method.

Thanks, everyone, for your suggestions and insight. I appreciate you all giving me a moment of your time.

 

[britechguy]

Like reformatting?

No, as initialization is the step before you can even do a format on the drive.

Perplexity.ai: How do you reinitialize a drive under Windows?

The method they give using diskpart is the one I generally use simply because I find it less tedious and that I included in a tutorial I wrote: Doing a Completely Clean (Re)install of Windows 10 or 11 Using the Media Creation Tool to Fetch the Windows ISO File