Win10+ Setup Disk (Works with UEFI Secure Boot / BIOS / Install.wim over 4 GB)

@freddie-o well, x86 and x64 separate isos are both fine, they have the usual structure where you got a sources folder with boot.wim and install.wim. The isos I'm referring to are the ones that have an x64 and x86 folders in the root, which respectively contain... well... basically an x64 and x86 iso in them. In that regard I can see how the script wouldn't work based on just iso folder structure. After that I'm absolutely clueless.

 

Having trouble using this script.
Generated a usb-stick using this script.
Selected a win11FIXED iso.
This iso is produced by the MDL fix-kit for bypassing legacy pc win11-blocking limitations.
(win11 boot and upgrade fix-kit ver. 3.0).
This iso works fine for upgrading legacy pcs from win 10 to win 11.
(that is, an update of drivers are needed beforehand) .
Now I wanted to generate a bootable usb-stick with this iso on it.
To be used for clean installs on blank disk.
The script runs fine, finished ok.
Booting the usb-stick, starts ok,
selecting clean install of win11pro, works for a while, win11-windows-logo displays, but after a restert,
abort with error mess "dpc watchdog violation".
Any hint for solving this matter ?
regards
snofte

 

That has nothing to do with this script.

 

Sorry for being late. You could try Ventoy (www.ventoy.net). It creates a USB stick with 2 partitions. A 32 MB Fat partition contains what is needed for booting; You just copy your ISO images into the second exFat partition. After booting a menu allows you to chose the ISO you want to install.

 

I'm already using ventoy on my own USBs. I also have one win10 setup disk personal usb that I use as a fail safe for when ventoy decides to be iffy. Also, all the win10/11 USBs at work are also made using win10 setup disk. I was just wondering if I could make a USB with an x86+x64 iso.

 

ventoy are uefi and secure boot / and legacy capable

 

It is possible to create a WinPE combining X86 and X64 and copy it to a 1 GB fat32 active partition. Format the remaining space of the usb disk as exFAT and copy the contents of the X86 and x64 to their respective folders (for example x86 and X64). During the Winpe creation, modify the startnet. cmd file in order it can detect the folders x86 and x84 and execute setup.exe.

 

Two (minor) modifications to the script :
When executing robocopy where the source is a mounted iso image, the files attributs are set to read only for the target files and this was the cause of difficulties when execiting bcdedit. The work arround is to add the /a-:R parameter to teh robocopy statements. Hence the script is cleaner.
To initialize the usb disk, the first action is to invoque the disk management cmdlets; if they fail, diskpart is executed.
The new version can be found here : https://drive.google.com/file/d/1cmyMICqe9C-yldgMC8-OqaJRWllsD8uM/view?usp=share_link

 

Hey, thanks for this, is it up to date ? to use it with win 11 ltsc just rleased

 

Is there a reason to use the script instead of simply extracting the contents of the ISO to an NTFS formatted USB drive and booting?

 

Do I need FAT32 to install on a disk with capacity of more than 2TB?

 

What I am asking is why do I need FAT32 for UEFI/GPT disk?

 

I don't, but I would still like to know under what scenario could I use the script.