Clients still showing the 21H2 Enablement Package (5003791) as Required after being updated with 3012973

Question

All ConfigMgr clients that have installed the Feature update to Windows 10 (business editions), version 21H2, en-us x64 (3012973) still show the Feature Update to Windows 10 Version 21H2 x64-based systems 2021-11 via Enablement Package (5003791) as Required. It seems like a bug in the detection method (metadata) for the Enablement Package which is making our compliance reports look bad. I even tried installing the Enablement package on an already updated system using DISM and it is still showing required.

Answer 1

@Steve Carneol
Thanks for your posting on Q&A.

Please help to confirm how many ConfigMgr clients shown as required the Feature Update to Windows 10 Version 21H2 x64-based systems 2021-11 via Enablement Package (5003791) after installing the Feature update to Windows 10 (business editions), version 21H2, en-us x64 (3012973). Please try to review the StateMessage.log on the clients and make sure the clients already sent the state messaging to the MP.

According to this link, Windows 10, versions 2004, 20H2, 21H1, and 21H2 share a common core operating system with an identical set of system files. So we could upgrade to Windows 10 21H2 after installing the Enablement Package (5003791).

By the way, what is the version of your MECM? I will research further on my lab environment and confirm whether it is a bug. I will come back as soon as possible if there are any updates.

Thanks for your understanding and cooperation.

Best regards,
Rita

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.