Thanks, so I shall only integrate SSU and CU. I do hope that 610 ESD files are released, then I will work with these as my base image.
Hey Guys, I was playing around with Win10 Ent x64 20H2 in VM in order to sysprep/capture. I installed KB4562830 on my existing VM state of 2004/20H1, the enablement update, but of course this installs Edge. I successfully uninstalled Edge via Command Prompt (from Program Files (x86) location) but it remains in WinSxS (amd64_microsoft-windows-e..-firsttimeinstaller...) where two (n version and regular) Edge installers are located. Is there any way to actually remove/uninstall this from WinSxS? It is making my captured install.wim/esd 0.4gb larger than usual.
New Edge just released KB4584642. This one seems to be the "RTM" as it is released to WSUS. Edit: There is a slight variation for 1803 only which is named KB4584641.
They heard my rant https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-549#post-1626565
Although documented only for Windows 2004 and not for the 20H2, this Edge update/installer installs just fine using the msu downloaded from the Catalog on top of Windows 20H2 with Edge installed previously. I don't think it makes any changes from what I see, but it may be useful to set some flags.
It will be just as easy not to use Edge as it was not to use IE Well, in fact it may not be as easy... What I'm more annoyed by with this recent Edge development is that 2 installers for it are deposited in WinSxS taking up 200mb of space. When installed (which it will be by default) this adds another 600mb to the image, which means when compressed as install.wim it adds 0.5 gb to the install.wim size (maybe .2 or .3 to .esd). From now on... Yeah that sucks to forever have the images sizes increased in this way. You can uninstall Edge via scripts and such, and that does decreases final image size but still the WInSxS installers remain. What a mess. It could be removed via NTLite but then one risks breaking future update compatibility so it is no safe solution. So this is the new reality MS has chosen. Perhaps it will get more streamlined in the future but I doubt it. Sysprep aficionados must be pissed about this too. What I think they should do if going the WU route is make it optional, but not (regardless) deposit Edge installers in WinSxS unless one has chosen to include Edge. This whole "here is 200mb added to your .wim because you're not using Edge" doesn't sit right with me.
One set is .MSU and one set is the .CAB which is inside the MSU too. In my test it updated Edge to 85.xxxxx https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-551#post-1627277 Edge auto updates itself to 86.xxxx
Regular Edge updates like KB4584642 are normal packages which extract one MicrosoftEdgeStandaloneInstaller.exe in WinSxS only 20H2 EP (KB4562830) has the double behavior, because the incompetent who created it chose PackageFormat="PSFX" to save 2 or 3 MB same incompetent who created last ISO/ESD didn't know that you should delete Installer\msedge.7z and empty EdgeUpdate\Download maybe in the future they will convert Edge Chromium to MSIX package