none
Feture updates not available as required for all windows 10 machine RRS feed

  • Question

  • Hi All, 

    Could someone provide their expertise on the Feature updates available on SCCM under  All windows 10 updates. 

    In my environment i have nearby 1700 machines of windows 10 and most of these windows 10 are on 1607 Build, and remaining are approx 250 machines have Windows 10 1709. 

    I am looking to upgrade these machines to 1809 build but however all windows 10 machines do not show Feture update 1809 as required under Windows 10 updates. it only shows 570 machine where this feature upgrade 1809 shows as required. A week or two back it was showing the accurate number i.e 1700 as required, but once 1903 updates pop up in Software centre the number get reduced for 1809 build.  and for 1903 its showing approx all windows 10 machine available in environment. 

    please see attached for details. 

    Wednesday, June 5, 2019 9:51 AM

Answers

  • I am finally able to get it done by disabling the latest Feature update in WSUS. I disabled the 1903 then all the machines shows required 1809 problem solved
    Friday, July 19, 2019 2:26 PM

All replies

  • First, to clarify, what version of ConfigMgr are you running? This is a 2012 forum but I don't think that you are running ConfigMgr 2012.

    The latest feature update should always show as required for systems as that's the generally preferred upgrade path from Microsoft's perspective; however, why does it matter what the console shows for this? If you want your systems to upgrade to 1809, simply deploy 1809 to them. Done. The actual applicability of an update and what a system installs is not determined by what the console shows. Systems install applicable updates deployed to them.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, June 5, 2019 12:53 PM
  • Hi Pawan,

    When 1903 is released previous versions are marked as superseded, hence the required count are showing differently. 

    Also there is an known issue with 1607 cumulative update check the below link 

    https://support.microsoft.com/en-gb/help/4088889/windows-10-update-kb4088889

    As Jason said, you can proceed the upgrade for 1809.

    Thursday, June 6, 2019 6:23 AM
  • Hi Jason, 

    I did deployed this feature update to machines however it does not show up in software centre, So i suspect if it does not shows as required in SCCM then those updattes wont get deployed on such machine. 

    And I am using Configmgr 2012.  Do you recommend any other way to get this update deployed. 

    Regards

    Pawan Kumar

    Thursday, June 6, 2019 9:24 AM
  • Hi,

    SCCM 2012 only supports Windows 10 builds 1507 and 1511, so it is recommended to upgrade to SCCM current branch.

    Here is a link for your reference.
    https://techcommunity.microsoft.com/t5/Configuration-Manager-Archive/System-Center-Configuration-Manager-Support-for-Windows-10-and/ba-p/273771

    Best Regards,
    Tina

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 6, 2019 9:38 AM
  • HI Tina, 

    We are on SCCM 1806 version.

    Regards

    Pawan Kumar

    Thursday, June 6, 2019 10:15 AM
  • Hi Kalyan, 

    I believe the KB you referring to is for LTSB type windows 10. We do not have that in our environment.

    Regards

    Pawan Kumar 

    Thursday, June 6, 2019 10:17 AM
  • That's not ConfigMgr 2012 then.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, June 6, 2019 2:28 PM
  • No, that is not correct as noted.

    Note that applicability on some older Win 10 builds depends on them having the latest CU installed thus have you verified that these 1607 and 1709 systems have the last CUs and servicing stack updates applied to them?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, June 6, 2019 2:38 PM
  • Hi Jason, 

    These machines were showing accurate number as update required 2 weeks back. When the new update 1903 appears in windows 10 updates then 1809 required number decrease. I see that machine is not recognizing the 1809 updates anymore eventhough these machines are still on 1607 or 1709. 

    Regards

    Pawan Kumar

    Thursday, June 6, 2019 2:52 PM
  • > I see that machine is not recognizing the 1809 updates anymore

    How exactly have you validated this? As noted, what's shown in the console is not an accurate reflection of applicability.

    Have you reviewed the WindowsUpdate.log on a target client to see the results of an applicability scan?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, June 6, 2019 2:57 PM
  • HI Jason, 

    If I deploy the update 1809 build on machine having 1607 and 1709 build, it does not install or show in software center even if i deploy it as available.  

    I believe you are right about CU, But how to identify which one is needed so that it can install 1809 on these machines. 

    I ran windows update manually on 1-2 machine these machine install some updates and then after that 1809 update deployment pop up in software centre 

    I checked the history it shows some CU installed by manual updates. But in the ssame case when i ran the windows update manually on other machine then it install different CU  and other updates. So i am bit confused to choose which one the right CU to make such machines detect 1809 upgrade. 

    Regard

    Pawan Kumar

    Monday, June 24, 2019 4:08 PM
  • > I believe you are right about CU, But how to identify which one is needed so that it can install 1809 on these machines.

    The latest CU as you should always be deploying the latest. CUs are "cumulative", hence their name "Cumulative Update" and thus include all previous fixes and CUs. Having a random CU installed is meaningless. Having the latest CU installed is meaninglful.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, June 24, 2019 6:53 PM
  • Hi Jason, 

    I tried to install the latest CU of 1607 but its not completing , it's getting rollback after 99%. I tried all possibilities. 

    Regards

    Pawan Kumar

    Wednesday, July 3, 2019 11:58 AM
  • The something is failing with the update itself and you need to troubleshoot that by examining the Windows event logs on the systems where the rollback is occurring and that is outside the scope of control or visibility of ConfigMgr.. 

    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, July 3, 2019 1:34 PM
  • I am finally able to get it done by disabling the latest Feature update in WSUS. I disabled the 1903 then all the machines shows required 1809 problem solved
    Friday, July 19, 2019 2:26 PM