Why would you want to install it so desperately? It will be on WU when needed, it's just a WU settings reset/preparation update. ps, that file set is just an example, probably not even for 20H2, i just posted an example.
My Plans I am running 1909 Plan to Update to 2004 (19041) 1909 Out of Support soon. 20H2 (19042) Update to 21H1 (19043) Dev_Channel Waiting to Test "Sun Valley"
It is not typical to configure the use of Express updates in WSUS, although Microsoft recommended this configuration a while ago. From my experience it is more reliable not to use the Express files, but full update files, which are the same with the regular .cab files. Is this the first time when we have a documented SSU failure? I don't remember any other upfront buggy SSU. There were few instances when there were v2 for SSUs, but those were released long after the original release and were only improved versions, not meant to fix obvious faults.
Express updates is the only option for regular WU 1903 built-in servicing stack (and two released SSUs) were causing WinPE updating to fail 1507 & 1607 (x86) has known issue were you cannot offline integrate CU they don't want to fix it
It is being reported that KB4023057 has been released BUT not showing up on WU. Is there a Download for it yet ?
that's the same as on uup but no real cab, just the msi inside, @abbodi1406 did post this when i first published it here.
4 years and counting of KB4023057 explanation https://forums.mydigitallife.net/search/1/?q=KB4023057&o=date&c[node]=54&c[user][0]=204274
No rumors: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-585#post-1644515
So why is it referred to as 19042.843 update? The cab from the Windows Update source appears to be for 1803. Is it something we should apply with DISM to 19042, or just wait for more to come from MSFT about it?