Is this right? Analyzing component store in latest Beta build

I did an Analyze component store and cleanup sequence on build 4010 - had not done one for a long time, I got the idea seeing in the build announcement thread how people do this every time. Anyway, check out the image - Analyze said to do cleanup, cleanup completed fine, analyze said do cleanup again - I went through this cycle twice. Is this normal or is something wrong? Prior to this, I did all of the commands in this list - restore health found some issues that got fixed and verified as fixed through check health:

sfc /scannow
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
Dism /online /cleanup-image /analyzecomponentstore
Dism /online /cleanup-image /startcomponentcleanup

One add-on note: I rebooted, tried again - analyze looked the same. I watched the cleanup, it went very fast, almost to 20% immediately, and ended like this:

C:\WINDOWS\System32>Dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Image Version: 10.0.22635.4010

[=========== 20.0% ]
The operation completed successfully.

Awalt said:

....tried again - analyze looked the same. I watched the cleanup, it went very fast, almost to 20% immediately, and ended

Click to expand...

That is typical of the clean up having already been completed once before. It's normal behaviour for all builds including RTM 23H2.

Awalt said:

analyze said do cleanup again - I went through this cycle twice. Is this normal or is something wrong?

Click to expand...

Yes, there is something wrong, but it's Microsoft's fault and as far as I can tell is of no real consequence. Somewhere along the lines after multiple updates to thes Insider builds there are orphaned package manifests that appear to need cleaning. As far as I can make out the actual files don't exist in the component store any more, just the manifests that say they do. The result is that DISM reports a dozen or more packages to reclaim, but cannot reclaim them (as they don't really appear to be there).

It's nothing new, I have been seeing this issue for over a year now....

KB5027295 Windows 11 Insider Beta 22621.1972 and 22631.1972 - June 29 - post #42

...and now the Dev build shows the same issue.

Great, thank you @Bree for the insight and reply. I won't worry about it then, especially since I have not seen any issues with the install! I'll keep checking things when an update comes out, it's a nice list of things to check.