Problems / Troubleshooting Patching Windows Server 2016 with WSUS RRS feed

  • Question

  • hi Folks

    we are using WSUS2012R2 and deploy patches (critical updates, security updates & updates) to server2016 - systems.

    the following issues in our environment are pretty strange, maybe the community have some good advices:

    - patch-download stucks at 0% (in our case KB3150513; "2017-05 Update for Windows Server 2016 for x64-based Systems")

    - the Windows update log with the PS-command "get-Windowsupdatelog" breaks with the error "Copy-Item : Cannot find path 'C:\Program Files\Windows Defender\SymSrv.dll' because it does not exist." -> we have uninstalled Windows Defender in our system-build. similar experiences?

    - are there any other recommendations for patching Server 2016 - Systems with wsus2012r2? we read stuff about adding ESD-File-Support in the IIS or Installing the KB3095113. But we think, these both steps will only apply to Windows 10 and not for Server 2016?

    thank you guys for some good advices :-)

    Monday, June 12, 2017 9:04 AM

All replies

  • Hi Sandro,

    1. Did you install any of the monthly rollup in the Server 2016 before, if not, we may install one of the monthly rollup on the Server 2016 manually. There is a know issue that unpatched Server 2016 has some issues downloading updates from WSUS server;


    2. As for the .esd in IIS, it's necessary for upgrade files, for common update files, we have no need to add it to IIS.

    Best Regards,


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

    Tuesday, June 13, 2017 1:46 AM
  • hi anne

    sorry for the late reply. we finally patched up the system directly to the online-service of microsoft. after that, the system could communicate and install later deployed patches without any issues...

    the ESD-File-Support is only needed, when deploying windows 10 - clients.

    But we still have the problem with the ps-command "get-windowsupdatelog".

    Thursday, January 11, 2018 5:34 PM