Driver issues with W10/11 image

W

webtastix

New Member
Messages
16
Reaction score
0
Hi there,

i have been attempting to make a Win 11 / 10 install image for use in our oem business for a few weeks and am struggling
I used the Win 11 image downloaded using Microsoft media creation tool as the base and have intergraded the WIM's for Win 10 into that image, using the instructions here: https://www.ntlite.com/community/in...-editions-of-windows-within-the-program.2430/

It works fine without the unattended config, but once i add that (using the autofill all) i get confusing errors (no partition config or key etc)

Win 10 Home:
Your PC/Device needs to be repaired
View attachment 10226

Win 10 Pro: The computer restarted unexpectedly or encounted an unexpected error
the only errors in the log files i see are:
View attachment 10224

Win 11 Home:
Windows could not update the computers boot configuration

Win 11 Pro:
Works perfectly

i have been pulling my hair out over this one, so any help would be hugely appreciated
 
This error is caused by not having the right storage drivers installed in the image. They need to be added twice, in both boot & install.wim.
If you're adding drivers to multiple images in a single pass, don't forget to:

Expand Reapply tasks across editions
- Integrate drivers (check all editions & boot.win WinPE Setup)

Every Windows release will have newer drivers than the older releases. When you boot from a W11 ISO base image, W11 boot.wim has better NVME driver support compared to W10's install.wim. A good practice is to find the correct drivers, and add them yourself instead of counting on the built-in drivers to be compatible.
 
garlin said:
This error is caused by not having the right storage drivers installed in the image. They need to be added twice, in both boot & install.wim.
If you're adding drivers to multiple images in a single pass, don't forget to:

Expand Reapply tasks across editions
- Integrate drivers (check all editions & boot.win WinPE Setup)

Every Windows release will have newer drivers than the older releases. When you boot from a W11 ISO base image, W11 boot.wim has better NVME driver support compared to W10's install.wim. A good practice is to find the correct drivers, and add them yourself instead of counting on the built-in drivers to be compatible.
Click to expand...
These images work perfectly on thier own though, its only once they have been through NTLite / intergrating into one WIM file that they break... does NTLite remove drivers it thinks arent required or something like that? Also Win 11 Home breaks whereas Win 11 Pro works both from the same original iso file?
 
When NTLite processes each image, it will extract them to a separate temp folder. No drivers are removed, unless you explicitly ask NTLite to remove a driver component. It's most likely if you added a driver to W11 Pro -- it wasn't integrated at the same time to the other images.
 
garlin said:
When NTLite processes each image, it will extract them to a separate temp folder. No drivers are removed, unless you explicitly ask NTLite to remove a driver component. It's most likely if you added a driver to W11 Pro -- it wasn't integrated at the same time to the other images.
Click to expand...
I havent made any changes to the images whatsoever from the original iso's from Microsoft
Extracted the Home/Pro WIM's from W11 and W10 and then used imagex to merge them into one WIM then applied unattend using NTlite and complied to an iso
Original images work perfectly merged/automated image (only unattend, no extra scripts drivers etc) doesnt
 
I don't see any obvious problems with the preset. Was there another preset before this one?
 
garlin said:
I don't see any obvious problems with the preset. Was there another preset before this one?
Click to expand...
ive tried around 10 different setups so far, thats the one im sitting at that im having the issues mentioned above, just with a standard image with win10 intergrated into the win11 wim
 
W11 is UEFI only, whereas W10 supports both UEFI & MBR. What happens when you add a default UEFI disk layout (which wipes the disk)? Not sure why it would apply here, but that's the only explanation that matches.
 
garlin said:
W11 is UEFI only, whereas W10 supports both UEFI & MBR. What happens when you add a default UEFI disk layout (which wipes the disk)? Not sure why it would apply here, but that's the only explanation that matches.
Click to expand...
i tried that at one point but was getting errors that when i googled suggested issues with GPT/MBR, so i took it back off, is there a way to force it to convert the disk to GPT no matter what?
 
Not from a normal installer. This requires modding boot.wim (WinPE Setup) to install a short script.

1. Extract the ZIP file.
2. Load the boot.wim (WinPE Setup) image.
3. Open the mounted folder and copy startnet.cmd to \Windows\System32
4. Unload the image (saving changes).
5. Copy format-MBR.txt & format-UEFI.txt to the ISO's root folder
6. Make new ISO.

None of this is supported by NTLite, but it's been well tested. The script initializes WinPE, then checks if Windows recently booted in UEFI or MBR mode. Depending on the answer, it wipes the disk clean and applies the matching disk layout for this boot type.

The script always assumes it's wiping disk 0 (from diskpart). So you better check(!) or temporarily unplug the other disks if you think diskpart will pick another drive. You don't edit the script, but switch the BIOS mode to force the other disk layout.

Setup will run looking for the autounattend.xml in the usual place.
 

Attachments

garlin said:
Not from a normal installer. This requires modding boot.wim (WinPE Setup) to install a short script.

1. Extract the ZIP file.
2. Load the boot.wim (WinPE Setup) image.
3. Open the mounted folder and copy startnet.cmd to \Windows\System32
4. Unload the image (saving changes).
5. Copy format-MBR.txt & format-UEFI.txt to the ISO's root folder
6. Make new ISO.

None of this is supported by NTLite, but it's been well tested. The script initializes WinPE, then checks if Windows recently booted in UEFI or MBR mode. Depending on the answer, it wipes the disk clean and applies the matching disk layout for this boot type.

The script always assumes it's wiping disk 0 (from diskpart). So you better check(!) or temporarily unplug the other disks if you think diskpart will pick another drive. You don't edit the script, but switch the BIOS mode to force the other disk layout.

Setup will run looking for the autounattend.xml in the usual place.
Click to expand...
thanks for that, will give it a go
 
My bad, I forgot to remove a few lines of code added for a multi-architecture (x86/x64) ISO. Please re-download the ZIP file.
 
do you need to do anything special to make it run? i have added the script to system32 and the files to the root, but it doesnt do anything with the drive section.. do i need to define a partition insite ntlite?
 
Nope the idea is WinPE self-identifies the boot type and writes the disk layout. NTLite knows nothing about it, and everything will work as it did before. We've moved responsibility for disk management to the script. The defaults are directly copied from MS's reference docs, and behave as if you asked Setup to partition a never-used disk.
 
hmmm maybe i did something wrong then, as with that script in it still stops at the disk step with blank or last config on there
 
Sorry, I forgot another step. Rename \sources\setup.exe on the ISO to \sources\HIDE_setup.exe

We need to make WinPE think Setup doesn't exist, so it recovers and runs startcmd.net instead. I wrote this as part of a multi-image ISO, but never released the instructions. That's probably the last (?) thing I left out.
 
Does this make it load any drivers differently? once ive renamed that file it stops at the hard drive screen asking for disk drivers, im just testing this in a Hyper-V VM and looking in NT Lite it says disk drivers for Hyper-V are found so seems strange?
before i did that script above it loaded the disk and let me partition etc it just failed later in the setup
 
You must log in or register to reply here.
Back
Top