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. WSUS silently fails to synchronize updates released in April 2015

WSUS silently fails to synchronize updates released in April 2015

View products that this article applies to.

Notice
This article also applies to Windows Server Update Services for Windows Server 2012 R2.

↑ Back to the top

Symptoms

Windows Server Update Services (WSUS) silently fails to synchronize updates that are released in April 2015. This includes the updates that were released on April 14, 2015 (Patch Tuesday).

↑ Back to the top

Workaround

To work around this problem, use the following method to manually synchronize new updates in WSUS. Repeat these steps for every update category that you want to synchronize.
  1. In the WSUS console, disable updates from synchronizing. To do this, follow these steps:
    1. In the navigation pane, expand the <server_name> node.
    2. Click the Options node.
    3. In the center pane, click Products and Classifications.
    4. In the Products and Classifications dialog box, click the Classifications tab.
    5. Clear the check box for the classification that you cannot synchronize to WSUS.
  2. Run synchronization in WSUS. To do this, follow these steps:
    1. In the navigation pane, expand the <server_name> node.
    2. Click the Synchronizations node.
    3. In the right pane, click Synchronize now.
  3. In the WSUS console, enable updates for synchronizing. To do this, return to the Classifications tab, and then select the check box for a classification that you want to synchronize.
  4. Run synchronization in WSUS.
  5. Repeat steps 1-4 for any other update classification that you want to synchronize, as appropriate.

    Note You can enable and disable more than one update classification at a time. However, at least one classification most be enabled for WSUS synchronization to occur.
  6. If System Center 2012 Configuration Manager (ConfigMgr) is present in the system, run synchronization in ConfigMgr.
Notes
  • These changes are suggested only as a temporary fix.
  • We recommend that you do not make changes directly in the WSUS console when you use ConfigMgr to manage software updates. By default, ConfigMgr overrides any direct changes that are made in the WSUS console every hour. After you disable or enable Classification, run the synchronization immediately to avoid ConfigMgr overriding the changes.

↑ Back to the top

Status

Some WSUS users reported an intermittent sync problem shortly after the release of the April 2015 security updates. This issue may have temporarily affected WSUS administrators' ability to sync released hotfixes to their top-level WSUS servers. Although the workaround in this article was published, and Microsoft support professionals quickly investigated the reported problem, the cause of the sync failure has not been determined.  

No issues have been reported or connected with the May 2015 security update release, and there are no additional details to report. Microsoft will continue to monitor for any signs of the problem's recurrence.

↑ Back to the top

Keywords: kbtshoot, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 3058255
Revision : 1
Created on : 1/7/2017
Published on : 5/21/2015
Exists online : False
Views : 314