none
June 12, 2018—KB4284880 - not detected as applicable RRS feed

  • Pergunta

  • Hi,

    I'm trying to update the server 2016, however it does not detect KB4284880 even though it is deployed via sccm.

    The problem is not on SCCM side since some servers in the same setup are receiving this udpate, and some are not.

    This is probably not a coincidence:

    https://support.microsoft.com/en-us/help/4132216/servicing-stack-update-for-windows-10-1607-may-17-2018

    • Addresses an issue that might sometimes lead to incorrect checks for applicability during installation of Windows Updates.

    However it does not seem to help.

    If I download KB4284880 and trigger the installation manually it is proceeding as expected.


    • Editado Aurimas N sexta-feira, 15 de junho de 2018 14:08
    sexta-feira, 15 de junho de 2018 12:22

Respostas

  • We have narrowed the scope and it seems in our case this only happens to the vanilla servers (those that have no updates installed yet), therefore we found a workaround:

    Even though previous cumulative update (2018-May kb4103723) is superseded and should not be required, only after installing it in conjunction with kb4132216, our servers detect 2018-June cumulative update kb4284880 as applicable.

    • Sugerido como Resposta LordHoradrim quarta-feira, 20 de junho de 2018 13:17
    • Marcado como Resposta Aurimas N quarta-feira, 4 de julho de 2018 07:10
    quarta-feira, 20 de junho de 2018 08:43

Todas as Respostas

  • I'm getting exactly the same issue. Our maintenance window starts, kb4132216 installs instantly but doesn't require a restart. Half an hour later, still within the 6 hour maintenance window, the server does another scan for updates but finds nothing except the latest Defender definition update.

    As far as I can see no 2016 servers are applying kb4284880, they aren't failing it just isn't detected. It is in SCCM which handily reports the boxes as non-compliant as they haven't installed the update. It has the correct Deployment.

    quarta-feira, 20 de junho de 2018 08:34
  • We have narrowed the scope and it seems in our case this only happens to the vanilla servers (those that have no updates installed yet), therefore we found a workaround:

    Even though previous cumulative update (2018-May kb4103723) is superseded and should not be required, only after installing it in conjunction with kb4132216, our servers detect 2018-June cumulative update kb4284880 as applicable.

    • Sugerido como Resposta LordHoradrim quarta-feira, 20 de junho de 2018 13:17
    • Marcado como Resposta Aurimas N quarta-feira, 4 de julho de 2018 07:10
    quarta-feira, 20 de junho de 2018 08:43
  • You're luckier than us. It is occurring to all our 2016 servers nearly all of which have previous Cumulative Updates installed.
    • Editado Eric G-S quarta-feira, 20 de junho de 2018 08:50
    quarta-feira, 20 de junho de 2018 08:50
  • It seems that the Servicing Stack update basically kills any chance of the Cumulative Update applying in that Maintenance Window. I took a server which was not detecting out of the Window and forced an Update Evaluation and it picked up the Cumulative Update and is installing it. I'm pretty confident that if I configured an extra Window and put the non-detecting servers in it then they would detect and install correctly.

    The problem now is that we only have one Window a month agreed with our customers and even if I can get by that a Change Freeze has just been declared on one of the systems. GAH!

     
    quarta-feira, 20 de junho de 2018 10:51
  • Same problem here...

    Chris

    quarta-feira, 20 de junho de 2018 13:06
  • I do have similar issue, I am using Windows Server 2016 Core and I can manually deploy MS patch 4132216 but when I deploy the cumulative update KB4284880, it gets installed but it is not showing up in the deployed patch list. Also even after multiple reboots, whenever I run the patch manually, it asks me to deploy it again.

    Not sure whether KB4284880 is really applicable or not? We have tried deploying these 2 patches via SCCM and only KB4132216 got installed hence we decided to manually deploy the patches and now facing this weird issue.

    Any help would be appreciated!!!

    
    quarta-feira, 20 de junho de 2018 19:08
  • We have the same with KB4284880.

    Only 4 out of 350 Windows 2016 are applying this KB, the 346 says they are already compliant.

    Weird

    quinta-feira, 21 de junho de 2018 11:41
  • Hey Aurimas,

    SSU KB4132216 must be installed before installing KB4284880 as per 

    https://support.microsoft.com/en-gb/help/4284880/windows-10-update-kb4284880 

    Install it from the Software Centre and then re-evaluate software update deployments for that/those client/s.



    • Editado Ben Whitmore quarta-feira, 4 de julho de 2018 07:07
    quarta-feira, 4 de julho de 2018 07:06
  • Hey Aurimas,

    SSU KB4132216 must be installed before installing KB4284880 as per 

    https://support.microsoft.com/en-gb/help/4284880/windows-10-update-kb4284880 

    Install it from the Software Centre and then re-evaluate software update deployments for that/those client/s.



    I've already stated in the OP that it does not solve the issue
    quarta-feira, 4 de julho de 2018 07:09
  • I am having the same problem.  I have also already installed KB4132216 and restarted multiple times.  This is a fairly new server with very little done to it.
    quinta-feira, 5 de julho de 2018 17:39
  • I am seeing indications that KB4284833 has superseded KB4284880 and it is Nessus that is wrong. 
    quinta-feira, 5 de julho de 2018 17:47
  • The below worked for us too. As this was only happening on a fresh built server we created a new update group and added the 3 KB's and any new servers built now are happily patching away.

    So much for the idea of "Superseded Cumulative Updates"!

    "We have narrowed the scope and it seems in our case this only happens to the vanilla servers (those that have no updates installed yet), therefore we found a workaround:

    Even though previous cumulative update (2018-May kb4103723) is superseded and should not be required, only after installing it in conjunction with kb4132216, our servers detect 2018-June cumulative update kb4284880 as applicable."

    segunda-feira, 9 de julho de 2018 14:48
  • I am seeing this same problem with Windows 10 1607 PCs. KB4132216 is installed but the June cumulative KB4284880 is displaying as not required in SCCM. I am unable to find KB4284833 in SCCM which makes me think it is not in WSUS. Is there any chance this problem may be fixed with the July 2018 cumulative update that should come out today?
    terça-feira, 10 de julho de 2018 13:42
  • We've had the similar issue with patching deployment via SCCM 2016, any Server 2016 servers below the May 2018 build level will not accept the latest CU kb4343884/KB4457131, even with SSU KB4132216 installed. However, the manual installation of the CU KB .msu file will work without issue.

    So we then made a SCCM deployment package, to install both KB4132216 and kb4343884 .msu files obtained from Update Catalog. Then deploy the CU released later (KB4457131) via SCCM Software Update deployment, the CU would be accepted as applicable, and the installation completed without issue.

    sexta-feira, 21 de setembro de 2018 02:07