Driver issues with W10/11 image

This doesn't touch any drivers. All we're doing is taking a brief detour to the script, and then calling setup.exe to resume like nothing happened.
 
garlin said:
This doesn't touch any drivers. All we're doing is taking a brief detour to the script, and then calling setup.exe to resume like nothing happened.
Click to expand...
after loading a partition tool to have a look at what it did it appears its left me with an unintialized drive, which im guessing is why windows doesnt recognise it?
 
Partitioning is not the same task as creating a volume or filesystem. Setup's supposed to review the current layout, check if it's valid, and then create the necessary volumes on each partition. This is replicating the manual steps of:

1. Boot WinPE (Setup). Stop at the first Setup dialog.
2. Open a CMD window with shift-F10.
3. Run diskpart by hand, where many guides instruct you to type "clean; convert gpt; etc..."
4. Exit diskpart
5. Continue until reaching Setup's normal disk layout screen.
6. Accept the existing settings, and Setup starts creating volumes and copying files.

diskpart never creates a volume. Setup confirms the target disk has all the different partition types it expects to find, and proceeds.
 
yeah, what i mean is with this script in there it fails completely saying the pc doesnt meet requirements and when i look at the disk after running it it is setting the disk to uninitilaized with no partitions/volumes, without the script loaded it shows the disk select page which once selected correctly creates the partitions
which makes me think the script is doing something strange and not applying the diskpart info correctly?
 
Boot w/o an unattended file. By the time you see Setup, the script has already (or should have) executed. Run diskpart from CMD and see if it created it correctly or not. A simple test is manually leave the disk cleaned. Then if it worked, the next time you boot it should have a non-empty partition table.
 
garlin said:
Boot w/o an unattended file. By the time you see Setup, the script has already (or should have) executed. Run diskpart from CMD and see if it created it correctly or not. A simple test is manually leave the disk cleaned. Then if it worked, the next time you boot it should have a non-empty partition table.
Click to expand...
nothing created on the disk, even removing the script and changing the setup.exe back im just getting your machine does not meet requirements so now im just totally confused
 
PC doesn't meet requirements is unrelated. You don't have (HW) Bypass reg keys integrated into boot.wim.
 
im beginning to think something just breaks when you do the merging the Win 10 and 11 into one WIM, and using the Win 11 boot.wim to load them, as i havent been able to get it to work like that whatso ever, and ive been banging my head for weeks now and not really getting anywhere
 
I finally sat down, and ran both sets of merged ISO's through the install process.

1. Downloaded W10 22H2 clean ISO, and appended W11 22H2 to the install.wim
Only change made was to add Unattended mode (with Prompt edition selection).​
  • W10 correctly installed
  • W11 correctly installed
2. Downloaded W11 22H2 (May 2023) clean ISO, and appended W10 22H2 to the install.wim
Only changes made was enable BypassTPM for boot.wim, and Unattended mode (with Prompt edition).​
  • W10 install fails on first reboot, "Windows could not start the installation process."
  • W11 correctly installed

W10's install stopped, with Panther\setuperr.log:

View attachment 10280

Panther\setupact.log:

View attachment 10281

So what happens if we roll back to an older W11 ISO, but keep the previous install.wim?

I tried all W11 releases from 21H2 (RTM) to 22H (May 2023), and none of them allow W10 images to start installing after the first reboot. Switching to the W10 21H2 install image does not make any difference. Something fundamental is preventing W10 images to install, when provisioned by W11's WinPE.

Unless a better explanation is provided, I would stick to W10 ISO as the base for building a merged W10/11 install ISO.

Either something is missing from the W10 ISO, or W11 ISO introduced a new problem that didn't exist in W10. On paper, every WinPE is supposed to successfully install Window releases of the same or earlier versions.
 
garlin said:
I finally sat down, and ran both sets of merged ISO's through the install process.

1. Downloaded W10 22H2 clean ISO, and appended W11 22H2 to the install.wim
Only change made was to add Unattended mode (with Prompt edition selection).​
  • W10 correctly installed
  • W11 correctly installed
2. Downloaded W11 22H2 (May 2023) clean ISO, and appended W10 22H2 to the install.wim
Only changes made was enable BypassTPM for boot.wim, and Unattended mode (with Prompt edition).​
  • W10 install fails on first reboot, "Windows could not start the installation process."
  • W11 correctly installed

W10's install stopped, with Panther\setuperr.log:

View attachment 10280

Panther\setupact.log:

View attachment 10281

So what happens if we roll back to an older W11 ISO, but keep the previous install.wim?

I tried all W11 releases from 21H2 (RTM) to 22H (May 2023), and none of them allow W10 images to start installing after the first reboot. Switching to the W10 21H2 install image does not make any difference. Something fundamental is preventing W10 images to install, when provisioned by W11's WinPE.

Unless a better explanation is provided, I would stick to W10 ISO as the base for building a merged W10/11 install ISO.

Either something is missing from the W10 ISO, or W11 ISO introduced a new problem that didn't exist in W10. On paper, every WinPE is supposed to successfully install Window releases of the same or earlier versions.
Click to expand...
omg... it was that simple.... have just tested that and have the same outcome as you.. with the w10 boot etc both OS's work perfectly... didnt even think to try that as i thought the boot.wim only worked with same and older.... thank you so much for that... cant believe it was such a simple issue haha
 
I can make the Module_Init_HWRequirements error disappear, by using AveYo's hack from MediaCreationTool.bat:
Code: 
# Mount boot.wim image
$winsetup = "sources\winsetup.dll"

$b = [IO.File]::ReadAllBytes($winsetup)
$h = [BitConverter]::ToString($b) -replace '-'
$s = [BitConverter]::ToString([Text.Encoding]::Unicode.GetBytes('Module_Init_HWRequirements')) -replace '-'
$i = ($h.IndexOf($s)/2); $r = [Text.Encoding]::Unicode.GetBytes('Module_Init_GatherDiskInfo'); $l = $r.Length

if ($i -gt 1) {
    for ($k=0; $k -lt $l; $k++) {
        $b[$i+$k] = $r[$k]
    }
    [IO.File]::WriteAllBytes("sources\winsetup.dll",$b)
}

He avoids the function call by overwriting the module's name inside the DLL with another string, "Module_Init_GatherDiskInfo" (with the exact same length as the original module name).

But I still can't get past the MultiEdition key error...
 
You must log in or register to reply here.
Back
Top