Thanks for sharing the details. The first batch of devices upgraded to 25H2 without a hitch, but the second batch failed across the board. Since nothing changed in your client config or update package, your hunch about a Patch Tuesday update introducing a conflict is correct .
I think you should check the update history on one of the failed devices and comparing it against the successful ones from Nov/Dec. Look specifically for cumulative updates or servicing stack updates released in late Dec or Jan. If you spot differences, try uninstalling those updates temporarily and re-running the upgrade.
Another good step is to run the Windows Update Troubleshooter and collect logs with SetupDiag. That tool can highlight exactly which component or driver is blocking the upgrade. If it points to a specific KB, we can then confirm whether it’s a known blocker.
If you want to be extra thorough, you could also test the upgrade on a clean VM with the same patch level as your Feb devices. That helps isolate whether the issue is environmental or truly tied to a recent patch.
Give these steps a shot and let me know what you find. If this helps move things forward, please hit “Accept Answer” so we know we’re heading in the right direction and let me know if you need any assistance. Thank you!