Build 26200.7705, In insider Release Preview channel finds repairable components and needs /RESTOREHEALTH to fix.

The same update to Build 26200.7705 was applied to machines with public build and machines on the Release Preview insider channel. The results were quite different.

The public Build machines were updated from 26200.7628 to 26200.7705 while the ones on Release preview were updated from 26200.7701 to 26200.7705.

After the update the DISM scans on public build ran clean, while the same scans on the machines in the Release preview channel found repairable components and had to be fixed with command:

DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH

As usual when it needs to repair components, the command sits for a long time at 62.3% before finally complete successfully. The process is quite long and painful and a waste of my internet download usage.

The question is, why the different behavior on Insider R.P. versus public build with the same exact build number? Did the previous update to 26200.7701 on R.P. insider damage some components?

This below is the DISM scans result on several Release Preview channel machines.