WMF 5.1 breaks class registrations for the ConfigMgr client agent
I've localized this issue to WMF 5.1 on Windows 7. With this installed, the WMI namespace: root\ccm\policy\defaultmacine\requestedconfig becomes invalid. This is important because in In-Place upgrade scenarios from Windows 7 to Windows 10, the task sequence agent cannot resume the task sequence without being able to read this namespace. I know this is a combination of WMF and ConfigurationManager so I will post there as well.
This issue was recently reported via another channel, and is being actively investigated.
Don’t have an ETA at this time, but will update this thread as we learn more.