For February, a ‘bumpy’ Patch Tuesday journey

One week out from Patch Tuesday and it’s been a bumpy launch for the month, particularly for older variations of Home windows 10 and Server 2016. (Much less affected: the patron variations of Home windows 10 2004 and 20H2.)

Home windows Server 2016/1607 suffered the worst of the problems: the unique model of the Servicing Stack replace KB4601392 induced patching to get “caught.” Server patchers needed to soar via a ton of hoops to get the month-to-month safety replace put in. Microsoft pulled the dangerous replace and changed it with KB5001078. When you had been unfortunate and put in KB4601392 earlier than it was pulled, Microsoft has this  steerage to manually reset Home windows updates elements.

Home windows Server 2016 lengthy has had a fame of being a horrible platform to patch. It installs updates slower than Home windows Server 2019 and usually takes longer to reboot afterwards — and Microsoft received’t (or can’t) backport the fixes from Server 2019 to the older platform. Not like Home windows 10, in the event you bought Home windows Server 2016 to your agency, you’ll be able to’t improve to Server 2019 without spending a dime; it’s a further buy. (Given the entire patching points on that platform, Microsoft, ought to present a license to Server 2019 without spending a dime for affected companies.)

When you nonetheless run Home windows 10 1909, you too had been impacted by a buggy replace: KB4601315. I personally seen on my 1909 workstation that I wasn’t provided that replace; I solely obtained this month’s .NET patch. I checked round on and located I wasn’t alone. Others skilled the identical difficulty, particularly on client variations of Home windows 10. Two days after Patch Tuesday, Microsoft launched KB5001028, an “out of band” launch to repair a blue display that occurred whenever you tried to make use of a Wi-Fi Protected Entry 3 (WPA3) connection. Microsoft notes that you’re extra prone to encounter this difficulty when reconnecting to a Wi-Fi community after disconnecting, or when waking from sleep or hibernation. (It is a cumulative replace ,so it may be put in on prime of, or as a substitute of, the sooner February replace.)

Typically folks query why Microsoft’s pre-release beta testing Insider program, can’t discover points like this. The underlying drawback is that the Insider program is testing code for future releases of Home windows, it’s not testing patches and updates on the older releases most individuals nonetheless use. We’ve lengthy complained in regards to the lack of high quality management with Microsoft updates and, sadly, this seems to be one other less-than-stellar set of releases.

Microsoft for a few years has revealed a device that helped us block a hard replace till we had been able to cope with it, or till the replace had a repair launched. Known as the Wushowhid.diagcab device, we’ve used this to dam buggy updates for years. In the previous few weeks, nonetheless, Microsoft pulled the device from its web site with no reason why. The place is that this wushowhide device?

Copyright © 2021 IDG Communications, Inc.

Source Link

Leave a Reply

Your email address will not be published. Required fields are marked *