I wonder when 1909 specific updates will come, if at all. The way they are setting this up is really strange.
Hi, someone can tell me how i can get this Business and Costumer ISO's ([18362.295] Windows 10 Version 1903 Updated Aug 2019) on my own language? Or maybe, what is the procedure to follow to obtain the XX ISO's from EN ISO's? Thank you very much for your help.
For now it seems they are planning to use the 1909 enablement package, but that can be for testing purposes for a sp like CU.
Go here, and click the link by @GezoeSloog: https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324/page-176#post-1544043 Download the en-US consumer source iso and the consumer svf patch + the business svf patch of your desired language and put them all in the same folder. Download this tool package and extract " Batch_Extract_370_x86.rar" and put the files 2 from the rar next to the source iso + 2 patches and run "_batch_extract.bat". All possible info about svf patches: https://forums.mydigitallife.net/threads/smartversion-tools-scripts.79415/
Other question, this version ([18362.295] Windows 10 Version 1903 Updated Aug 2019) is this the most recent and stable version? Or is there any other much more recent?
Finally, Windows Sandbox is working on my PC after integrating the latest CU, SSU and CU for .NET Framework 3.5 and 4.8 and after doing a clean install. However, it's very slow, I can't install some programs and I can't move some folders from the host to it. I can't disable Windows Defender in it (as well as do other things), too.
Business/Customer ISOs have multiple SKUs, there is some script that allows me to extract only the one I need? Thanks for the replies.
I used WU on the (slow, weak) test rig 2 & now have this build also (18362.329). It did take awhile to install though, I have so much spare space to that partition I haven't run disk cleanup yet. Still testing it for broken stuff too.
I tried installing a built 18363.329 image on top of 18362.327 and was blocked because windows installer thinks that 18362.327 is newer. Did anyone else get this bug? I ended up just starting fresh with 18363.329.
I'll stop using uup until whatever is causing the bugs with the update gets fixed. Can anyone point me to the media creation tool for august update? The one I downloaded from microsoft gives me the july .239. I've seen some images you guys shared with a 1903_updated_aug_2019 .ISO which is .295 build. Any help?
Just set addupdates to 0 and use W10UI manually for updates integration, set cleanup to 0 in the script too. As @abbodi1406 mentioned in the uup dump thread, he will add that option to the convertconfig.ini too.
And he just released the new UUP>ISO converter: https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/page-119#post-1544917 Will probably be used by UUP dump soon too.