October 2020 introduced a lighter-than-usual crop of patches. For the primary time in fresh reminiscence, there have been none at all in favour of Web Explorer or the (Chromium-based) Edge browser. The cumulative updates went in with few reviews of issues, despite the fact that there have been many court cases about printers now not running after the replace.

Odd issues came about, although, outdoor the standard per thirty days patching time table. The day after Patch Tuesday, Microsoft introduced a(nother) repair for a safety hollow within the HEVC codec — CVE-2020-17022 — dispensed, as soon as once more, most effective during the Microsoft Retailer.

HP’s Safe Click on Endeavor began falling over right away after putting in this month’s Home windows cumulative updates. HP launched a Win10 update-friendly model a few days later. It continues to astound me mainstream product from a significant producer isn’t examined earlier than the cumulative updates roll out.

There was once a safety hollow plug in particular for Visible Studio programmers, CVE-2020-17023.

Then there’s the safety patch for Microsoft Dynamics 365 Trade, CVE-2020-16943, that was once introduced however by no means gave the impression. It’s nonetheless lacking in motion. One thing in there about counting chickens earlier than they’re hatched.

As traditional, we had dire warnings galore from the standard patch-right-now assets (“Microsoft warns beeeelions of shoppers to patch right away!”). As traditional, we haven’t observed any right away exploited safety holes, with the imaginable exception of SharePoint Server 2016 and 2019. 

The standard grab-bag of insects

Each and every month for the previous yr or two, we’ve observed a large accumulation of insects arrive at the heels of Patch Tuesday. This month’s no exception. You’ll be able to see a motley choice of blocked replace error messages, error codes, blue monitors, crashes, and peripheral issues in Mayank Parmar’s article in Home windows Newest, Lawrence Abrams’ piece for BleepingComputer, Venkat’s rundown in Techdows, Günter Born’s put up in Born’s Tech and Home windows Global, and numerous parrot websites across the internet.

I don’t see any specific trend to any of it, which has turn out to be an increasing number of not unusual. New patches simply appear to deliver alongside a trove of unrelated insects, any one among which can also be massively irritating — however none of which appear to be specifically standard.

The only exception: I’ve observed many reviews of printers that prevent running after the newest cumulative replace will get put in. In each and every case I’ve observed, pulling the plug at the printer and plugging it again in solves the issue — a very easy job for people, now not such a lot for admins.

‘Home windows can’t check the writer of this driving force device’

Some individuals are reporting an surprising error when putting in positive drivers. Microsoft describes the placement within the Resolved problems portion of the Home windows Liberate Knowledge Standing web page:

When putting in a third-party driving force, you could obtain the mistake, “Home windows can’t check the writer of this driving force device.” You might also see the mistake “No signature was once provide within the matter” when making an attempt to view the signature houses the usage of Home windows Explorer.

This factor happens when a number of of the next is found in a driving force package deal:

• An improperly formatted catalog record is recognized throughout validation by way of Home windows. Beginning with this free up, Home windows would require the validity of DER encoded PKCS#7 content material in catalog information. Catalogs information will have to be signed in line with phase 11.6 of describing DER-encoding for SET OF contributors in X.690.
• A driving force catalog record extension isn’t probably the most supported extensions.

That’s a characteristic, now not a worm. Microsoft suggests that you just touch the motive force producer and ask for an replace. In case your dealer isn’t actual serious about maintaining with Home windows 10, smartly, funny story’s on you. Günter Born places it succinctly: Home windows is a big exterminator, rendering nonetheless running gadgets as digital waste, as a result of drivers can not be put in.

‘Not obligatory’ .NET previews aren’t not obligatory any longer

We’ve observed this downside for a number of months, and it nonetheless hasn’t been fastened.

Home windows Replace doesn’t maintain the .NET “Preview” per thirty days rollups the best way you (or no less than, I) would be expecting. Cumulative Replace previews must be manually licensed by way of clicking a “Obtain and set up” hyperlink. .NET Previews don’t even be offering the choice.

There’s a convoluted algorithm about Home windows mechanically putting in .NET Previews. @abbodi86 has unrolled the habits this fashion:

The brand new .NET Previews are not anything other from all earlier non-security .NET cumulative updates. They simply have the time period “Preview” in label.

For those who’re a “seeker” (click on Take a look at for updates in Home windows Replace), the .NET Preview replace will likely be  put in irrespective of your different settings.

For those who aren’t a “seeker,” when a typical replace scan takes position, one among two issues will occur. (1) If the former .NET Safety replace isn’t but put in, the .NET Preview replace will likely be flagged as doubtlessly outmoded, and Home windows Replace won’t be offering it. (2) If the newest .NET Safety replace is already put in, the .NET Preview replace will likely be put in.

If that isn’t complicated sufficient for you, @abbodi86 has complete main points right here.

I do not know why Microsoft thinks that its “preview” (i.e., not-yet-ready-for-prime-time) patches must be put in on machines with none caution or opt-out capacity. However there you might have it.

Microsoft pulls again on doubtlessly undesirable PWA apps

When is a PUP installer now not a PUP installer? When it’s a Home windows beta, in fact.

Someone at Microsoft determined it will be a good suggestion to jury-rig some beta check variations of Home windows 10 so that they mechanically put in the brand new PWA (revolutionary internet app) variations of Phrase, Excel, PowerPoint, Outlook and OneNote. A number of beta testers took umbrage at an running gadget that cavalierly put in doubtlessly undesirable systems. A pair days later, Microsoft modified direction, claiming that the pushy habits was once a worm.

Proper. Sean Hollister at The Verge has main points.

Administrative center 2010 and Trade Server 2010 hit finish of lifestyles

As of Oct. 13, each Administrative center 2010 and Trade 2010 fell off the enhance cycle. You gained’t get any longer patches. A pity, in reality, as a result of Administrative center 2010 (regardless of its interface peculiarities) was once an actual workhorse. Patch Girl Susan Bradley has main points.

Model 20H2 (or is it 2009?) rolling out

Microsoft is beginning to make Win10 model 20H2 to be had for the loads — despite the fact that you need to click on “Obtain and set up” to get it. No less than, that’s the speculation.

Making an allowance for model 2004 had virtually no new profitable options, and 20H2 has fewer nonetheless (theme-related shading on Get started tiles? Alt+Tab switching Edge tabs? Puh-lease), the frenzy to 20H2 is now below means. Recall to mind it as but some other cumulative replace, with the exception of it doesn’t plug any new safety holes.

For those who ever wanted a concrete instance of why twice-a-year upgrades for Win10 make completely no sense in any respect, now you might have it.

Patching issues? Hit us on AskWoody.com.