Updated the 20H1/2 / 21H1 Updates Overview: https://forums.mydigitallife.net/th...-20h1-2-vb_release.80763/page-16#post-1571109
Microsoft has updated their Blog post: UPDATE: This update is available for ALL Insidders in the Beta Channel on both 20H2 and 21H1.
A couple of hours ago. https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-596#post-1646534
The 20H2 enablement pack is contained in 21H1 enablement though, or at least superseded. KB4562830 can be uninstalled after installing the 21H1 enablement without obvious negative side-effects.
Used updates: Code: defender-dism-x64.cab Windows10.0-KB4580325-x64_Flash.cab Windows10.0-KB4584642-x64_EDGE_Cr.cab windows10.0-kb4586858-x64_DU_SafeOS.cab windows10.0-kb4601382-x64_87d4ba1dac3ea12aee681b660c505607ae9b01f3.msu <--- left the separate SSU out to test the packaged one!!! Windows10.0-KB4601554-x64-NDP48_CU_4341.2.cab windows10.0-kb5000736-x64_21H1_EP.cab Windows10.0-KB5000751-x64_DU-Sources_844.cab windows10.0-kb5000967-x64_FxP_671.cab Code: ============================================================ [1] Target (x64): "D:\W10UI\19041_Work_x64_US" [2] Updates: "D:\W10UI\19041.1_Updates_x64" [3] DISM: "Windows 10 ADK" [4] Enable .NET 3.5: YES [5] Cleanup System Image: YES [6] Reset Image Base: YES [7] Update WinRE.wim: YES [8] Install.wim selected indexes: 1 / [K] Keep indexes: Selected [M] Mount Directory: "D:\W10UImount_12833" [E] Extraction Directory: "D:\W10UItemp_12854" ============================================================ Change a menu option, press 0 to start the process, or 9 to exit: Code: ============================================================ Running W10UI v9.4 ============================================================ ============================================================ Extracting .cab files from .msu files ============================================================ 1/1: windows10.0-kb4601382-x64_87d4ba1dac3ea12aee681b660c505607ae9b01f3.msu ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/9: defender-dism-x64.cab 2/9: Windows10.0-KB4580325-x64_Flash.cab [Flash] 3/9: Windows10.0-KB4584642-x64_EDGE_Cr.cab [EdgeChromium] 4/9: windows10.0-kb4586858-x64_DU_SafeOS.cab [WinPE] 5/9: Windows10.0-KB4601382-x64.cab [LCU] 6/9: Windows10.0-KB4601554-x64-NDP48_CU_4341.2.cab [NetFx] 7/9: windows10.0-kb5000736-x64_21H1_EP.cab [Enablement] 8/9: Windows10.0-KB5000751-x64_DU-Sources_844.cab [Setup DU] 9/9: windows10.0-kb5000967-x64_FxP_671.cab [UX FeaturePack] ============================================================ Mounting sources\install.wim - index 1/2 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.1 Image Version: 10.0.19041.1 An error occurred trying to open - windows10.0-kb5000736-x64_21H1_EP\update.mum Error: 0x800f0823 The specified package cannot be added to this Windows Image due to a version mismatch. Update the Windows image and try the operation again. Processing 1 of 3 - Adding package Package_for_KB4580325~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] Processing 2 of 3 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4341.2 [==========================100.0%==========================] Processing 3 of 3 - Adding package Package_for_WindowsExperienceFeaturePack~31bf3856ad364e35~amd64~~19041.671.1.0 [==========================100.0%==========================] Error: 0x800f0823 The specified package cannot be added to this Windows Image due to a version mismatch. Update the Windows image and try the operation again. The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\Windows\Logs\DISM\DismUpdt.log Deployment Image Servicing and Management tool Version: 10.0.19041.1 Image Version: 10.0.19041.1 An error occurred trying to open - Windows10.0-KB4601382-x64\update.mum Error: 0x800f0823 The specified package cannot be added to this Windows Image due to a version mismatch. Update the Windows image and try the operation again. Error: 0x800f0823 The specified package cannot be added to this Windows Image due to a version mismatch. Update the Windows image and try the operation again. The DISM log file can be found at C:\Windows\Logs\DISM\DismLCU.log ============================================================ Resetting OS image base ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.1 Image Version: 10.0.19041.1 [============= 23.3% ] @abbodi1406 you probably need to address this ssu + lcu packaged MSU versions.
the hash value cab files which are in the windows10.0-kb4601382-x64.msu is the same as the previous one from the SSU and LCU. Are there any problems if I continue to unpack the msu and unpack the 2 cab files from the LCU and import them individually ?
Yes, they are the same, it's only packaged in the one LCU MSU. Yeah, using W10UI that should work, providing the cab manually.
DISM seems not to be able to handle the ssu/lcu combined package either: Offline: Code: dism.exe /image:"c:\mount" /Add-Package /PackagePath:"d:\W10UI\Test" Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.19041.1 Processing 1 of 1 - d:\W10UI\Test\windows10.0-kb4601382-x64_87d4ba1dac3ea12aee681b660c505607ae9b01f3.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x800f0823 Error: 0x800f0823 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
They were first released as 21H1 beta channel updates, so yes 21H1 / 19043 doesn't exist on public msft release websites, but all can be applied to 21H1 too.