Windows Update Client downloading updates - stuck at 0%

ITSam77 1 Reputation point
2021-08-02T16:52:01.21+00:00

WSUS Server and Clients worked perfectly until we moved the content folder with the WSUS tool to a different server.

If I check the HKLM\Software\Microsoft\Update Services\Server\Setup on the WSUS Server the ContentDir is \192.168.100.13\wsus$\WSUS

All Clients show that updates are available and the download process at 0%.

The WSUS log shows:

2021.08.02 17:46:06.2918534 620 1416 DownloadManager Downloading from http://<server>.<domain>:8530/Content/49/43FBF5F35825FB9ABD6B9AF073D67AFE2B36A449.exe to C:\Windows\SoftwareDistribution\Download\a6b06eaee5b3a327da2de1bc2924b04a\43fbf5f35825fb9abd6b9af073d67afe2b36a449 (full file)
2021.08.02 17:46:06.2918696 620 1416 DownloadManager Created download job <...>; streaming data: No.
2021.08.02 17:46:06.2936638 620 1416 DownloadManager New download job {<...>} for UpdateId <...200>
2021.08.02 17:46:06.2942620 620 1416 DownloadManager Update the URLs for DO Job <...> - Update <...200>
2021.08.02 17:46:06.2970206 620 1416 DownloadManager 0 of 1 files' URLs are updated.
2021.08.02 17:46:06.2973900 620 1416 DownloadManager Download job <...> resumed.

The file (43FBF5F35825FB9ABD6B9AF073D67AFE2B36A449.exe) is available on the disk of the server where the content is moved to.
The URL http://<server>.<domain>:8530/ is the Server where the WSUS is installed, but the content is on a different server.

What is the reason that the download stuck at 0%?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,282 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Adam J. Marshall 8,886 Reputation points MVP
    2021-08-02T17:39:11.88+00:00
    0 comments No comments

  2. Rita Hu -MSFT 9,626 Reputation points
    2021-08-03T06:43:11.8+00:00

    @ITSam77
    I found a related link for your reference. Please follow this link first to make sure WSUSContent moving is successful.

    Note that the link isn't form MS, just for your reference.

    Hope the link will be helpful.

    Regards,
    Rita


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. ITSam77 1 Reputation point
    2021-08-03T13:39:37.987+00:00

    @Rita Hu -MSFT and @Adam J. Marshall

    thank you for your help.
    I studied the links and dokuments very crefully and could not find a foult.
    The only difference we have after moving the content folder that we use a networt path:
    \192.168.100.13\wsus$\WSUS

    All other links and dokuments show only a local path like J:\WSUS.

    Could this be the reason?


  4. Adam J. Marshall 8,886 Reputation points MVP
    2021-08-03T17:49:11.277+00:00

    How are the share permissions on wsus$? Everyone - Full Control?
    What about the permissions on that $wsus folder ?

    0 comments No comments