-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Drivers getting skipped #3
Comments
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 :-) |
Hi @UXabre |
It looks like a windows driver issue , where i can download and put this iaStorB.sys package in WINMAN repo |
or I think winpe drivers in finalized/drivers folders are conflicting with windows server 2016 drivers in source/drivers folder |
seems like foreman installation is finished and now OS is failing to boot from the installed OS , where can be the issue , install.wim ? |
Regarding driver installation: Regarding your last comment; is the failure the sames as the BSOD you sent earlier? Or what is the exact error message here? Kind regards! |
Hi @UXabre |
Referring to below link to fix , not sure if it will work |
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 |
Hi |
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 |
@UXabre , below are my tftboot folder contents , where is wimboot ? , its showing zero KB , not in finalized folder . Dont we need install.wim ? |
@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 ? |
Hi, I think it might be worthwhile investigating the following files: 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, |
I am having issue while installing , below screenshot shows the error
The text was updated successfully, but these errors were encountered: