In my case the v6.1f2 doesn't accept the Win11_25H2_EnglishInternational_x64.iso (no matter in which folder it is), giving ========================================================= No iso file detected ... ========================================================= Press 9 or q to exit.
Because it doesn't work (see my post above of this morning). Anyway I have resolved by simply apply the update kb5054156 to my unsupported hardware with 24H2.
@rpo The file selection always points to the same folder. In one of my scripts, I use: Code: for /F "tokens=*" %%i in ('powershell -NoP -C ^ "Add-Type -AssemblyName System.Windows.Forms;" ^ "function Get-FileName($InitialDirectory)" ^ "{$OpenFileDialog = New-Object System.Windows.Forms.OpenFileDialog;" ^ "$OpenFileDialog.InitialDirectory = $InitialDirectory;" ^ "$OpenFileDialog.filter = 'ISO images (*.iso)|*.iso';" ^ "$OpenFileDialog.ShowDialog() | Out-Null;" ^ "$OpenFileDialog.FileName};" ^ "Get-FileName($InitialDirectory) | Write-Host;" ^ "$OpenFileDialog.FileName;" ^ ') do set "ISO_Path=%%i" The advantage is that the system remembers the last folder used. This is just a suggestion.
Just comment line 59 : Code: rem set "s=%s%$FB.InitialDirectory=\"%~dp0Source_ISO\";" or delete it : this way the system remembers the last folder used. instead of pointing to the Source_ISO folder.
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.