Hi Richard Brunner,
Thank you for sharing the detailed "nuclear" cleanup procedure that finally cleared the blockage on those 6 remaining PCs. It is excellent news that you were able to resolve it and get the entire fleet upgraded to 25H2.
To clarify why your final approach worked when the logs specifically pointed to adammigrate.dll (ADAM/AD LDS), I think even though the RSAT tools were not explicitly "installed" in the visible UI, the presence of the adammigrate.dll error in the logs confirms that orphaned components or stale registry pointers from a past configuration (or a base image) were triggering the migration engine to look for files that didn't exist. By performing step 2b (Remove ALL Optional Features except .NET), you effectively purged the hidden or corrupted remnants that dism and sfc were previously unable to unlink on their own. This "scorched earth" removal of optional components is a powerful technique for these exact "ghost" migration errors.
If you have a moment, please consider accepting the answer. While my specific pointer to RSAT was the catalyst, your rigorous execution of the optional feature removal was the cure, and marking this thread as resolved helps document this "clean sweep" strategy for other administrators fighting persistent 0x8007042B migration errors. Thank you, have a nice day!
VPHAN