I can reproduce it when i put only x86 updates next to a x64 install.wim, or the other way around. Or when the assigned folder contains no updates (when i assign a folder for it in the script).
@coleoptere2007 Code: :: updates location :: leave it blank to automatically detect the current script directory set "" should be: Code: :: updates location :: leave it blank to automatically detect the current script directory set "Repo="
Haven't had much time look into things but this is what I experienced. So on 2004 VM installed KB4562830 and the 2 preview updates (KB4580364 and KB4580419). The installed KB4584642. However, when I rebooted after that last update, Edge was at v85.0.564.67? However, when I ran Edge, and went to the About page, it started updating itself. When it was done, it was at version 86.0.622.58 (but no updates were showing in WU before this). But then I checked WinSxS and now there are 2 folders with Edge installer deposited in there, so now we have THREE Edge installers inside WinSxS. So even if you uninstall Edge in the OS, these will still be present in WinSxS. I had really hoped updating Edge would have deleted/replaced the previous 2 installers, but no. So now there is almost 300mb sitting in WinSxS regardless -- they actually managed to make it worse. Sigh MS... Is there any downloadable ISO option for 20H2 that doesn't have the double Edge installers from KB4562830 present? It being the Enablement update and all...
Well I think problem is due to the fact I use the script without WHD, will test later with debug mode. Thx for giving me a new way.
What has WHD to do with this? It's most likely just an error caused by yourself (considering the other error showed). Incorrectly editing of the updates filenames could cause it too.
Try downloading the newest version of W10UI WITHOUT changing anything in it. Or just change the INI leaving the REPO setting the same.