none
WSUS was not getting all updates from Windows Update Site RRS feed

  • Question

  • Recently, I discovered that WSUS from my customers is not getting all updates available in Windows Update Site, like the last ones KB4088889, KB4089848, KB4099950, for example. WSUS is able to find all others updates and I can approve its without problems. I think that maybe be a problem inside of site of Microsoft or Microsoft will release this updates later, I don´t know. My customers have WSUS installed in Windows 2012 R2 and 2016 servers, so is not a problem related with the version of O.S. Are there more people with this problem??? Please let me know.

    Thanks

    Tuesday, April 3, 2018 3:08 PM

Answers

All replies

  • I too do not have these updates available on WSUS running on Windows 2016. 

    Google shows others are having the same issues as well.

    Example: https://community.spiceworks.com/topic/2123015-march-22-2018-windows-10-updates-are-not-listed-in-wsus

    Since they are available in the MS catalog you can import them into WSUS.


    Wednesday, April 4, 2018 1:16 AM
  • Yes, they need to be imported manually into WSUS.

    The problem is they do not show as applicable so even if approved they wouldn't get installed. Any ideas how to fix this?

    Wednesday, April 4, 2018 7:54 AM
  • Ok, looks like I'm being impatient... the "installed/not applicable" percentage is slowly rising as pcs are reporting to WSUS.
    Wednesday, April 4, 2018 8:13 AM
  • Thank you for your post. I didn´t find anything about this problem in Internet. I have imported these updates in WSUS and now all client machines are able to download and apply its.
    Wednesday, April 4, 2018 5:28 PM
  • Does anyone know why these are not showing up in WSUS?
    Friday, April 6, 2018 9:06 PM
  • Does anyone know why these are not showing up in WSUS?


    MSFT does not always release updates via WSUS. Some updates *never* release via WSUS, other times, they do come to WSUS later..

    For Windows updates (not Office updates) you can check KB894199 to see if the update has been released to the WSUS channel

    https://support.microsoft.com/kb/894199

    IF the update you want, has not been released to WSUS, you *may* be able to go to MUCatalog and import from there into your WSUS.

    http://www.catalog.update.microsoft.com/Search.aspx?q=KB4088889


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, April 6, 2018 10:44 PM
  • Some updates, specifically the KB 4099950, are rolled into the cumulative update.
    Tuesday, April 10, 2018 5:23 PM
  • Microsoft clearly states that the update KB4099950 should be available through WSUS.

    https://support.microsoft.com/en-us/help/4099950/nic-settings-are-replaced-or-static-ip-address-settings-are-lost-after

    Like others, I am confused why our all of our WSUS servers aren't syncing it.

    Wednesday, April 11, 2018 12:22 PM
  • Did anyone figured this out? Why is KB4099950 available in a catalog download and not in WSUS?
    Wednesday, April 11, 2018 1:23 PM
  • I believe, as stelong stated, it is because KB4099950 is rolled up into other updates.

    https://support.microsoft.com/en-us/help/4088875/windows-7-update-kb4088875

    https://support.microsoft.com/en-us/help/4088878/windows-7-update-kb4088878

    From the above sites:

    After you apply this update, a new Ethernet Network Interface Card (NIC) that has default settings may replace the previous NIC and cause network issues. Any custom settings on the previous NIC persist in the registry but aren't used.

    This issue is resolved by KB4099950 which will be automatically applied when installing this update.

    Wednesday, April 11, 2018 1:45 PM
  • I agree that it's almost certainly included, or else not required in the latest April rollup - KB4093118.

    But in order for this to be included in last month's updates, there would need to be a revised version of them released - when I check WSUS, there is only one revision which occurred on the original release date (13th Mar).

    If you don't release the rollups in your monthly patching cycle, then KB4088878 is still required.

    But KB4099950 does not appear in WSUS, neither has KB4088878 been revised since last patch Tuesday to include it.

    So we're back to manually importing KB4099950... unless the issue is with our WSUS configuration? Does anyone see anything different?

    EDIT: See marked answer - you need to import KB4099950 to WSUS from Microsoft Update Catalog. See also technet post here.


    • Edited by jamesaf Thursday, April 12, 2018 4:40 PM
    Thursday, April 12, 2018 11:38 AM
  • Post Update: The follow updates launched April/2018 are not synchronized with WSUS too: KB4093120 and KB4093105. This is becoming a bad habit from Microsoft. Now I have to check all updates launched in Microsoft Update´s site against WSUS database.
    Tuesday, April 24, 2018 7:19 PM
  • I have this issue too.

    I already manual to import this KB (KB4099950 and KB4088878) but always not to auto update for any client.

    This is very confuse .

    I don't know why the KB4088878 not to auto update any clients.

    The WSUS server already approval install for any group.


    Hi I can't to find solution for solve this issue, I have Event 364 Source File: /Content/1B/DCD02B975BCC454188A2BB1F036E3E590C25641B.exe Destination File: D:\WSUS\WsusContent\1B\DCD02B975BCC454188A2BB1F036E3E590C25641B.exe But I don't know how to deline this KB Number..

    Thursday, April 26, 2018 8:37 AM
  • This is becoming a pain. I have just had to rebuild one of our servers, and after waiting a while for it to update via SCCM nobody can RDP to it (due to the credSSP issue fixed in KB4093120). How do we deploy this update?

    The ENTIRE point of SCCM updates is to make life easier for the sys admins.


    Monday, June 25, 2018 2:28 PM
  • Now for some reason my windowsupdate.log is showing all GUID numbers and not actual text, so I can't troubleshoot! argh! great job MS
    Monday, June 25, 2018 2:52 PM
  • It´s very frustranting when we have a tool that always has worked well and made our work easier along all these years, and now this tool became unreliable. As far as I know by my researches there are several updates that are missing in WSUS and were not sincronized in the last three mounths:

    APRIL

    - KB4093120
    - KB4093105
    - KB4023057
    - KB4056254


    MAY

    - KB4103720


    JUNE

    - KB4284833
    - KB4284848

    It´s getting harder and harder to work with Microsoft. If anyone knows other updates missing, please let me know, Thanks.

    Thursday, June 28, 2018 6:57 PM
  • I just noticed that KB4284848 is actually in our WSUS database and automatically approved, in the category 'Updates' but is showing as 'not applicable' for all WIN 10 workstations.

    However if I rdp into any of these workstations and manually run an online update check, the workstation promptly begins to download and install the update.

    Is there some group policy or registry setting that you could think of that is causing the workstations to pass-up on the update when checking through WSUS, but not when online.
    Friday, July 6, 2018 3:43 AM
  • I just noticed that KB4284848 is actually in our WSUS database and automatically approved, in the category 'Updates' but is showing as 'not applicable' for all WIN 10 workstations.

    However if I rdp into any of these workstations and manually run an online update check, the workstation promptly begins to download and install the update.

    Is there some group policy or registry setting that you could think of that is causing the workstations to pass-up on the update when checking through WSUS, but not when online.
    I don't have KB4284848 within Configuration Manager (WSUS on Server 2016). I've searched and searched and found I may have to manually import it. But I also read it's locking machines when applying so many it didn't make it to WSUS as it's causing issues? 
    Wednesday, July 25, 2018 7:57 PM
  • Hi,

    I got similar problem. I'm using WSUS Server 6.3 (Windows Server 2012 R2).

    I known that some updates may be available in Microsoft Catalog but not in WSUS by default. In my case, it's about WMF 5.0 (PowerShell 5.0) package for Windows 7/2008 R8 using KB3134760.

    This package is available in the Catalog. Microsoft explain clearly that we need to import manually this package in our WSUS server to obtain it. But when the package is in WSUS... it's not marked as necessary for any computer. If I approve it, it still not necessary (even If I known this package could be necessary and can be installed manually). Not really interesting to add a package if this one couldn't be installed...

    It's like something is missing in the WSUS database to put a flag "UP" to tell "Hey, I'm here and available for you."

    Monday, September 17, 2018 12:41 PM