Line 59 : Code: set "s=%s%$FB.InitialDirectory=\"C:\My Folder\";" Double quotes (") must be escaped by \ : \" Script location : Code: "C:\CD-ROM\Windows 11\Win_11_Boot_And_Upgrade_FiX_KiT_v6.0\Win_11_Boot_And_Upgrade_FiX_KiT_v6.1.cmd"
He is posting allover the board, i ran the test and it worked fine with a spacing in the folder name.
There is zero difference between 6.0 and 6.1 other then ISO selection, what exact problems did you have?
It opens the default folder, you can select that ISO or browse to another folder and select an ISO there, working fine here.
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.