@SunLion Has anyone reported after pre downloading the updates, then running the main script, should I re run the main script the pre downloaded updates are erased.Have to re download the updates again? I haven't experienced this issue before?
It remains the same, without modifications. When the _PreDownloadAllUpdates.cmd script is executed, all .cab and .msu updates are removed for pre-cleanup. Then, all the latest updates are downloaded. The main script will only download updates that are not already in the folder.
@SunLion Thank you I re downloaded a fresh 26H1 archive, ran the _PreDownloadAllUpdates.cmd it downloads updates & places them all in the UUP dir. Once this is completed if I happen to re run _PreDownloadAllUpdates.cmd again it wants to re download all again? This has never occurred before? I have not modified the folder structure.
In versions 2xH2 and 26H1, a pre-cleanup was added to the _PreDownloadAllUpdates.cmd script to ensure that no previous updates exist. In my case, I use a single structure to edit all versions. So, when I update the all.txt file, I want only the most recent updates to remain in the UUP folder. Perhaps this is not necessary for the package published for you. I will remove it. Edit the _PreDownloadAllUpdates.cmd file and remove the following lines: lines 20 and 21 if exist *.cab del /f /q *.cab >nul if exist *.msu del /f /q *.msu >nul
I have found in 26H1 when running in a VM the store & some other apps that should have been removed are there on first startup, has WU reinstalled these perhaps?
In my tests, they are removed. See attached image. Check if the star2.bin file exists in the path below: $OEM$\$Docs\Default\AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\LocalState\start2.bin NOTE: If you chose not to install Openshell, this will not be removed either, as you will then have the complete official Windows Start Menu.
Yes, it supports all versions, but you should choose the specific version you need for your processing. You can use this tool with any (single) install.wim file from the 24H2–26H1 (26H2) release, in the edition and locale of your choice.
Hmm, come on—working with the script is extremely simple. The script has been thoroughly tested on all versions from 24H2 to 26H2, and no issues were found. Please read the instructions carefully again.
Instructions are on half the desktop while I follow the steps in the other half. Your guide info dosent says nothing about last step to create the iso. l.e: i tried with different iso, all end up with name 24h2 even if iso is 26h1
Tested in VirtualBox, without autounattend.xml, and the installation ran without errors. I'm going to add the WinSetup.dll file to the sources folder along with the script.