Can't Seem To Integrate Dell RAID drivers Into ISO

masterne0

New Member
I created a bootable Windows 11 ISO, burned it using RUFUS onto a USB drive but when I try booting up Windows setup. It would never seems to load the drivers needed to detected the drive installed on the desktop, specially the SSD drive.

I can manually load the same drivers and then the drive would show up.

Am I integrating them incorrectly when using NTLITE? I had integrated them in the DRIVERS section in NTLITE and also underneath the APPLY > REAPPLY TASK ACROSS EDITIONS > INTEGRATE > BOOT.WIM.

I also incorporated Chrome during the installer but when I boot it from the USB, it doesn't seem to install it. Works fine if I boot the same ISO in a virtualbox/VMWare setting I see Chrome actually being installed.
 
I think you're doing the right steps. Don't have a Dell, but check their website if you have one their models where you have to disable SATA before installing NVME drives, then re-enable SATA post-install. I dunno, but it's a Dell thing.

For a Dell/HP/Lenovo, you need to check the OEM SetupComplete box in the Unattended page. Otherwise Windows will skip over Post-Setup commands because you have an OEM product key. This is a Windows feature, they require OEMs to do strange contortions to install their apps.

Non-OEM machines (ie. VM's) don't get this treatment. Blame MS.
 
OEM SetupComplete fixed the preinstall of the google chrome.

Still haven't figure out how to integrate the raid drivers so I dont have to hit "f6"/Browse key to find the drivers manually for the drive to be detected during install.
 
I unzipped the EXE, and there's 3 driver folders:
- HsaComponent​
- HsaExtension​
- VMD​

You're adding all of them (or least the parent folder) in the Drivers tab?
 
From what I can tell, this an Intel RST problem when you have both VMD and non-VMD drivers and the "wrong" one gets loaded first.
So this isn't specific to NTLite, but here's some leads:


And the classic hack, just disable RAID mode if you really don't need it and use AHCI instead.
 
Thanks. I will take a look but I guess for now, I can just manually load it each time. Not a huge deal, just annoying.
 
Here's my reading of the Dell comments:

Newer RST's are released with an INF improperly ranking itself in comparison to the (older) Intel storage driver included in the Windows image. While both drivers are present, the "wrong" driver is picked at boot time. Therefore it looks like driver integration failed.

By running F6, you're re-inserting the new driver ahead of the non-working version.

The last article hints at grouping drivers by folder, so when they're added to the image -- it forces a specific load order.
Sorry it's still not an answer, because the general Dell community hasn't arrived at a consensus solution.
 
Back
Top