Media Content Code: Code: Name: en-us_windows_10_consumer_editions_version_21h2_updated_june_2022_x64_dvd_bd124508.iso Size: 6043674624 bytes (5763 MiB) CRC32: 49755459 CRC64: 73B698CC8940109C SHA256: 6a362816b16452375a68316af050e6397aa8a916f252965c0dd96b3266c088d5 SHA1: 8ace6cee53a60ca2cc9db5e029807ce73d44d147 BLAKE2sp: 7f8b5de621306534e5c281437cb45bfb9603db57932d3e6e01b84d9bb9dd0d64 SKUs: Code: [01] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Home | Core [02] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Home N | CoreN [03] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Home Single Language | CoreSingleLanguage [04] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Education | Education [05] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Education N | EducationN [06] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Pro | Professional [07] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Pro N | ProfessionalN [08] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Pro Education | ProfessionalEducation [09] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Pro Education N | ProfessionalEducationN [10] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Pro for Workstations | ProfessionalWorkstation [11] 09/06/2022 en-US x64 10.0.19041.1766 Windows 10 Pro N for Workstations | ProfessionalWorkstationN Code: Code: Name: en-us_windows_10_business_editions_version_21h2_updated_june_2022_x86_dvd_7bbb0400.iso Size: 4158246912 bytes (3965 MiB) CRC32: 437602BE CRC64: 21D3C46DA0C574CC SHA256: 7d6af9e96aaf6e7f8933a0f5fc72a38dad1e34dc0ff6e4aeeae6a220ee49d632 SHA1: cd1a824aecee31a568d66476f61d146e7aba16bd BLAKE2sp: 3db6fb27dbb4a9c2f2e7c5f14801f808b61e793be3b42be7a7d97d1117d4abe3 SKUs: Code: [01] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Education | Education [02] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Education N | EducationN [03] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Enterprise | Enterprise [04] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Enterprise N | EnterpriseN [05] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Pro | Professional [06] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Pro N | ProfessionalN [07] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Pro Education | ProfessionalEducation [08] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Pro Education N | ProfessionalEducationN [09] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Pro for Workstations | ProfessionalWorkstation [10] 09/06/2022 en-US x86 10.0.19041.1766 Windows 10 Pro N for Workstations | ProfessionalWorkstationN
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.