Windows 10 Feature Update 20H2 - Device with (W10 - 2004) Shown as Compliant in ConfigMgr

zolkin 1 Reputation point
2020-12-09T13:30:33.81+00:00

Hi All,

Maybe someone have seen the following situation already:

I have a Windows 10 device on Feature version 2004 (19041.630). I made a deployment from ConfigMgr to make the latest release 20H2 available for this device. I was waiting long to see if it comes to SW center, but NO. Then I checked the deployment if there is any error..., but there I noticed that this device is shown as "compliant" already, so thats why it is not popping up in SW center.

Has anyone experienced similar behaviour? How is ConfigMgr checking the version of Windows?

Thanks.

Cheers
Zoltan

Microsoft Security Intune Configuration Manager Updates
Windows for business Windows Client for IT Pros User experience Other
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Youssef Saad 3,416 Reputation points
    2020-12-09T13:53:41.007+00:00

    Hi @zolkin ,

    What is your ConfigMgr CB version? Windows 10 20H2 is supported only starting from 2006 Current Branch version.

    In the All Windows 10 Updates node, you will see "Feature Update to Windows 10, version 20H2" update with the number of required devices.

    If you don't see the software update in the Software Center, you have to select "Show in the Software Center" when you deploy it in the User Experience parameters.

    Regards,


    Youssef Saad | New blog: https://youssef-saad.blogspot.com
    Please remember to ** “Accept answer” ** for useful answers, thank you!

    0 comments No comments

  2. zolkin 1 Reputation point
    2020-12-09T14:52:01.237+00:00

    Hi @Youssef Saad ,

    Thank you for the reply.
    Yes, I forgot to mention that the ConfigMgr was updated already about a month ago to the latest CB 2006.
    I see this client device in the Deployment Monitoring as Compliant, eventough when I check the "winver" localy I get that it has the version 2004.
    I had the same behaviour in November too, but I was hoping that with the newer release of H2 in December it will be working.
    Other devices can see it in SW center, only my test device has this kind of behaviour.

    Cheers,

    0 comments No comments

  3. Youssef Saad 3,416 Reputation points
    2020-12-09T18:49:04.653+00:00

    Make sure that the ConfigMgr client is also upgraded to the latest version on your test device.

    Check also the following log files:

    • CBS.log
    • DISM.log

    Regards,


    Youssef Saad | New blog: https://youssef-saad.blogspot.com
    Please remember to ** “Accept answer” ** for useful answers, thank you!

    0 comments No comments

  4. SunnyNiu-MSFT 1,706 Reputation points
    2020-12-10T09:19:50.987+00:00

    @zolkin
    Windows 10 version 2004 and 20H2 share a common core operating system with the same set of system files. In other words, the new features of Windows 10 version 20H2 are included in the quality update released on October 13, 2020 of Windows 10 version 2004, but it is in an inactive and dormant state.
    Your Win10 version is 2004 (19041.630), indicating that you have installed the November 10, 2020—KB4586781 update. You need to use the Feature Update through Windows 10, version 20H2 Enablement Package to activate the Windows 10 version 20H2 feature to upgrade to Windows 10 version 20H2.
    As shown below:
    46844-11.png
    You may get more detailed information from the reference article: https://support.microsoft.com/en-us/help/4562830/feature-update


    If the response is helpful, please click "Accept Answer"and upvote it.
    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.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.