Error: The component storage is corrupted. Please copy the original image and start again.

A

Alex Corretor Do Brasil

Member
Messages
162
Reaction score
14
The following error message appears: "The component store is corrupted. Please copy the original image and start again."
1764887428829.png

The image I used to work with is indeed modified, but outside of NTLite.

I then took a 100% original image from the Microsoft website, without any alterations, and tried to generate a new project, but the error persists.

Despite the error, it continues generating the edited image.

It seems to be related to the bug reported in this post, as updates to the recovery images are ignored when the error appears.
1764887499888.png
index.php


I am using NTLite version 2025.11.10675 and the Windows 11 25H2 ISO.
 

Attachments

Update your image before using NTL - is it working?
If yes - you've no concern regarding NTL.
 
You don't need to integrate the KB5043080 and KB5070311 into boot.wim
 
Alex Corretor Do Brasil said:
This has already been discussed in this post.
For average users, no, for certain situations, yes.
Click to expand...
Yes maybe, if you have a problem installing Windows.
Is that the case ?

The only case I've seen is with Intel RAID/VMD drivers that were to be integrated, but they are "separate" drivers.
Never seen any other errors during the first installation phase (boot.wim) before the first reboot (other than the W11 prerequisites and with the new setup).
 
tistou77 said:
Yes maybe, if you have a problem installing Windows.
Is that the case ?

The only case I've seen is with Intel RAID/VMD drivers that were to be integrated, but they are "separate" drivers.
Never seen any other errors during the first installation phase (boot.wim) before the first reboot (other than the W11 prerequisites and with the new setup).
Click to expand...
Integration problems in boot.wim are not limited to RAID/VMD drivers. Cumulative updates and WinRE packages can also generate inconsistencies in the WinPE environment, especially because boot.wim does not use the same set of components as the installed system. In other words, the fact that you "have never seen it" does not mean it doesn't happen—it only means that you haven't encountered this type of error, not that it doesn't exist.
 
In this case, it's Windows Setup (index 2) and not WinPE (index 9) that's used.
This differs from the other post, which is about WinPE (or with WinRE if used)
 
Hi - you could do your self a big favor downloading an updated image from UUP Dump instead of installing updates outside NTL, where it's possible to configure ie. net.FX3 integration in the ConvertConfig file for Windows based installations if you need this.

I only keep boot.wim 2 and never experienced any probs regarding WinSxS folder.

But heads up testing an outdated image give error given the amount of updates integrated outside NTL.
Some aren't needed even use NTL.
Wait 1½ hour the new B update for december come from MS.
 
francis11 said:
Hi - you could do your self a big favor downloading an updated image from UUP Dump instead of installing updates outside NTL, where it's possible to configure ie. net.FX3 integration in the ConvertConfig file for Windows based installations if you need this.

I only keep boot.wim 2 and never experienced any probs regarding WinSxS folder.

But heads up testing an outdated image give error given the amount of updates integrated outside NTL.
Some aren't needed even use NTL.
Wait 1½ hour the new B update for december come from MS.
Click to expand...
I didn't understand what you mean by using CUs outside of NTLite, because I'm using the original image from the Microsoft website without any modifications or integrations of updates outside of NTLite; I only use NTLite.

And this time I used the latest cumulative update for Windows and also for NTLite v2025.12.10723 and the same error occurred.
 

Attachments

You must log in or register to reply here.
Back
Top