locked
SCCM 1602, Windows 10 Service Plan: 1607-1703 update conflict? RRS feed

  • General discussion

  • Have been handed an SCCM ADR that was meant to update Win10 from 1511 to 1607.

    As a test of process SCCM Service Plan is configured (by a contractor) to run 8 months and 14days after release of the upgrade; in this case 1607 was deployed on the 16/04/17.

    The ADR/Service Plan created the deployment as expected including triggering the download of the 1607 Upgrade on the WSUS server.

    On review of the SSRS report for the  (Computers failing with a specific scan error) produced 11423 (-2145120257). This lead to reviewing the WindowsUpdate.log on the Test PC.

    Error in the windows update log:

    Two Swap OSUpgrades are found, Update1 = {7F016D4C-C9A6-4699-A7DA-3D86EF81843F}.201, Update2 = {83695761-2AAC-4890-B68E-94B01BAC720C}.200

    FilterInappropriateOSUpgrade failed, hr=80240FFF

    In SCCM the Unique Update ID

    {7F016D4C-C9A6-4699-A7DA-3D86EF81843F} is in relation to Feature update to Windows 10 Enterprise, version 1607, en-us

    {83695761-2AAC-4890-B68E-94B01BAC720C} is in relation to Feature update to Windows 10 Enterprise, version 1703, en-us

    Is similar to this issue:

    https://social.technet.microsoft.com/Forums/en-US/182478a7-36bb-4ef5-8419-e794d2999e9a/strange-error-and-no-1511-upgrades-with-code-filterinappropriateosupgrade-failed-hr80240fff?forum=winserverwsus

    The WSUS server is internal and I can confirm the PC is looking at the internal WSUS server. The Sync of WSUS, Download and distribution was completed as expected not sure why I am getting the issue above. Only the 1607 update is downloaded on the WSUS and is the only available within the constraints of the service plan dates?

    Anything else just ask..

    Can anyone advise?

    Tuesday, April 18, 2017 12:47 PM

All replies

  • I am having the exact same issue. I recently updated SCCM to the 1702 release. Since the release of the Windows 10 1703 to Windows Update all the updates that were published on the clients disappeared. I finally found the WindowsUpdate.log on the client which provided the clues I was after.

    I had already tried a rebuild of WSUS but this hasn't helped the matter. It is strange because the 1703 update in SCCM hasn't been downloaded or deployed only 1607. I will try declining 1703 through WSUS console to see if that works.


    Wednesday, April 19, 2017 2:36 PM
  • I am having the exact same issue too.

    I also experienced the SNAFU on this past Patch Tuesday (04-2017) where WSUS catalog Syncs in ConfigMgr were failing due to the Upgrade classification being selected. Following David James advice I deselected the classification so the catalog would Sync. The next day he said it could be enabled again.

    Not sure if this has relation to the issue but I am wondering if turning off the Upgrades Classification will fix this issue to.


    Thursday, April 20, 2017 2:26 PM
  • Other machines were not getting the "Two Swap OSUpgrades are found" error. But we were getting hr80240FFF errors in the log that prevented other updates.

    The issue resolved itself after manually applying kb4015219 to 1511 machines. The article mentions "Addressed issue that might sometimes lead to updates not getting installed on machines due to file corruption." We ended up building a software package to deploy it to machines. 

    We are testing the declining of the 1703 Update in WSUS as it is a better solution to resolving the issue. 

    Tuesday, April 25, 2017 2:08 PM