6.0 and 6.1 create the same iso (the only difference is the location of the source iso which doesn't affect the content of the generated iso).
This should work for you : Code: for /F "delims=" %%i in ('powershell -NoP -C ^ "[void](Add-Type -AssemblyName System.Windows.Forms);" ^ "$FileBrowser = New-Object System.Windows.Forms.OpenFileDialog;" ^ "<#$FileBrowser.InitialDirectory=\"%~dp0Source_ISO\"#>;" ^ "$FileBrowser.Title = 'Select the Windows iso image';" ^ "$FileBrowser.Filter = 'ISO images (*.iso)|*.iso';" ^ "$FileBrowser.Multiselect = $False;" ^ "If($FileBrowser.ShowDialog() -ne 'Cancel'){$FileBrowser.filename}" ^ ') do set "ISO_Path=%%i"
I tried to adapt my script into this format this weekend, but I failed. Your response is timely. Thank you.
That's because of the inserted generic ei.cfg file in the sources folder of the ISO. With option 2 that should not happen (checking now EDIT checked and option 2a and b don't show server in the title bar), option 1 uses UFWS and the server.cfg file, server doesn't enforce the windows 11 system requirements. For clean install and using option 2 only 2a is needed, for upgrades you need to run 2b on the system you want to upgrade to 24/25H2. Thanks
The only thing I noticed is that I can't select the other options, only the (0) button. I don't know if that matters.
Sorry. I understand now, I wasn't familiar with the tool. Just select example 2 and the asterisk moves by itself, then press “0”. So in my case, to prevent the Windows Server message from appearing, I have to select 2 and 3 (AIO 2a\2b)? Thank you.
After reading the notes and to be on the safe side, is it perhaps better to leave only option [1] AIO 1, even though the words “Windows Server” appear? Thank you.
Use only option 1 OR option 2a. NOT 2b, unless you want to prepare the CURRENT OS for upgrading. Option 2a will copy the necessary preparation script to the ISO, too, for execution prior to setup.exe, in order to prepare that system. Whew, long sentence.
Enthousiast: Just for your information: I deployed Win_11_Boot_And_Upgrade_Fix_Kit_v6.1f2.cmd (option #1 with default extras) after placing a newly downloaded 7.20 GB size "Win11_25H2_English_x64.iso" ISO inside the Source_ISO folder. The conversion process went very quick and a slightly smaller 7.18 GB size ISO was created in less than 2 minutes. A bootable install disc was created and a clean install of Windows 11 Pro Version 25H2 Build 26200.6899 was done in my 7th generation Dell Precision Tower 3620. The install and setup process went fine without any problems.
No. Some Registry Voodoo, mainly. Option 1 works as-is, but uses (and displays) Server as disguise, as Server does not check for the requirements. Wrong display is only until the first reboot. Option 2a uses a different method, you fist run the special script copied to the ISO, and then setup.exe. Option 2b is a quick fix if you want to upgrade your current OS to 11 and the PC does not meet the requirements.
Excuse my ignorance. I'm looking for a tool that allows me to upgrade my Windows 10 Pro to Windows 11 while keeping my installed programs.
If your PC meets the requirements, Windows Update can do this for you. Otherwise, create a windows 11 iso; a in-place upgrade keeps your programs.and parameters. Be sure to apply the latest windows 10 updates before upgrading.