after upgraded to 19044.1766 network diagnose broken then I fresh install 19044.1766 from uup broken still .
If @EaglePC would read the damn release notes, would find out it's "broken by design". A huge flaw in diagnostics leading to EoP (elevation of privilege) was already exploited in the wild. And it affects pretty much all windows versions, Microsoft had to quickly patch it out, hence the suboptimal "error".
DISM will not show the 4 because it's by registry only, mount the install.wim and run any commandline and you will get to see the 4.
Finally... 19045 has come. Code: dism /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Product-Data-22h2-EKB-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1806.mum dism /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Product-Data-22h2-EKB-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum dism /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Product-Data-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1806.mum dism /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Product-Data-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum dism /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1806.mum dism /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum dism /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1806.mum dism /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum Spoiler
Here we go again, people should not follow these procedures, didn't it cause problems when in the past the official release of the "new" build actually got released?
Will applying the EP for 19045 cause updates to cease in the General Availability channel? In the past, applying an EP BEFORE the final release date of the new Windows 10 version, would stop updates in the General Availability (GA) channel. For example, if you were on 19043 and pre-maturely applied the EP for 19044, the Windows Update server would stop offering updates, if 19044 had not officially been released yet.
Just don't. It's proven to break exactly that on more than two occasions! You know the saying about doing something (wrong) again, expecting a different outcome..
I don't even have the 19045 EP yet, but I expect that it will be released in the RP channel before the final release in the GA channel. In the past, you could manually apply the EP early, but the GA channel updates would cease. As soon as the there was a final release, the GA channel updates would resume again with no other problems.
I've seen an install borked by the fake EP with my own eyes. It did not recover by itself once officially released, even after the 2nd month LCU. Had to be scrapped. But knock yourself out, it makes for great winver screenshots, minus everything else.