Where we stand with the October patches

Topic

New Reply

What a weird month. First we got the third round of patches for a zero-day in Internet Explorer (which never materialized) and then Start, Search and
[See the full post at: Where we stand with the October patches]

4 users thanked author for this post.

Lori, Northwest Rick, GreatAndPowerfulTech, abbodi86

Reply | Quote

Replies

So it’s looking good for the Oct 2019 Windows 7 Security Only Updates being telemetry free and no breakage as well on 7 compared to Windows 10.

But folks need to be reminded of any latest Windows 7/other Windows versions related Servicing Stack and SHA-2 KB updates/KB reissues  that have occurred and the latest month that they where issued/reissued.

I have at least one servicing stack KB and one SHA-2 KB from around March 2019 but I do not remember installing any newer versions after March 2019.

I have skipped the W7 Security Only for 2019 for the months of July and September and for September I have also skipped the IE cumulative updates as there where other issues  on IE that month that hopefully will be fully fixed with the Oct 2019 IE cumulative update.

So I’m just waiting for DEFCON3 to happen and things cleared for the most part to be installed.

 

Reply | Quote

Anonymous, according to you: “So it’s looking good for the Oct 2019 Windows 7 Security Only Updates being telemetry free”

What do you know that makes you feel upbeat about the Windows 7 SO being telemetry-free? I’ve seen nothing about that in the Computerworld article on the October patches by Woody, with a link to it in the Home Page full post. Is it there, but I missed it?

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

Reply | Quote

Look back at the posts from Patch Tuesday and/or a day or two afterward. I think there was a remark from someone who had looked through the included files.

1 user thanked author for this post.

OscarCP

Reply | Quote

[Tex265]

So much for 1903 issues.

Where are you on 1803, 1809, and Windows 7?

What’s the plan for the many of us on 1803 to follow?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

• This reply was modified 5 years, 4 months ago by Tex265.

Reply | Quote

So far, running a clean Windows 10 Pro version with client Hyper-V turned on and running all workloads in virtual machines (Windows XP SP3 through Windows 10 1909 and some Linux distros) works well. That way, it’s easy to keep a golden VM to quickly build new VMs and if Microsoft messes up, which happens frequently these days, all it takes to restore a VM is copying a VDHX file from backup. Additionally, new Windows version can be tested in a VM before upgrading the host.

Reply | Quote

Group A ,  Wx64.  Home Premium.  No problems so far.  Took the roll up first day of issue.

Reply | Quote

So, bottom line, we’re still stopped dead at Defcon 1, even though quite a few people have updated their Win 7 and even Win 10 machines without a hitch.  Jan. 2020 has come early it seems.

Being 20 something in the 70's was far more fun than being 70 something in the insane 20's

Reply | Quote

There are two (2) weeks before Patch Tuesday. There is no terrible malware in the wild waiting to bite us.
What’s the hurry?
I know.  It’s like an itch wanting a scratch! 🙂
But WAIT for DEFCON-3 or above.

1 user thanked author for this post.

Charlie

Reply | Quote

There are thirty-five days between 2nd Tuesdays this month, 8th October to 12th November. We are just now a smaller fraction over three-fifths through the available period for testing and waiting. I read today’s blog article to indicate that Woody has not forgotten and is keeping an eye on the situation. It did not suggest to me a final opinion on this month’s status. I’ll be ready when Woody writes the next batch of directions.

Reply | Quote

Charlie, as a Group-Ber myself, I’ve seen many folks take the plunge as soon as there’s a new month of updates and then report their results (for everyone’s benefit). More often than not Woody has changed DEFCON to 3 or higher at the end of that month (October, in this case), or shortly before the following month’s updates.

I’m ‘assuming’ that we’re not yet seeing DEFCON 3 as Woody is defining what the best approach(es) to take are for each version of Windows, especially with the [mess] that turned September’s DEFCON from 3 to 1 within days, before some of us even had a chance to install September’s updates.

I, too, will be happy to see DEFCON 3 🙂

Win 7 SP1 Home Premium 64-bit; Office 2010; Group B (SaS); Former 'Tech Weenie'

2 users thanked author for this post.

Charlie, Northwest Rick

Reply | Quote

Don’t get me wrong, I’m really glad to get a break from the nerve wracking chore of doing the monthly MS updates!  I’m also glad to hear that there are no major threats to worry about.  I’m not complaining.

