Forum Discussion

Karl-WE's avatar
Dec 07, 2020

WSUS 10.0.17763.678 fails to download any updates since in-place upgrade. Event 10032, 364

Hi everyone,

 

after in-place upgrade from Server 2016 LTSC GUI to 2019 LTSC GUI and running the WSUS post upgrade wizard, the WSUS Server fails to download any updates.

 

Events

364 Error
Content file download failed.
Reason: Value does not fall within the expected range.
Source File: /d/msdownload/update/software/secu/2015/06/sqlserver2014-kb3070446-x64_aab1ac21337a4f0b20d228c21fc7c9eb68418431.exe
Destination File: E:\WSUSFiles\WsusContent\31\AAB1AC21337A4F0B20D228C21FC7C9EB68418431.exe


10032 Error
The server is failing to download some updates.

 

latest WAM is in place and everything else like Clients contacting and DL works fine. Usual optimizations on Pool etc are in place.

 

I have checked the permissions guidance from Adam J. 

(btw. the docs article is still missing in en-us)

 

WSUS Permissions - WsusContent, Registry, and IIS | AJ Tek Corporation

 

 

 

 

  • Karl-WE's avatar
    Karl-WE
    Mar 16, 2021

    bongobakaco yes it was solved. The problem was that after the in-place upgrade from Server 2016 to 2019 the postinstall did delete the proxy password in the settings. As proxy auth was required this was the reason and simply re-enter the password fixed it. 

    cc TanTran 

  • ran another postinstall and reset, but it will stuck on any updates that would need a new download as before, so weird.

    • TanTran's avatar
      TanTran
      Icon for Microsoft rankMicrosoft
      I got a similar case, Upgrade to 2004 from 1809 stuck at finish setup prompt for 5 hours and have to reboot. It turned out the Firewall block slscr.update.microsoft.com. Issue seems to be resolved now with https open for the problem devices. Windows update log show hundred of retries to download from slscr.
      • Karl-WE's avatar
        Karl-WE
        MVP

        bongobakaco yes it was solved. The problem was that after the in-place upgrade from Server 2016 to 2019 the postinstall did delete the proxy password in the settings. As proxy auth was required this was the reason and simply re-enter the password fixed it. 

        cc TanTran 

Resources