Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. After you disable the "Download express installation files" option in Windows Server Update Services 3.0, client computers may be unable to receive new updates

After you disable the "Download express installation files" option in Windows Server Update Services 3.0, client computers may be unable to receive new updates

Symptoms

You have a server that is running Microsoft Windows Server Update Services (WSUS) 3.0. The Download express installation files option has been enabled for a while, and then you disable this option. Then, you run the Server Cleanup Wizard to remove the update files that are no longer needed. After you approve an update, one or more client computers cannot receive the update from the server. When this problem occurs, you receive the following error message on the affected client computers:
HTTP status 404 (0x80190194)
Additionally, the following error message is logged in the Windows Update log file (WindowsUpdate.log) on the affected client computers:
<Date><Time> 1580 238DnldMgr WARNING: BITS job {41768452-00D5-410C-976C-5E1BBB4972B0} failed, updateId = {1278EEC8-2BDC-4163-A4FE-CA6F39958529}.101, hr = 0x80190194, BG_ERROR_CONTEXT = 5
Note The Windows Update log file is in the %Windir% folder.

↑ Back to the top

Cause

This problem occurs because the URL of the express installation files is still cached on the affected client computers. Even if you run the Server Cleanup Wizard, the cached is not refreshed. Therefore, the affected client computers still try to download the express installation files.

↑ Back to the top

Workaround

To work around this problem, update the cache on all client computers that connect the server for updates. To do this, use one of the following methods.

Method 1: Empty the SoftwareDistribution folder on client computers

  1. On client computers, stop the Background Intelligent Transfer Service and the Windows Updates service. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the Command Prompt window, type the following commands, and then press ENTER after each command:
      net stop wuauserv
      net stop bits
  2. Rename the SoftwareDistribution folder. To do this, follow these steps:
    1. Click Start, click Run, type %Windir%, and then click OK.
    2. Right-click the SoftwareDistribution folder, and then click Rename.
    3. Type a different name, and then press ENTER. For example, you type the name SoftwareDistribution.old.
  3. Start the Background Intelligent Transfer Service and the Windows Updates service. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the Command Prompt window, type the following commands, and then press ENTER after each command:
      net start bits
      net start wuauserv
Note After you start the Windows Update service, a new SoftwareDistribution folder will be automatically created.

Method 2: Decline the updates that client computers cannot receive

  1. In the WSUS console, identify the updates that client computers cannot receive.

    Note You can use the Update Status Summary report or the Update Detailed Status report to identify the updates that client computers cannot receive.
  2. Change the Approval status of these updates to the value of Declined on the server.
  3. After all client computers finish detecting updates on the server, change the Approval status of these updates back to the original value.

Method 3: Configure the client computers to detect updates from another server that is running WSUS 3.0

  1. Set up another server that runs WSUS 3.0, and then synchronize the new server with Microsoft Update.
  2. Configure client computers to detect updates from the new server.

    For more information about how to point a client computer to a WSUS server, visit the following Microsoft TechNet Web site:
    http://technet.microsoft.com/en-us/library/dd939830(WS.10).aspx
  3. After all client computers finish detecting updates from the new server, configure the client computers to detect updates from the original server.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: kbsurveynew, kbexpertiseadvanced, kbtshoot, kbprb, kb

↑ Back to the top

Article Info
Article ID : 974500
Revision : 3
Created on : 4/20/2018
Published on : 4/20/2018
Exists online : False
Views : 138