Official 19041 LTSC started from 19044.1288. 10.0.19041.1? It must be a homebrewed\reconstructed image. Official image is recommended.
Since 19041.1 was never released by Ms, it had to be reconstructed. This may be the reason why component store is broken after using the install.wim, but Resetbase always managed to clean this up when using 19041.1 as the base and installing an LCU, until now. For some reason the resetbase for the Dec LCU did not remove any superseded items. See packages.txt after resetbase. The 10 items in the component store that dism complains about during scanhealth also were not removed. I previously installed the Aug LCU to the 19041.1 base as I did with the Dec LCU and resetbase at that time removed the superseded items and there was also no component store corruption reported. The question is why resetbase did not do the same for Dec.? I managed to fix the component store by removing the following items Code: Microsoft-Windows-Branding-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package~31bf3856ad364e35~amd64~~10.0.19041.1 from Code: c:\Windows\servicing\Packages\ c:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\ HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\ Does anyone know why the reconstruction of 19041.1 corrupts the component store after applying the install.wim? When the install.wim is mounted, /ScanHealth shows no corruption. After using the image, I get the errors mentioned above
About this error: https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-56#post-1865721 Solution: https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-56#post-1865854
Sorry, but I have no idea what Code: "Of course, if you generate all the catalogs instead of using catalogs from other packages from Microsoft." means or even a clue how to accomplish that. Thanks, anyway.
These components is the problem. Code: 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-Branding-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt 2024-12-21 16:33:07, Info CBS Manifest of corrupted package: Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package~31bf3856ad364e35~amd64~~10.0.19041.1 not found, skip repair attempt Try this: https://forums.mydigitallife.net/th...-editions-reconstructions.88605/#post-1850661 Solution: https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-57#post-1866055
Tried that too. Same result after applying the reconstructed wim. Maybe the wim I'm using as input is the cause? Which wim did you use?
This issue is hard to settle down even by official CU. Anyway, the homebrewed "19041.1" is impossible to get rid of the error.
OK, I guess I'm wasting my time with this using a 19041.1 base for updating . I never noticed this problem all these years using this wim since running resetbase after updating hid/fixed the issue from/for me until I installed the Dec LCU recently. For anyone interested in testing/verifying this issue, simply Install the 19041.1 base (install.wim) without updates and run dism /online /Cleanup-Image /Scanhealth after applying the image . The result should be: the component store is repairable. If not, please post here. Thanks...
Although the non-official initial build (e.g. 19041.1\26100.1) is not perfect, if by CU update, the error will be gone, why not? You can try iamaHUN's 26100.1 LTSC packages, or 19041.1 EnterpriseSN packages. iamaHUN "reverts" components from CU to initial build, different to "repacking" which is lacking required certificates. But please remember that "the reverted initial 19041.1\26100.1 build should be updated by an adequate official CU" to be 0 error. Adequate? The CU has all updates of the relevant non-official components.
I'm fine with that. I just don't know why the error was not resolved with the Dec. LCU. That's what started me asking about all this. Maybe I did not do the update correctly. I will give it another try.
Okay, I reran a clean install with the 19041.1 install.wim and updated it with the Dec. LCU. I don't know what I did wrong the last time I used the wim, but this time resetbase fixed the original corruption as it did all these years. I apologise for taking up everyone's time about this discovered non-critical imperfection. Code: Microsoft Windows [Version 10.0.19041.5247] (c) Microsoft Corporation. All rights reserved. c:\>dism /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19041.5247 [==========================100.0%==========================] No component store corruption detected. The operation completed successfully.