Server upgrade - not reporting to WSUS RRS feed

  • Question

  • Hi

    we recently upgraded one of our servers to 2012r2 and since the upgrade its not reporting to WSUS

    i followed all the steps in this link


    ive checked the registry keys for WSUS and we are already using the FQDN for the server

    we also changed the IIS pool size to unlimited in case there were a large number of updates 

    is there anything else we can try?

    its just this server that has the issue and only after upgrading the OS 

    Vicky - Technical Support Engineer

    • Edited by flogadob Tuesday, May 19, 2020 12:39 PM
    Tuesday, May 19, 2020 12:38 PM

All replies

  • Firstly, check the WSUS log here: C:\Windows\WindowsUpdate.log

    If the Group Policy has been correctly applied, the agent will reflect this and should show the following on consecutive lines during an update:

    "WSUS server: http://SERVER:8530" 
    "WSUS status server: http://SERVER:8530"

    I hope this helps!

    Tuesday, May 19, 2020 1:10 PM
  • Hi 

    thanks for the reply, i forgot to mention, the GPO is definitely getting applied, ive attached a warning that keeps coming up in the log, i dont know if its relevant

    WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll

    Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

    Tuesday, May 19, 2020 2:45 PM
  • Hi flogadob,

    Thanks for your posting.

    Here are the following steps you may want to try:
    1. Please consider confirming the following services are running in your client:

    2. Please consider trying the following link to check the connection between the WSUS role and the client:


    3. Please consider checking the following options in the WSUS console:

    If you have any updates about this issue, please keep us in touch.


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

    Wednesday, May 20, 2020 6:17 AM
  • Hi,

    these are all as they should be we still have the issue


    Wednesday, May 20, 2020 8:30 AM
  • We have managed to sort this, we removed superseded updates and ran a server cleanup seems to have fixed the issue

    thanks for all the replies

    Wednesday, May 20, 2020 12:11 PM
  • Hi flogadob,

    Thanks for your posting.
    I am glad to hear that your issue was successfully resolved. If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
    Thank you for your cooperation, as always.

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

    Thursday, May 21, 2020 2:49 AM