November’s patches to start with gave the impression somewhat risk free, with a few catastrophic issues in 64-bit Office 2010, which is a little bit of a status funny story anyway.
As the month melted on, we noticed a Win10 model 1803 2d cumulative replace, KB 4467682, that led to havoc, together with blue monitors on Surface Book 2 PCs, and custom designed Start Menu insects (thx, Günter Born). Microsoft yanked it on Dec. 6 — no small comfort to the ones of you who install the whole lot as quickly because it’s presented. Or even a week later.
We additionally noticed a reappearance of the Windows 10 September-October-November-December 2018 Update, model 1809. This time, 9 weeks after the unique launch, the new cumulative replace turns out lovely strong, even if I’m seeing some reviews of jiggered sleep states.
More Flash maladies
Meanwhile, now we have an emergency Flash Player replace (thanks, Adobe), KB 4471331, launched a couple of days in the past, that addresses a lately lively exploit in the wild. Yes, it’s a December patch. Yes, you must install it now.
Think of it this fashion. The worst it’ll do is reduce to rubble Flash — and that’s doing you a prefer.
Like such a lot of different Flash updates, it screams for you to disable and abandon Flash totally — one thing I’ve been harping about for years.
The Win10 model 1809 improve isn’t being pressured but
As perfect I will inform, Microsoft’s re-re-release of Win10 model 1809, by means of KB 4469342, hasn’t but brought on pressured upgrades. You can run Windows Update on Win10 model 1803, at the second, and be rather positive that you simply gained’t get bumped to model 1809.
That’ll trade quickly.
If you in truth need Win10 model 1809, take a look at your pulse and your IQ, and you should definitely install the new December 2018 Servicing Stack Update, KB 4070788, first. That compensates for the undeniable fact that the Windows updater isn’t good sufficient to replace itself first. No, I gained’t level you to the directions for putting in 1809.
More .Net amusing ‘n’ video games
I’m seeing extra and extra reviews about issues of this month’s .Net patches.
Fuhgeddaboutit. This month’s .Net patches are all non-security patches, and aren’t value your time, or the complications.
Win7/Server 2008R2 Network Card insects proceed
Microsoft has a worm in its Win7 Monthly Rollup that’s been, uh, bugging us since March. If you put in any Win7/Server 2008R2 patches after March and your community connections didn’t cross kablooey, you’re nearly surely OK to continue with this month’s patches.
On the different hand, should you’ve been ready to install patches to your Win7 or Server 2008R2 system, you wish to have to take note of a worm that Microsoft has said.
Symptom: There is a subject matter with Windows and third-party instrument that is comparable to a lacking document (oem<quantity>.inf). Because of this factor, after you follow this replace, the community interface controller will forestall operating.
Workaround: 1.To find the community software, release devmgmt.msc; it’s going to seem underneath Other Devices.
2. To robotically rediscover the NIC and install drivers, choose Scan for Hardware Changes from the Action menu.
Alternatively, install the drivers for the community software via right-clicking the software and deciding on Update. Then choose Search robotically for up to date motive force instrument or Browse my pc for motive force instrument.
That’s a odd, convoluted collection of steps. Microsoft nonetheless hasn’t showed which third-party instrument is at fault, however reviews have it that it’s in large part a VMware drawback. Eight months later, the worm’s nonetheless there, nonetheless said, nonetheless unfixed.
If you’re anxious that putting in this month’s updates will clobber your community interface card, you should definitely take a complete backup earlier than putting in the updates. You too can take @Long goneToPlaid’s recommendation and edit sure registry entries prematurely.
Seek Bar issues
Many of November’s updates come with a caution like this:
After putting in this replace, customers might not be in a position to use the Seek Bar in Windows Media Player when enjoying particular information. This factor does now not impact customary playback.
Microsoft is operating on a solution and estimates a resolution might be to be had mid-December 2018.
If you employ the Seek Bar in Windows Media Player, most likely it’s time you look at one thing a lot more succesful, corresponding to VLC or Plex. But should you completely should have the Seek Bar, in WMP, don’t replace till subsequent Patch Tuesday.
The returning unhealthy penny, KB 4023057
Yesterday Microsoft launched but any other model of KB 4023057, the Update to Windows 10, variations 1507, 1511, 1607, 1703, 1709, and 1803 for replace reliability. This is the 20th or 30th model of the patch.
As I stated on Nov 19, the remaining time it used to be up to date:
@ch100 has presented the simplest rationalization that is smart to me:
KB4023057 used to be and nonetheless is certainly one of the maximum bizarre and unexplained updates in the fresh occasions. This replace hasn’t ever been presented to WSUS, however simplest to Windows Update. This would point out that it intended for unmanaged end-users and unmanaged small industry customers. …
This patch is also risk free, however why it used to be launched and the place it in truth applies, it is nonetheless a thriller.
It’s perhaps related to the 1809 rollout, even if why it didn’t seem in early October when 1809 first raised its unsightly head leaves me baffled.
You don’t want it, don’t need it, and should you in finding it put in, uninstall it. Unless you wish to have to be driven to 1809 at the previous alternative, anyway.
All of this makes correct now a very good time to follow Windows and Office patches. Here’s how to continue:
Step 1. Make a complete machine picture backup earlier than you install the November patches.
There’s a non-zero likelihood that the patches — even the newest, largest patches of patches of patches — will hose your system. Best to have a backup that you’ll reinstall even supposing your system refuses to boot. This, as well as to the standard want for System Restore issues.
There are numerous full-image backup merchandise, together with a minimum of two good loose ones: Macrium Reflect Free and EaseUS Todo Backup. For Win 7 customers, If you aren’t making backups steadily, take a look at this thread began via Cybertooth for main points. You have good choices, each loose and not-so-free.
Step 2. For Win7 and eight.1
Microsoft is blocking off updates to Windows 7 and eight.1 on fresh computer systems. If you might be operating Windows 7 or eight.1 on a PC that’s 18 months previous or much less, apply the directions in AKB 2000006 or @MrBrian’s abstract of @radosuaf’s means to be certain that you’ll use Windows Update to get updates implemented.
If you’ve already put in any March or later updates, your Network Interface Card must be immune to the newest slings and arrows. But should you haven’t been maintaining on patches, see the dialogue in the Network Card insects phase above to offer protection to your self.
If you’re very curious about Microsoft’s snooping on you and need to install simply safety patches, understand that the privateness trail’s getting harder. The previous “Group B” — safety patches simplest — isn’t useless, nevertheless it’s not inside the snatch of standard Windows consumers. If you insist on manually putting in safety patches simplest, apply the directions in @PKCano’s AKB 2000003 and take note of @MrBrian’s suggestions for hiding any undesirable patches.
For maximum Windows 7 and eight.1 customers, I like to recommend following AKB 2000004: How to follow the Win7 and eight.1 Monthly Rollups. Realize that some or all of the anticipated patches for November would possibly not display up or, in the event that they do display up, might not be checked. DON’T CHECK any unchecked patches. Unless you might be very positive of your self, DON’T GO LOOKING for added patches. In explicit, should you install the November Monthly Rollups, you gained’t want (and most probably gained’t see) the concomitant patches for October. Don’t mess with Mother Microsoft.
Watch out for motive force updates — you’re a ways getting them from a producer’s site.
After you’ve put in the newest Monthly Rollup, should you’re intent on minimizing Microsoft’s snooping, run thru the steps in AKB 2000007: Turning off the worst Win7 and eight.1 snooping. If you wish to have to totally lower out the telemetry, see @abbodi86’s detailed directions in AKB 2000012: How To Neutralize Telemetry and Sustain Windows 7 and eight.1 Monthly Rollup Model.
Realize that we don’t know what knowledge Microsoft collects on Window 7 and eight.1 machines. But I’m beginning to consider that knowledge driven to Microsoft’s servers for Win7 homeowners is nearing equality to that driven in Win10.
Step three. For Windows 10
If you’re operating Win10 model 1709, or model 1803 (my present desire), you for sure need to block the pressured improve to Win10 1809. Don’t get stuck flat-footed: Although it looks as if we are transparent correct now, Microsoft might make a decision to push 1809 once more with very little realize. Follow the recommendation in How to block the Windows 10 October 2018 Update, model 1809, from putting in. Of path, all bets are off if Microsoft, uh, forgets to honor its personal settings.
Those of you who run Win10 Pro and adopted my “new tactic” recommendation remaining month — to set “quality update” (cumulative replace) deferrals to 15 days — don’t want to do anything else. Your system were given up to date remaining week, and must be operating high-quality. Don’t contact a factor.
For the remainder of you, together with the ones of you caught with Win10 Home, undergo the steps in “eight steps to install Windows 10 patches like a professional.” Note that clicking “Check for updates” in Step 6 gained’t reason undue heartache at this level: the “seeker” Win10 1709 cumulative replace is operating high-quality; the 2d Win10 1803 cumulative replace has been pulled; the 2d cumulative replace for Win10 1809 (launched in December) might in truth lend a hand; and Microsoft isn’t but forcing an improve to 1809 on Win10 1709 or 1803 seekers. Surely a brief calm earlier than the standard patching hurricane.
You can use the wushowhide process in the “8 steps” rationalization to block KB 4023057 — a patch you for sure don’t need.
For the ones of you operating Win10 Pro, I counsel you apply the directions in Step 7, however go away your complex setup settings like the ones proven in the screenshot.
That’ll ensure that Microsoft has 15 days to pull its unhealthy preliminary patches
Windows patching has became a recreation of whack-a-mole. Make positive you’re the one with the mallet.
Thanks to the dozens of volunteers on AsokayWoody who give a contribution mightily, particularly @sb, @PKCano, @abbodi86, @gborn, @Long goneToPlaid, @Cybertooth and @MrBrian.
We’ve moved to MS-DEFCON four on the AsokayWoody Lounge.