Storage Drives not detected within Setup Wizard

N

NitrousX

New Member
Messages
21
Reaction score
1
Hi guys I’m in the process of rebuilding my laptop Asus G15.

Before deploying the ISO Windows 11 25H2. I was testing it in a VM which I was able to boot into ok. But the last 2 ISOs that were slightly different as I added some appx and script for winget apps into a batch file.



I found that running them within the VM it worked ok but I then noticed that some winget packages was missing. So, I went back into NTlite and made some further changes. After I made some changes, I noticed that the within the Setup wizard it stated it could not find the storage or raid controller drivers. I thought maybe there was an issue with my VM so I swapped from Virtualbox to Hyper-V same issue. I then thought let me try deploying the image straight to the laptop. I have followed suggestions online. They suggested the following:

  • Making sure that BIOS is set to ACHI
  • Disabling CSM
  • Add RAID controller driver and NVME driver onto USB


Please note the laptop is an AMD laptop a lot of the information online make suggestions to download the Intel Rapid Storage drivers. This only applies if your device has a Intel CPU/Chipset. But if you have AMD device you will require the AMD RAID files.



I tried all the above and the Internet says to add the drivers onto a separate USB but the setup file does not detect the USBs. Instructions state that there should be a “load driver” button but I cannot see this at all.



I did try setting up NTlite on another workstation with a fresh ISO on another device. Thinking maybe it was an issue with my PC. After creating the ISO with the same settings, I had the same issue. Mind you I did not use the same preset, I created the settings from fresh on my other device.



So, what I did as a test was to see if I could just use the default iso from Windows. And sure, enough the drive is recognized. So, I believe there is an issue with my config. Things that I have done differently compared to in the past, is using the drivers & registry files. And integrating them into Windows PE, Setup and Windows RE partitions.



I have attached the XML and screenshots of the settings because whatever I have done is obviously screwing up the setup on first boot. See link here https://mega.nz/file/L5gzgRwQ#D0-CpHi2dABGebAQnq2WhIEMyIRYQ9Ek64rEL2tDjoU

I come across this before nearly a decade ago back on Windows 10 where a feature build did not have the support for newer NVME drives. Similar to what is happening now but for whatever reason I cannot find the load driver button. Despite having USB's connected to the laptop they are not detected at all. Also wanted to note that on the image I created I made sure that I imported all the drivers for into the Windows PE, Setup and install WIM file.



Been stuck trying to figure this out for the past week. Let me know if you need additional information from me thanks
 
Are you using the new (default) 25h2 installation setup ?
And did you delete any files/directories from the root of the ISO ?

Some are required with the new setup for storage drive (but not with the old one) among other things, and there were also problems with unattended and this new setup (perhaps fixed since).
If so, you can try testing the legacy setup (Settings - System => Boot/Setup - Legacy) in NTLite for boot.wim.

Alternatively, by clicking on "Browse" button, can't you import a driver (for testing) ?
 
Windows includes a set of default storage drivers, and sometimes it works from a clean ISO. But most of the time you have to find the right driver. I see your preset includes some drivers. Since you're a licensed NTLite user, use the import drivers feature on the Drivers screen. This will copy the current host's driver files, so you know those drivers will work.

To speed up image processing, you don't have apply all changes to boot.wim.

boot.wim is only briefly used to launch Setup, and disappears as soon as Windows reboots into the newly extracted image. All you need for reapply changes to boot.wim is the added drivers. NTLite will check the Settings box if you're using any HW bypasses for the install. Other than that, you don't really need to update boot.wim since it has a single purpose.
 
tistou77 said:
Are you using the new (default) 25h2 installation setup ?
And did you delete any files/directories from the root of the ISO ?

Some are required with the new setup for storage drive (but not with the old one) among other things, and there were also problems with unattended and this new setup (perhaps fixed since).
If so, you can try testing the legacy setup (Settings - System => Boot/Setup - Legacy) in NTLite for boot.wim.

Alternatively, by clicking on "Browse" button, can't you import a driver (for testing) ?
Click to expand...
Hi there thank you for getting back to me. No I haven't deleted any files within the directory of the ISO. If i have removed any files then it has been through ntlite like removing non-relevant editions of windows or removing components like Maps or co-pilot etc. Any drivers that are pre-installed within the iso i have left as is.

i'll see if i can find the legacy setting
 
garlin said:
Windows includes a set of default storage drivers, and sometimes it works from a clean ISO. But most of the time you have to find the right driver. I see your preset includes some drivers. Since you're a licensed NTLite user, use the import drivers feature on the Drivers screen. This will copy the current host's driver files, so you know those drivers will work.

To speed up image processing, you don't have apply all changes to boot.wim.

boot.wim is only briefly used to launch Setup, and disappears as soon as Windows reboots into the newly extracted image. All you need for reapply changes to boot.wim is the added drivers. NTLite will check the Settings box if you're using any HW bypasses for the install. Other than that, you don't really need to update boot.wim since it has a single purpose.
Click to expand...
Oh so are you just suggesting not to reapply the changes to boot.wim. Should I just add these to the install.wim, setup and winre or uncheck those too?
 
boot.wim is a subset of Windows (that's why it's so small), so it's not intended that you apply monthly updates and tweaks to it. All that it benefits from is adding drivers that the Windows ISO is missing.

For boot.wim (index 2), only check the Drivers box. Everything else can be applied to WinRE.
 
garlin said:
boot.wim is a subset of Windows (that's why it's so small), so it's not intended that you apply monthly updates and tweaks to it. All that it benefits from is adding drivers that the Windows ISO is missing.

For boot.wim (index 2), only check the Drivers box. Everything else can be applied to WinRE.
Click to expand...
I have followed your advice and things have progressed now. I can see that the Windows Setup now allows me to add/remove partitions. But after applying the partitions the VMs/Laptop reboots and then it goes into a boot loop. I have left the devices for about 30mins or so but they keep restarting but never gets to the point to begin the task sequence.

I did take your advice and unchecked all the integrations and just left the boot.wim index checked for drivers. Despite selecting this option i cannot get into windows at all. And i have tried not including the drivers in the integration section too.
 
tistou77 said:
Are you using the new (default) 25h2 installation setup ?
And did you delete any files/directories from the root of the ISO ?

Some are required with the new setup for storage drive (but not with the old one) among other things, and there were also problems with unattended and this new setup (perhaps fixed since).
If so, you can try testing the legacy setup (Settings - System => Boot/Setup - Legacy) in NTLite for boot.wim.

Alternatively, by clicking on "Browse" button, can't you import a driver (for testing) ?
Click to expand...
Im trying to find the legacy setting you mentioned. Im struggling to find can you send me a screenshot of where i should be looking please thanks
 
NitrousX said:
Im trying to find the legacy setting you mentioned. Im struggling to find can you send me a screenshot of where i should be looking please thanks
Click to expand...
Type "boot" in the search bar and you should find it easily

Capture.PNG
 
1767372796310.pngthank you for pointing me in the right direction. I found the setting i set the top two options to enabled. then i was able to delete the partitions like normal but after the sequence where it copies the installation files and reboots i get this msg. I also tried disabling secure boot within bios same msg above
 
You must log in or register to reply here.
Back
Top