Featured Articles

5th Generation Broadwell 14nm family comes in three lines

5th Generation Broadwell 14nm family comes in three lines

Intel's 5th Core processor family, codenamed Broadwell, will launch in three lines for the mobile segment. We are talking about upcoming…

More...
Broadwell Chromebooks coming in late Q1 2015

Broadwell Chromebooks coming in late Q1 2015

Google's Chromebook OS should be updating automatically every six weeks, but Intel doesn't come close with its hardware refresh schedule.

More...
New round of Nexus phone rumour kicks off

New round of Nexus phone rumour kicks off

Rumours involving upcoming Nexus devices are nothing uncommon, but this year there is a fair bit of confusion, especially on the…

More...
Nvidia officially launches the 8-inch Shield Tablet

Nvidia officially launches the 8-inch Shield Tablet

As expected and reported earlier, Nvidia has now officially announced its newest Shield device, the new 8-inch Shield Tablet. While the…

More...
Aerocool Dead Silence reviewed

Aerocool Dead Silence reviewed

Aerocool is well known for its gamer cases with aggressive styling. However, the Dead Silence chassis offers consumers a new choice,…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Friday, 11 April 2014 13:43

Hefty Windows patch delayed for 8.1

Written by Nick Farrell



Patches systems can’t receive future updates

The Windows 8.1 Update, which was Redmond’s big patch for Windows 8.1 has been suspended for some enterprise users after the company discovered that patched systems are can’t receive future updates from Windows Server Update Services (WSUS) servers. The patch updates the user interface for desktop and mouse users, but it apparently had a problem playing nice with corporate networks.

The problem occurs when clients connect to WSUS with HTTPS enabled, but without TLS 1.2. Windows 8.1 machines with the KB 2919355 update installed will no longer be able to receive future updates from those servers. Microsoft said the problem is for WSUS 3.0 Service Pack 2, also known as WSUS 3.2, when run on Windows Server 2003, 2003 R2, 2008, and 2008 R2; this version does not have HTTPS or TLS 1.2 enabled by default, but HTTPS is part of the recommended configuration. WSUS 4 on Windows Server 2012 and 2012 R2 is also technically affected, but since Windows Server enables TLS 1.2 by default it is not a major problem.

Microsoft will have to come up with a fix soon as the Windows 8.1 Update is a mandatory security update that will be a prerequisite for all future security fixes for Windows 8.1. A work around is that if client machines have the update installed users, administrators should enabling TLS 1.2 on Windows Server 2008 R2, or disable HTTPS. 

Microsoft describes it primarily as an issue for WSUS 3.0 Service Pack 2, also known as WSUS 3.2, when run on Windows Server 2003, 2003 R2, 2008, and 2008 R2; this version does not have HTTPS or TLS 1.2 enabled by default, but HTTPS is part of the recommended configuration.

WSUS 4 on Windows Server 2012 and 2012 R2 is also technically affected, as the bug is client-side, but Windows Server enables TLS 1.2 by default, so issues are unlikely to arise in practice.

Nick Farrell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments