Package_1191_for_KB5017327~31bf3856ad364e35~amd64~~10.0.1.5 (CastingTransmitter) Package_1199_for_KB5017327~31bf3856ad364e35~amd64~~10.0.1.5 (PackageManager) These two, installed and image got damaged.
Perhaps the 10240 troubles aren't limited to the above. Try this. Don't install the LCU, install a recent CU say from April or May 2022. Do a resetbase Install the LCU. 99/100 your component store will be screwed and turned to a non serviceable mess, forcing you to do an in place upgrade to recover your windows and start again. Don't do a resetbase and your WinSxS folder will stay at around 13GB instead of 7/8 as it should be.
It is the most beautiful. Thank you. Resolved finally. Code: C:\windows\system32>dism /english /image:K: /add-package:Z:\Windows10.0-KB5014024-x64 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.19291 Processing 1 of 1 - Adding package Package_for_KB5014024~31bf3856ad364e35~amd64~~10240.19291.1.1 [==========================100.0%==========================] The operation completed successfully. C:\windows\system32>dism /english /image:K: /add-package:Z:\Windows10.0-KB5017327-x64 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.19291 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.19444.1.5 [==========================100.0%==========================] The operation completed successfully. C:\windows\system32>
I didn't share any instruction, I posted my finding about the image got (silently) corrupted, and about what WU by itself does. So what are you talking about?
https://forums.mydigitallife.net/th...struction-project.80939/page-474#post-1755347 Code: Try this. Don't install the LCU, install a recent CU say from April or May 2022. Do a resetbase Install the LCU. Then I install 10240.18187 Windows10.0-KB4498375-x64.cab. And the latest CU can be integrated by Dism.exe.
Interesting April 2019, not May2019 (which is what WU offers on fresh installs).... Speaking about WU this is the list of that WU installed on a fresh install on a ISO updated offline with May 14, 2019—KB4499154 (OS Build 10240.18215), few of them maybe HW specific, like Intel uCode update and alike Code: [01]: KB3116097 (uCode update) [02]: KB3118714 (OOBE update, 8 Dec 2015) [03]: KB3119598 (OOBE update, 8 Dec 2015) [04]: KB3122962 (OOBE update 15 Dec 2015) [05]: KB3125217 (Disk Cleanup Update) [06]: KB3161102 (Windows Journal remover) [07]: KB3172729 (Secure boot update) [08]: KB3173427 (SSU for Windows 10: July 12, 2016) <---Interesting, SSU May 2022 was already installed) [09]: KB4021701 (update for windows update) [10]: KB4033631 (.NET Framework 4.7 update) [11]: KB4535680 (secure boot DBX update) [12]: KB4577586 (Adobe Flash remover) [13]: KB4589198 (uCode update) [14]: KB5012170 (secure boot DBX update) [15]: KB5014024 (SSU for Windows 10: May 10, 2022) [16]: KB5017327 (LCU Sept 2022)
Unfortunately, the older CU 10240.18187 still have to be installed by Dism++. Code: C:\windows\system32>dism /english /image:K: /add-package:Z:\10240.18187\Windows10.0-KB4498375-x64.cab Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.18187.1.0 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800f0922 Error: 0x800f0922 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 C:\windows\system32>
So CU from May 2019 installs w/o problems with dism (I did it yesterday) and the one from April does not ?
Try with a decent file manager (like XY Explorer free) Resetbase is ongoing, WinSxS already reduced from 13GB to less than 12...
10240.18218 Code: C:\windows\system32>dism /english /image:K: /add-package:Z:\10240.18218 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Processing 1 of 2 - Adding package Package_for_KB4498353~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.18218.1.0 [==========================100.0%==========================] Error: 0x800f0922 Package Package_for_RollupFix may have failed due to pending updates to servicing components in the image. Try the command 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\dism.log C:\windows\system32> 10240.18215 KB4499154, not available.
Possibly you'll find a direct link it in the hotfix thread (files are still in the MS server, they remove just the links )
In LCUs that can be successfully installed, ssshim.dll should also be 10.0.10240.17709. I will compare the differences between their manifests. By editing the mum, the possible impact of other components has been eliminated. In total, only 3 manifests were copied, but when they failed, DISM uninstalled a large number of drivers.
For WinPE/RE, problematic Package is package_3105_for_kb5017327~31bf3856ad364e35~amd64~~10.0.1.5.mum.
Would be interesting to know, what happens if you service offline a 10240 using another 10240 install, where the online system is installed in a partition called X:
To no avail as I did install 10240.16384 to X:. But X: is shown on my 19044 OS, it is C: upon completion of Setup. Then, C & C, still failed. This situation is same as Unstaged. Failed when Dism, Package Manage, SSShim, TrustedInstaller mismatched.