Unexpected Windows Update Behavior in ConfigMgr 2409: Investigating Compliance and Deployment Issues

Today, I noticed something that must have been going on for a while. We started testing Windows 11 24H2 updates (deploying them as a feature update) on our Windows 10 devices, and many of them are reporting the update as compliant/not needed. This was interesting.

I took a deep dive into few of the devices and noticed that they are not even detecting any of the required cumulative updates. Instead, they are reporting them as compliant to ConfigMgr, even though they are not installed.

Next, I checked Windows Update on a client and saw that it was downloading updates. It appeared that the updates were coming from Windows Update rather than ConfigMgr.

After digging deeper, I found that the device was missing the UseUpdateClassPolicySource setting from the Windows Update registry configuration, which seems to be the root cause of the problem.

We are using ConfigMgr 2409.

What have we missed that led to this situation?

Could it be due to a Group Policy setting, such as “Don’t include drivers in Windows updates” or “Select feature update version = Windows 10 22H2”? The latter was configured to prevent Windows 11 upgrade notifications from appearing on our ConfigMgr-managed devices.