Ondrej Sebela Hello Ondrej, thanks for fixing the USB script, it works. I have another issue. I followed the article, but when I try to boot from USB, the task Test-WebConnection google.com fails. Also the task Testing Wi-Fi Network Adapter fails. A window opens and I can see the WiFi adapter in the network settings. I guess this is no driver issue. I injected the latest Windows 10 and WinPE drivers from DELL. "Transcript started, output file is X:\windows\TEMP\wreconnect.log No Wi-Fi profile was found, making initial connection. (I deleted the WiFi profile for testing. Even with the profile, the sequence fails.) Start-WinREWiFi OK Test-WebConnection google.com FAIL Testing required WinRE content OK Starting WlanSvc Service OK Testing Wi-Fi Network Adapter FAIL Warning: Could not find an installed Wi-Fi Network Adapter Warning: Drivers may need to be added to WinPE" Any ideas what could cause this? I have the same WiFi adapter as described in your article. Thanks and regards, Mark

Hello Ondrej, thanks for this useful article. I´m stuck with the USB script in line 388. Set-Content -Path $WinREWiFi -Value (Get-Content $WinREWiFi... The script quits with the error message, that -Path is NULL. I checked the USB script and in line 384 there is a script named WinREWiFi.ps1: $WinREWiFi = Get-Item "$wimMountPath\Program Files\WindowsPowerShell\Modules\OSD*\Public\WinREWiFi.ps1 I mounted the modified boot.wim, which is on the USB stick and there is no such script in the specified path. Do I have to change something in the USB script? Is there any change in OSDCloud so that there is no WinREWiFi.ps1 script anymore? Thanks in advance and best regards, Mark