Solved CBS Check Utility.

@hader Yes, perfect.

======================== Start CBS Check EndResult ===================================
File CBS.log found.
Loading C:\Windows\Logs\CBS\CBS.log file into memory.
Done.
Found 13232 Lines to process.
We found 0 Hits....
======================================================================================
Sorry; No EndResult hits found.
Do you want to run "DISM /Online /Cleanup-Image /ScanHealth" to retry? [Y] or [N]: n
======================== End CBS Check EndResult =====================================

Press Enter to continue...:

Thank you for this Hader a clean bill of Health.

So ran this and what does it tell me. Said found 1 hit .. but hit what and what do you with that info. I ran restorehealth yesterday just for fun and found no issues

======================= Start CBS Check EndResult ===================================
File CBS.log found.
Loading C:\Windows\Logs\CBS\CBS.log file into memory.
Done.
Found 104646 Lines to process.
======================================================================================
Found EndResult string at line: 65855.
======================================================================================
2026-10-05 13:15:10, Info CBS Last Successful Step: Stage package detection completes.
2026-10-05 13:15:10, Info CBS Total Detected Corruption: 0
2026-10-05 13:15:10, Info CBS CBS Manifest Corruption: 0
2026-10-05 13:15:10, Info CBS CBS Metadata Corruption: 0
2026-10-05 13:15:10, Info CBS CSI Manifest Corruption: 0
2026-10-05 13:15:10, Info CBS CSI Metadata Corruption: 0
2026-10-05 13:15:10, Info CBS CSI Payload Corruption: 0
2026-10-05 13:15:10, Info CBS CSI FileFlags Corrupt: 0
2026-10-05 13:15:10, Info CBS Total Repaired Corruption: 0
2026-10-05 13:15:10, Info CBS CBS Manifest Repaired: 0
2026-10-05 13:15:10, Info CBS CSI Manifest Repaired: 0
2026-10-05 13:15:10, Info CBS CSI Payload Repaired: 0
2026-10-05 13:15:10, Info CBS CSI FileFlags Repaired: 0
2026-10-05 13:15:10, Info CBS CSI Registry Metadata refreshed: False
2026-10-05 13:15:10, Info CBS CSI Store Metadata refreshed: True
2026-10-05 13:15:10, Info CBS Staged Packages:
2026-10-05 13:15:10, Info CBS CBS Staged packages: 0
2026-10-05 13:15:10, Info CBS CBS Staged packages removed: 0
We found 1 Hits....
======================================================================================
Found 1 EndResult. If the last EndResult above shows Corruption;
Run "DISM /Online /Cleanup-Image /RestoreHealth" to correct the issue(s).
======================== End CBS Check EndResult =====================================

Do nothing, it found a record that you had run DISM, that's all.

Hader have you had a chance to have a look at this months update to see if Microsoft have fixed the bug?
I installed the update, rebooted, DISM /Online /Cleanup-Image /RestoreHealth, DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase to blow away the pesky leftovers as Disk Cleanup would not remove them, DISM /Online /Cleanup-Image /ScanHealth and your Utility reported a clean bill of health.

EB2XR6 said:

Hader have you had a chance to have a look at this months update to see if Microsoft have fixed the bug?
I installed the update, rebooted, DISM /Online /Cleanup-Image /RestoreHealth, DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase to blow away the pesky leftovers as Disk Cleanup would not remove them, DISM /Online /Cleanup-Image /ScanHealth and your Utility reported a clean bill of health.

Click to expand...

No! the issue is not resolved. It is still there with 26300.9550. I already notified MS about this issue several time but they seem to ignore it.
You can test it for yourself by run the DISM /Online /Cleanup-Image /RestoreHealth command and search inside the C:\Windows\Logs\CBS\CBS.log file when it's done (or watch it live with PS as Admin command: Get-Content C:\Windows\Logs\CBS\CBS.log -tail 10 -wait ) and search for the start of the download stage: "FLOW: Entering stage: Download" After that the progress is seen at each "FCAcquirerWUClient" line. It shows a counter percentage 0-100 how much % it has downloaded 274Mb at attempt 1 (successful) and attempt 2 (fails, because the MS upload server said: "You got it already!")

It always starts with CBS suspicion that maybe (not in many cases) there is something wrong:
After this suspicion it enters always the download stage.

Search for this "sub phase: 4, sub percentage: 100" You can will find 4 hits per /RestoreHealth run and will show you how many bytes it downloaded at both attempts. The first attempt: 269364971 Bytes (varies from build to build) and a second attempt: 0 Bytes.

In some cases there are FileFlag corruptions after an update. The corruption is fixed with /RestoreHealth. But from that point onwards; it always repeats and keep on downloading every time while nothing is wrong anymore.... That's why this command always takes 3,5x times longer to run as it should be.

I cannot oversee the consequences if you do not resolve those errors. The fact remains, however, that every update includes a manifest defining files and directory's permissions. /ScanHealth checks whether that manifest matches the one on the disk. Often, there is a mismatch for unknown reasons, which could potentially pose a security risk. Crucial files could be altered when properly protected.

This utility shows that without any doubt that /ScanHealth finds corruptions while it reports that everything is in OK.

Thank you Hader, I will have to watch next month.