Vulnerabilities

Microsoft Kicks Off New Patch Process

Today is the first day of Microsoft’s new patch process for Windows 7 and 8.1. It is moving all supported non Windows 10 PCs steadily towards the Windows 10 update model. 

<p><span><span><strong>Today is the first day of Microsoft's new patch process for Windows 7 and 8.1. It is moving all supported non Windows 10 PCs steadily towards the Windows 10 update model. </strong></span></span></p>

Today is the first day of Microsoft’s new patch process for Windows 7 and 8.1. It is moving all supported non Windows 10 PCs steadily towards the Windows 10 update model. 

The plans were first announced in August 2016, but October’s Patch Tuesday is when it begins. Microsoft’s director of product marketing, Michael Niehaus, elaborated in a blog post Friday Oct. 7.

From today, there will be two updates released on each Patch Tuesday (the second Tuesday of each month): a ‘security-only’ update and a separate ‘monthly rollup’ that combines security and non-security updates. One week later there will be a Preview Tuesday (the third Tuesday of each month) monthly rollup, described as an “additional monthly rollup containing a preview of new non-security fixes that will be included in the next monthly rollup, as well as fixes from all previous monthly rollup.”

Early next year Microsoft will for several months add older fixes to this preview rollup, “so it will eventually become fully cumulative; installing the latest monthly rollup will then get your PC completely up to date.” The Microsoft recommended route, “which ensures that all fixes for Windows are deployed on the PCs that you manage,” is to deploy the monthly rollup. 

Patching is a major problem for admins. The old adage of don’t fix it if it ain’t broken often applies. If software is working fine as is, there is a tendency to avoid the hassle and network strain of adding new patches. At the very least, patching has been a process of applying the most urgent ones as soon as possible, and leaving others until later. Furthermore, if a hotfix had been applied earlier, and it is working, why worry about the disruption of installing the official patch?

This has resulted in a confusion of different installations with different stages of patch. Before releasing new patches, Microsoft tests against fully patched operating systems — but many user installations are not fully patched. In effect, for many users, new patches have never been tested against their own environments — and this can lead to additional problems when a patch breaks something down the line.

By moving all patches to cumulative rollups, Microsoft will be imposing its own form of order on all installations; aiming for all installations to be fully patched. There are different opinions on the value of this. “Anything that helps keep systems up to date with security patches is a move in the right direction,” suggests Amit Sethi, principal consultant at Cigital. “We constantly hear about systems being compromised because they are running outdated software that contains known security vulnerabilities. The simplified update process should make it easier to keep Windows 7 and Windows 8.1 systems patched with all available security updates.”

Others, however, fear the opposite might happen. By forcing users to patch all or nothing, some companies might delay the process until they see whether there are any problems encountered by other companies. While admins can currently roll back a single bad patch, they will in future have to roll back the whole cumulative update if it becomes necessary. Any ‘wait and see’ delay will mean they are critically exposed to the inevitable Exploit Wednesday that follows every Patch Tuesday.

Advertisement. Scroll to continue reading.

“The time to get a patch in place is probably going to take longer,” said Chris Goettl, a product manager at Shavlik in the Redmond Magazine, Monday. “As this stretches out, you’re going to see the average time for an enterprise to get a patch in place is going to take additional time.”

Microsoft would seem to be aware of this problem and suggests that any company worried about the quality of the patches should subscribe to the Preview option. This could then be tested in a controlled environment. “To minimize the potential impact on an organization,” it suggests, “we recommend that you always have a ‘ringed’ deployment approach for all updates, starting with the IT organization, expanding to one or more pilot groups, followed by one or more broad deployment groups.  Allow sufficient time between rings for users to report any issues that they might see.”

One way or another, however, cumulative updates as per the Windows 10 model are coming to everyone.

Related Content

Copyright © 2024 SecurityWeek ®, a Wired Business Media Publication. All Rights Reserved.

Exit mobile version