Windows 8.1 Update (KB 2919355) prevents interaction with WSUS 3.2 over SSL

There is a known which causes some PCs updated with the Update (KB 2919355) to stop scanning against Server Update Services 3.0 Service Pack 2 (WSUS 3.0 SP2 or WSUS 3.2) servers which are configured to use SSL and have not enabled 1.2.

Description

The problem is specific to the following scenario when all of the following are true

  1. Client PC has installed Update KB 2919355
  2. with Windows 8.1 Update KB 2919355 attempts to scan against WSUS 3.2 running on any affected platform:
    • Windows SP2, or
    • Windows R2 SP2, or
    • Windows Server 2008 SP2, or
    • Windows Server 2008 R2 SP1
  3. HTTPS and Secure Sockets Layer (SSL) are enabled on the WSUS server
  4. 1.2 is not enabled on the server

Only users who have enabled HTTPS and have not enabled 1.2 on their WSUS 3.2 servers and who are also using these WSUS 3.2 servers to manage PCs running the Update KB 2919355 are affected by this issue. Please note, while we do recommend the use of HTTPS on WSUS servers, HTTPS and TLS 1.2 are not enabled by default.

Workarounds

If you are using WSUS 3.2 on Windows Server 2008 R2, you may perform either of the following steps to restore the scan functionality if you have deployed the Update KB2919355.

  • Enable TLS 1.2 (follow the instructions under More Information > SCHANNEL\Protocols subkey), or
  • Disable HTTPS on WSUS

If you are using WSUS 3.2 on an operating system other than Windows Server 2008 R2, you may perform the following step to restore the scan functionality.

  • Disable HTTPS on WSUS

When releases an update that resolves the issue, you may re-enable HTTPS on WSUS.

plans to an update as soon as possible that will correct the issue and restore the proper behavior for Update KB 2919355 scanning against all supported WSUS configurations. Until that time, we are delaying the distribution of the Windows 8.1 Update KB 2919355 to WSUS servers.

You may still obtain the Update (KB 2919355) from the Windows Update Catalog or MSDN. However, we recommend that you suspend of this update in your organization until we release the update that resolves this issue. You may also find the workarounds discussed in this article to be useful for testing this Update for your organization. Thank you for your patience during this time.

Translate »
%d bloggers like this: