Windows Drivers getting skipped

[karanveersingh5623]

I am having issue while installing , below screenshot shows the error

[karanveersingh5623]

Also I can see driver skipping when running powershell script . Attached Powershell output & driver's folder screenshot

[UXabre]

Hi @karanveersingh5623,

The drivers should be in an folder per type. In this case, you'll have to make a "megasas" subfolder under de drivers directory. After this, it should work.

As for your winPE related issue; only drivers added to the finalized/amd64/2016/drivers/.../ folders are included for winPE; that facility is only really used for hot-patching your installation (not winPE). If you run the script each time you want to add drivers to your windows installation, then you can skip that step entirely; but since creating windows images takes some time I've added the functionality in WinPE. Again, note that WinPE does need its drivers up front to work!

I hope this helps you out. I'll see to add some documentation to clearify your issue :-)

[karanveersingh5623]

Hi @UXabre
Thanks for your prompt reply , I understood the first part and created folder megasas , it got picked up by powershell script . PFA . The problem lies in the other shot I attached , "downloading user data & apply drivers , no .INF files found . What I am missing . Please let me know if you need more info

[karanveersingh5623]

I managed to surpass the error by putting all the drivers whether WINPE 10 or DELL oem in attached screenshots , When I boot into the system to check whether installation has properly completed , it goes to repair . Looks like finish template or script template issue but you can tell better . I am putting the screenshots in a sequence .

[karanveersingh5623]

It looks like a windows driver issue , where i can download and put this iaStorB.sys package in WINMAN repo

[karanveersingh5623]

or I think winpe drivers in finalized/drivers folders are conflicting with windows server 2016 drivers in source/drivers folder

[karanveersingh5623]

seems like foreman installation is finished and now OS is failing to boot from the installed OS , where can be the issue , install.wim ?

[UXabre]

Hi @karanveersingh5623,

Regarding driver installation:
You only really need one approach OR the other; meaning, either you include the drivers during the build phase (by putting the drivers in the source directory) OR you include them in the finalized folder. Both isn't really needed and might give issues as you encounter (although I don't think it should cause an issue ...)

Regarding your last comment; is the failure the sames as the BSOD you sent earlier? Or what is the exact error message here?
At least, the BSOD seems to indicate the wrong version of the driver is loaded; perhaps you can include the latest intel storage drivers and see if that solves the issue? You can also include a KB update in the updates folder (I'd recommend only doing this during built phase, not from winPE)

Kind regards!

[karanveersingh5623]

Hi @UXabre
Thanks for the reply.
The error msg in the screenshot attached , please refer . If you can help in finding the correct driver and update as I tried oems full driver pack and still getting the error , I am using Dell R740xd .

[karanveersingh5623]

Referring to below link to fix , not sure if it will work

https://downloadcenter.intel.com/download/29339/Intel-Rapid-Storage-Technology-Intel-RST-User-Interface-and-Driver

[UXabre]

Hi,

What were your exact steps to resolve this? How did you include the drivers? From what i can tell I'm guessing the 32-bit x86 drivers are probably loaded, try to only include the x64 drivers for instance. You can normally only extract the driver package.

Kr

[karanveersingh5623]

Hi
Very strange thing is when I not using any driver during the build process using the powershell scripts or in the finalized folders during the installation , this error screen always comes up . Totally exhausted .

[karanveersingh5623]

I am sure , same screen will come up with windows server 2019 , so i guess its more towards how powershell script is making the required wim files

[karanveersingh5623]

@UXabre , below are my tftboot folder contents , where is wimboot ? , its showing zero KB , not in finalized folder . Dont we need install.wim ?

Below my Finalized folder content

[karanveersingh5623]

@UXabre , Solved but the issue is with your poweshell script creating Server.wim , its not creating the .wim file properly , so I manually unzipped .iso and put the original install.wim in http share . check the shots . Which ps files I have to check and report the issue ?

[UXabre]

Hi,

I think it might be worthwhile investigating the following files:
./inc/AddDriversToWIM.ps1
./inc/OptimizeWIM.ps1 <== this one does a component cleanup; so might be our culprit? I would try and disable this functionality and check if the problem resolves
./inc/PrepareInstallWIM.ps1

Also, I've mounted all WIMs in an optimized mode; I don't think that affects the described behaviour though.

Thank you for your investigations and efforts! Unfortunately I can't reproduce that issue :-(

Kind regards,
Arend