24H2 apparently has a bug where it may be only be successful when ran once and if ran again in the future, then it fails. 23H2 and 22H2 didn't have this bug!
Did CBS on 24H2 write gibberish to install.wim on my June installation?! This is why I have a brand new install this month, on July 8th...
To update on this problem: This issue seems to be far more common on 24H2 than with 23H2:
Where DISM with scanhealth fails with the message about it being repairable, and restorehealth fails too.
In 24H2, unfortunately, multiple times now, I saw the restore operation fail with an error message...
This update is really buggy! It feels like the nightmares of Windows 7! Where it got to the point where I didn't like Windows 7, unless I had updates integrated into the install media!
The error was brand new to the July, 2025 patch-Tuesday. That error isn't anything to panic about. It's the broken DISM state that had me forced to reinstall Windows, after I just installed 24H2 for the first time on my daily-driver, on June 10, 2025.
Both my PCs that are in regular use, had Windows 11 get wrecked like that!
It was fine before today's LCU!
But, the LCU is fine on a fresh install with newer install media.
It's worse than that. This update breaks Windows 11 installations that had any previous LCU updates:
DISM, 99 percent, will come back with the reply that required data can't be found. Also a load of corruption reports in CBS.log...
For both PCs, effectively forced to reinstall Windows!
The odds of Microsoft pulling the update, is extreme.
Looks like all installs with previous CUs, will get corrupted, and DISM unusable!
This apparently introduces the "CSI corrupted payload" bug.
That's very-early DDR4! That's the Skylake era! First-generation DDR4. What CPU do you have? It sounds like a system old enough to not be officially supported by Microsoft for Windows 11.
Important: What CPU does it have. It may be a DDR3 system, which is surely not supported by Microsoft for...
It claims no source data of any kind can be found. This issue didn't exist in 23H2.
I suspect it's the bug that came from RP! That the new broken-DISM bug from RP, is now widespread in the normal releases now.