WSUS server can't connect to Windows Update in Windows Server 2012

Consider the following scenario:

  • You have a Windows Server Update Services (WSUS) server that is running Windows Server 2012.

  • There is a required authenticated proxy running in the environment.

  • You enable the Use user credentials to connect to the proxy server setting together with the username, domain, and password provided in the WSUS console.

In this scenario, the WSUS synchronization performs successfully. However, the WSUS server cannot connect to Windows Update to download the required updates. 

Note This issue also affects the deployment of Microsoft System Center Configuration Manager and Forefront Client Services.

This issue occurs because the system clears the stored network credentials when you enable the Use user credentials to connect to the proxy server setting. Therefore, you cannot connect to Windows Update.

This hotfix is also available at Microsoft Update Catalog

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must be running Windows Server 2012.

To apply this hotfix, you do not have to make any changes to the registry.

You do not have to restart the computer after you apply this hotfix.

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 file information notesImportant Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.16 xxx

    Windows Server 2012

    RTM

    GDR

    6.2.920 0.20 xxx

    Windows Server 2012

    RTM

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Eventcategories.dll

6.2.9200.16384

8,704

26-Jul-2012

03:07

x64

Iiscustomaction.exe

6.2.9200.16579

102,912

12-Apr-2013

00:44

x64

Microsoft.updateservices.catalogsyncagent.dll

6.2.9200.16582

56,832

12-Apr-2013

00:44

x64

Microsoft.updateservices.contentsyncagent.dll

6.2.9200.16582

46,080

12-Apr-2013

00:44

x64

Microsoft.updateservices.reporting.rollup.dll

6.2.9200.16582

93,696

12-Apr-2013

00:44

x64

Microsoft.windows.bits.dll

6.6.4000.16582

131,072

12-Apr-2013

00:44

x64

Wsuscertserver.exe

6.2.9200.16384

64,512

26-Jul-2012

03:08

x64

Wsusservice.exe

6.2.9200.16582

17,920

12-Apr-2013

00:44

x64

Eventcategories.dll

6.2.9200.16384

8,704

26-Jul-2012

03:07

x64

Iiscustomaction.exe

6.2.9200.20682

102,912

12-Apr-2013

00:41

x64

Microsoft.updateservices.catalogsyncagent.dll

6.2.9200.20686

56,832

12-Apr-2013

00:41

x64

Microsoft.updateservices.contentsyncagent.dll

6.2.9200.20686

46,080

12-Apr-2013

00:41

x64

Microsoft.updateservices.reporting.rollup.dll

6.2.9200.20686

93,696

12-Apr-2013

00:41

x64

Microsoft.windows.bits.dll

6.6.4000.20686

131,072

12-Apr-2013

00:41

x64

Wsuscertserver.exe

6.2.9200.16384

64,512

26-Jul-2012

03:08

x64

Wsusservice.exe

6.2.9200.20686

17,920

12-Apr-2013

00:41

x64



Status

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

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File name

Amd64_7ab8b927a14dcc5eda478e71367856cd_31bf3856ad364e35_6.2.9200.16582_none_3e2886e1b40e95fb.manifest

File version

Not applicable

File size

697

Date (UTC)

12-Apr-2013

Time (UTC)

16:49

Platform

Not applicable

File name

Amd64_b93defe8cfebc11f8551c211aff6fa25_31bf3856ad364e35_6.2.9200.20686_none_7c231fff6ef907ce.manifest

File version

Not applicable

File size

697

Date (UTC)

12-Apr-2013

Time (UTC)

16:49

Platform

Not applicable

File name

Amd64_updateservices-services_31bf3856ad364e35_6.2.9200.16582_none_d78cc926490d935c.manifest

File version

Not applicable

File size

56,377

Date (UTC)

12-Apr-2013

Time (UTC)

16:49

Platform

Not applicable

File name

Amd64_updateservices-services_31bf3856ad364e35_6.2.9200.20686_none_d81a671962279882.manifest

File version

Not applicable

File size

56,377

Date (UTC)

12-Apr-2013

Time (UTC)

16:49

Platform

Not applicable



Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×