locked
WSUS (Windows Server Update Services) required updates not match MU/WU (Windows Update) RRS feed

  • Question

  • 1. Why WSUS (Windows Server Update Services) count differs from MU/WU (Windows Update)?

    2. How to configure them appear exactly the same?

    It seems known issue, MU/WU and WSUS treat needed updates differently. 
    Lawrence Garvin:
    • “note that WSUS contains superseded updates which can be reported as Needed if the newest update is not yet installed. WU/MU does not contain superseded updates, so will naturally have a shorter list in any condition. (Ergo, comparing WU/MU to WSUS is kinda like comparing oranges to tangerines, and you need to recognize that the sizes will be different.)”, and much more similar info.

    BUT we do need this numbers be the same. So question is how this could be done that WSUS display the same number that MU/WU?

    Tuesday, January 19, 2016 10:17 AM

Answers

  • There are often updates released to the MU channel that are not offered up to the WSUS channel.  You can manually add the missing update (assuming they are posted to the Catalog) to your WSUS.

    Also it could be due to the classifications you have checked in WSUS.  Review what you have selected, if you don't have ALL of them checked, then this would be another reason for the difference.

    You can't have the numbers be exactly the same.  You can analyze WHY they are different.

    • Proposed as answer by Steven_Lee0510 Wednesday, January 20, 2016 9:19 AM
    • Marked as answer by YMordak Thursday, January 21, 2016 10:12 AM
    Tuesday, January 19, 2016 9:01 PM
  • There are instances where a patch is pushed to the MU channel and not the WSUS.  So unless you manually add the update to WSUS you won't see it.

    Case in point: Windows 10 upgrade patches delivered to upgrade Windows 7 and 8.1 machines to 10.

    Example:

    https://support.microsoft.com/en-us/kb/3132806

    Update for Windows 7 (KB2977759)

    Locale: All
    Deployment: Optional/Automatic Updates and Catalog
    Classification: Updates, Non-Security
    Target platforms: Windows 7
    Approximate file sizes:
    • Windows 7 update: ~ 5313KB
    Description:
    Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.

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

    Not on WSUS/on MU.  But not a security update. 

    MU is more geared towards consumer updates.  WSUS is geared towards business.  I'd argue that you want to spot check WSUS against MU to ensure that your WSUS is doing what you think it's doing.

     

    • Marked as answer by YMordak Thursday, January 21, 2016 10:12 AM
    Wednesday, January 20, 2016 2:59 PM

All replies

  • There are often updates released to the MU channel that are not offered up to the WSUS channel.  You can manually add the missing update (assuming they are posted to the Catalog) to your WSUS.

    Also it could be due to the classifications you have checked in WSUS.  Review what you have selected, if you don't have ALL of them checked, then this would be another reason for the difference.

    You can't have the numbers be exactly the same.  You can analyze WHY they are different.

    • Proposed as answer by Steven_Lee0510 Wednesday, January 20, 2016 9:19 AM
    • Marked as answer by YMordak Thursday, January 21, 2016 10:12 AM
    Tuesday, January 19, 2016 9:01 PM
  • Hi,

    >>So question is how this could be done that WSUS display the same number that MU/WU?

    As far as I know, there is no way to achieve this. Not all updates will be pushed through WSUS.

    Best Regards.


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, January 20, 2016 9:19 AM
  • The following link may be helpful:

    http://blogs.technet.com/b/sus/archive/2008/07/02/wsus-so-why-do-updates-offered-on-windows-update-differ-from-those-wsus-reports-as-needed.aspx


    Balaji Kundalam

    Wednesday, January 20, 2016 9:26 AM
  • Thank to All who answered! I've searched a lot due to how to fix this and "You can't have the numbers be exactly the same." or "As far as I know, there is no way to achieve this." - are helpful in some degree, but still have hope that someone has workaround how to configure it.

    Which number to believe is correct WSUS or MU? Is there any arguments for MU against WSUS for retrieving reports data?

    Wednesday, January 20, 2016 2:29 PM
  • There are instances where a patch is pushed to the MU channel and not the WSUS.  So unless you manually add the update to WSUS you won't see it.

    Case in point: Windows 10 upgrade patches delivered to upgrade Windows 7 and 8.1 machines to 10.

    Example:

    https://support.microsoft.com/en-us/kb/3132806

    Update for Windows 7 (KB2977759)

    Locale: All
    Deployment: Optional/Automatic Updates and Catalog
    Classification: Updates, Non-Security
    Target platforms: Windows 7
    Approximate file sizes:
    • Windows 7 update: ~ 5313KB
    Description:
    Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.

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

    Not on WSUS/on MU.  But not a security update. 

    MU is more geared towards consumer updates.  WSUS is geared towards business.  I'd argue that you want to spot check WSUS against MU to ensure that your WSUS is doing what you think it's doing.

     

    • Marked as answer by YMordak Thursday, January 21, 2016 10:12 AM
    Wednesday, January 20, 2016 2:59 PM