Sometime, you’ll inform your grandkids concerning the halcyon days of July and August 2020, when Microsoft took pity on us poor patching souls and launched few bugs in its stew of Patch Tuesday patches.
Now, it seems to be like we’re effectively on our option to one other mess.
Though it’s nonetheless too early to throw up your palms and peremptorily cross on the September crop, I guarantee you that there is no such thing as a pleasure in Patchville.
Bitdefender bites 1909
Proper out of the gate, many of us working Bitdefender on Win10 model 1903 or 1909 had been handled to a warning when attempting to put in this month’s cumulative replace:
The file DeviceHarddiskVolume2WindowsSoftwareDistributionDownload9e0ac098b282aa922e874fe9c2e52396_ctcWindows10.0-KB4574727-x64.cab is contaminated with Trojan.Ciusky.Gen.13. The menace has been efficiently blocked, your machine is protected.
The method C:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856advert364e35_10.0.18362.1073_none_171f6eef2a0feed0TiWorker.exe manifests ransomware habits and was blocked. Your information have been protected against being altered.
Really useful answer? “Disable Bitdefender through the replace set up or outline an exception,” per Günter Born.
Home windows Subsystem for Linux subsumed
Home windows 10 model 2004 clients who truly use WSL 2, the Home windows Subsystem for Linux model 2, get a nasty shock. After putting in the September cumulative replace, on restart, the up to date methods throw an “Factor not discovered” error with the warning
The distant process name failed.
[process exited with code 4294967295]
Venkat on Techdows reviews that the one recognized answer is to uninstall the cumulative replace.
Paint Store Professional 7 slowdowns
If you happen to’re utilizing the decade-old Paint Store Professional 7 on Win10 model 2004, count on glacial efficiency. Born has a cheap conjecture: “Probably the preview handler for picture information put in by Paint Store Professional 7 is the trigger. Prior to now, such handlers had been the reason for Explorer crashes or robust Explorer actions.“
And the same old litany…
Many of us on-line report the same old vary of issues – “X” doesn’t set up, throws a blue display (strive re-starting repeatedly), Begin menu doesn’t work, Search doesn’t work. The record goes on and on. If in case you have a kind of particular issues, strive scanning the same old month-to-month Reddit thread or the Microsoft Solutions discussion board to see whether or not anybody else has encountered the issue.
Lengthy-standing bugs proceed to indicate up, together with the momentary person profile bug that results in lacking information, logon issues, and disappearing desktop icons. Mayank Parmar at Home windows Newest has a dialogue of the evergreen ESENT 642 warning bug. Lawrence Abrams at BleepingComputer explains how the “Optimize Drives” defrag date bug has been mounted – however the bug that trims onerous drives persists. @EP warns that a few of the Intel microcode updates could also be provided to machines that don’t want them.
As standard, the official Home windows Launch Info record covers only a few of the recognized issues.
Excellent news: Bye-bye Servicing Stack Updates
Aria Carley at Microsoft introduced that the Home windows installer is now, immediately, miraculously, able to updating itself, with no separate Servicing Stack Replace. (Typically I feel Home windows will flip into a contemporary working system!) The change solely impacts people who set up cumulative updates manually, or use one of many Microsoft replace administration instruments:
Our purpose is for all IT directors, whether or not managing gadgets on-premises or from the cloud, to expertise the simplicity of getting a single cumulative month-to-month replace to deploy that features the month’s cumulative fixes and the suitable servicing stack updates for that month, if relevant.
The one catch: With a purpose to do away with SSUs, you need to set up the newest SSU. Hen, meet egg. For these of you who use Home windows Replace, it’ll all occur mechanically.
Is Microsoft fixing a bug behind our backs?
@NetDef has an fascinating statement on AskWoody:
Two articles a few month aside are — to me — revealing a severe (and up to now un-announced) vuln in WSUS that’s being mitigated quietly… HTTPS internally has lengthy been thought of a finest observe, however not enforced in any approach ought to the sysadmins select to make use of HTTP between the server and shopper machines.
Now right now we see: “To make sure that your gadgets stay inherently safe, we’re now not permitting HTTP-based intranet servers to leverage person proxy by default to detect updates”
My suspicion is excessive right here. This solely is sensible on an inside atmosphere the place a foul actor may spoof updates through a software program proxy. And malware proxies are nothing new, however this means that maybe the cert test on updates packages is just not as safe as we’ve assumed.
Onward with socially distanced bug monitoring
After all, I like to recommend that you just keep away from this month’s patches till we’ve had an opportunity to kind by means of the injury, and Microsoft has had an opportunity to appropriate its bugs. Crowdsourcing works. I count on we’ll see fixes for Bitdefender and the Home windows Subsystem for Linux bugs in brief order. As for the others…, it is onerous to say.
If you happen to hit a bug – or, higher, an answer! – make sure you inform us on AskWoody.
Copyright © 2020 IDG Communications, Inc.