Being 20 something in the 70's was far more fun than being 70 something in the insane 20's

1 user thanked author for this post.

SueW

Reply | Quote

I don’t know when this Bug in Win10 File Explorer’s “List” View showed up nor if it was introduced by a patch or something else. Fortunately it’s not earth shattering and I can live with it because I rarely use [List] view anyway.
But it’s intriguing nonetheless.

1 Desktop Win 11
1 Laptop Win 10
Both tweaked to look, behave and feel like Windows 95
(except for the marine blue desktop, rgb(0, 3, 98)

Reply | Quote

Update:

For file names File Explorer uses font Segoe UI.
I changed the system font to Arial, rebooted and changed back to Segoe UI and rebooted again.
The weird phenomenon disappeared. See the attached test.doc

I don’t understand what happened. But I don’t really care because things are back to normal.

P.S. To change the system font I used Winaero Tweaker[/url], recommended by Deanna McElveen.

1 Desktop Win 11
1 Laptop Win 10
Both tweaked to look, behave and feel like Windows 95
(except for the marine blue desktop, rgb(0, 3, 98)

1 user thanked author for this post.

rexr

Reply | Quote

The calm before the storm 🙂

Reply | Quote

Transport Layer Security (TLS) connections might intermittently fail or timeout when connecting

2 users thanked author for this post.

Microfix, woody

Reply | Quote

I took the plunge two months ago on Win10 v1903 build 18362.267, and two days ago updated to Build 18362.418 via CU KB4517389 with SSU KB4521863. And also let .Net Framework update because i’ve had no problems with .Net yet.

I use WuMgr to prune updates if needed, per Susan Bradley’s patchwatch, and Winaero Tweaker to block updates until they are “ready”, and to tweak some Windows settings.

I then locked down my computers again from WU to prevent v1909 auto-installing until the pros give it a thumbsup. Using Tylenol is good while doing Windows Updates.

Win10 Pro 20H2,backups with Macrium Reflect home edition

Reply | Quote

So, have I read correctly that the second October IE CVE-2019-1367 fix (KB 4519974) is finally ready for prime time? Or is it still somehow flawed, and it might be prudent to wait to see what November brings? I stopped at the August IE update (KB4511872), and like SueW above, I am waiting for October’s DEFCON to flip from 1 to 3.

I have tried to follow the narrative between Woody’s Computerworld articles and commentary by Loungers, but with so much going on, it’s easy for an occasional visitor (moi) to get lost.

Many thanks!

1 user thanked author for this post.

SueW

Reply | Quote

Wait for Woody’s DEFCON article on ComputerWorld when he raises the number to 3 or above. He will probably clarify the hanging points.

3 users thanked author for this post.

SueW, LHiggins, Northwest Rick

Reply | Quote

OK, I volunteered to be Cannon Fodder this time, as with all the fires here I may not have another chance…

Installed:

Windows Malicious Software Removal Tool x64 – October 2019 (KB890830)

and

2019-10 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4519976)

…and a weird thing happened: upon reboot, it went through all the motions, then said, “shutting down” and rebooted again, this time right to the login, past that, and now all seems normal.

This “double-booting” thing after an update seems to have happened twice before; bears watching. (Bears is a good simile for computer work…”I can’t BEAR that…please BEAR with me…this is Unbearable…”

Win7 Pro SP1 64-bit, Dell Latitude E6330, Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Greenhorn
--
"The more kinks you put in the plumbing, the easier it is to stop up the pipes." -Scotty

3 users thanked author for this post.

Fred, Myst, DrBonzo

Reply | Quote

I always reboot twice after updates, with about 10 minutes between. Fixes all sorts.

cheers, Paul

1 user thanked author for this post.

Myst

Reply | Quote

Same thing (double booting) happened to me on each of a W7 Starter 32 bit and a W7 Pro SP1 64 bit when I installed the security only patch (KB4520003) The double boot has happened to me a couple of times previously. But it has never caused any adverse effect(s) that I can discern.

Everything seems fine on the above two machines. I also installed the IE 11 patch KB4519974, and of course I had all the proper SSU and SHA-2 prerequisites.

I’ve also installed the October Rollup on an 8.1 Pro 64 bit machine with no adverse effects and no double boot (KB4520005).

Good luck with the fires.

1 user thanked author for this post.

SueW

Reply | Quote