They can be found here: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-588#post-1645340
Just created 19043.844 esd and size is 3.8gb, so figure in two months recovery esd won't fit on fat32 key Spoiler 02/18/2021 05:08 PM 4,090,128,668 install.esd -------------------Fat32 limit 4,294,967,295
Size depends on what you did to it, did you run a cleanup command after/during integrating updates? This is my install.esd from a 19042.804 source WIM updated with only the 21H1 updates, no cleanup possible because of pending flag in the source 19042.804 WIM (which is created by W10UI_9.2 with resetbase set): Code: SKUs: Home, Pro, Education & Enterprise x64 nl-NL Name: install.esd Size: 3625371786 bytes (3457 MiB) Running WIM<>ESD on this WIM (Home x64 only, as base for all other SKUs to be based on): https://forums.mydigitallife.net/th...20h1-2-vb_release.80763/page-318#post-1645619
I added .net 3.5. I avoid cleanup ever since the bug in (iirc 1903), blocking install of new CU if you did cleanup.
That was with a small range IP build CUs which were missing some components. W10UI avoids the resetbase of the LCU for 1903/9/20H1/2/21H1, but it's a few 100MB less then without running it. The wim mentioned also has 3.5 pre-enabled, the settings are shown in the post. wim<>esd is at 43%
That would somewhat resemble what i did with the install.esd here: I think we are good to go for a while (even with your filesize) Code: SKUs: Home x64 en-US 19043.844 Name: install.esd Size: 3181801882 bytes (3034 MiB)
That's an UUP > ISO version? It lacks dotnetfx48 and the flash update or removal update, and did you set .net35 to be enabled.. @jackmonter5 used a Jan. Updated 2021 MVS ISO as base, I've used 19041.1 UUP ISO as source like you did. Apples and oranges
Just to be sure: can I install those 3 cabs files on my current stable channel without going to the insider program and getting 21H1? Is it worth it?
i installed the windows10.0-kb4601382-x64.cab windows10.0-kb5000736-x64.cab on my stable windows 10 19042 January 2020 and got 21H1
& I made my complete up-to-date 21H1 ISO (19043.844) by adding these -2021-01 IMC KB4589212 [10.0.2.4] -2021-01 WFEP KB4601906 120.2212.2020.0 [19041.666.1.0] -2021-02 21H2 EP KB5000736 [10.0.1.2] -2021-02 CU KB4601382 [19041.844.1.7] -2021-02 DotNET KB4601050 [10.0.4330.6] -2021-02 Flash Removal KB4577586 [10.0.1.2] -2021-02 SSU KB5000911 [19041.841.1.0] Plus other FOD packages
I made an image as well but since the new Edge is not included in the new EP I did things in 2 steps. I added everything using the 20H2 EP but left off the CU and 21H1 EP. I did a 2nd round and only added the latest CU and 21H1 EP. Am I correct that if you build an image using just the new EP and CU that you wont get the new Edge until it downloads after install?
1/9: Windows10.0-KB4577586-x64_Remove_Adobe.cab [Flash] 2/9: Windows10.0-KB4584642-x64_Microsoft_Edge_601.cab [EdgeChromium] 3/9: windows10.0-kb4586858-x64_WinPE.cab [WinPE] 4/9: windows10.0-kb4601050-x64-x64_NDP48_DotnetCU_35-48.cab [NetFx] 5/9: windows10.0-kb4601382-x64_LCU_844.1.7.cab [LCU] 6/9: Windows10.0-KB4601906-x64_Feature_X_Pack.cab [UX FeaturePack] 7/9: windows10.0-kb5000736-x64_21H1_Enablement_Package.cab [Enablement] 8/9: Windows10.0-KB5000751-x64_DU_Source.cab [Setup DU] 9/9: Windows10.0-KB5000911-x64_SSU_841.1.0.cab [SSU]
The new EP & 844 CU doesn't have the Chromium-base new edge rather have the old legacy EDGE As I don't use any of those MS EDGE & not intend to keep either, so I build my 21H1 ISO based on 20H1.1 base ISO build (19041.1.) a'with latest 21H1 EP+v844 CU, & while making, I also remove the legacy EDGE from the base 19041.1 ISO as well to make my Win10 ISO as bloat-free as possible.
How do you mean? You won't be enrolled or part of anything IP. The new edge is not part of the 20kb EP anymore, it will be offered / maintained by the CUs when 21H1 goes public. Most who were on 19042.xxx and enrolled in the beta channel already have the new edge running, so there was no need for re-putting it in the new EP.