Interesting update in the release preview channel. @boe323 I know u game so may be of assistance for this. Seems they added 1000hz support and updated some gaming stuff under the hood because I now get my video card is unsupported on first boot of forza horizon 3. Can u check some games and see how urs are and if u happen to have horizon 3 give that a try?
Updating boot.wim with 26100.1742 ISO from massgrave causes errors Code: ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.8037.1.19 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x80073712 Error: 14098 The component store has been corrupted. The DISM log file can be found at C:\WINDOWS\Logs\DISM\DismLCU_boot.log
Please show fuill progress, so we can see what updates were used and what W10UI version, i always use 26100.1742 as source and never experienced any problem: https://forums.mydigitallife.net/posts/1907739 W10UI Boot.wim: Code: ============================================================ Mounting sources\boot.wim - index 2/2 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_ServicingStack_8035~31bf3856ad364e35~amd64~~26100.8035.1.1 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_8035 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_KB5054156~31bf3856ad364e35~amd64~~26100.6717.1.4 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.8037.1.19 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting WinPE image base... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26100.8037 [===========================95.1%======================= ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26100.8037 [===========================70.0%======== ] The operation completed successfully. ============================================================ Unmounting sources\boot.wim - index 2/2 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image File : E:\W10UI_26100\26100_Work_US_1742\sources\boot.wim Image Index : 2 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. MVS ISO boot.wim: https://forums.mydigitallife.net/posts/1906204 Code: Package Identity : Package_for_KB5054156~31bf3856ad364e35~amd64~~26100.6717.1.4 State : Installed Release Type : Update Install Time : 06/02/2026 23:59 Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.7840.1.19 State : Installed Release Type : Security Update Install Time : 07/02/2026 00:03 Package Identity : Package_for_ServicingStack_7839~31bf3856ad364e35~amd64~~26100.7839.1.4 State : Installed Release Type : Security Update Install Time : 07/02/2026 00:01
Probably because I didn't included 26100.1742 (KB5043080), I just ended up by using 26100.1 ISO. I thought I wouldn't required KB5043080 from MVS ISO because it already has base updates.
Trying to make some sense here; You used 26100.1742 at first and got the error at updating boot.wim? And next you used 26100.1 (which is en-US only) At what attempt didn't you use kb5043080? It is the update that makes 26100.1 updated to 26100.1742. It is required when updating a 26100.1 ISO and advised to include it when updating the 26100.1742 ISOs too. TiP: always show full progress, most info will be included in it.
Well, it was ru-RU at that time, so I couldn't find 26100.1 ISO for ru-RU. I had to build from UUP Dump to get 26100.1 boot.wim with ru-RU (I wish in next release of W10UI 10.50, It would best if there is have an option to log W10UI full progress.)
Yes, this happens on my Windows 26H1 (28000.1719) too. I thought it was an error on ISO creating but it's not
Mitigation: The affected Samsung Galaxy Connect application was temporarily removed from the Microsoft Store to prevent further installations. Samsung has republished a stable previous version of the application to stop recurrence on additional devices. Recovery options for devices already impacted remain limited, and Samsung continues to evaluate remediation approaches with Microsoft’s support. Not all users will be affected. This issue is related to the Samsung Galaxy Connect application.