More Windows patches — and warnings about the Win10 1709 update KB 4089848

Topic

New Reply

In yet another out-of-out-of-band flurry, on Thursday Microsoft released new cumulative updates for all Win10 versions, a couple of Servicing Stack up
[See the full post at: More Windows patches — and warnings about the Win10 1709 update KB 4089848]

2 users thanked author for this post.

JDeC, dononline

Reply | Quote

Replies

I’m ever so grateful that Windows 7 is an orphan.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

12 users thanked author for this post.

Steve, anita.yk, windows7forever, JDeC, Pepsiboy, HiFlyer, Elly, Microfix, Geo, MrJimPhelps, Cybertooth

Reply | Quote

From Henk van Elburg on Twitter:

We’re are receiving update kb4091461 during our sccm deployement even when we blocked windows update by regkey.

https://twitter.com/hvelburg/status/977197143827107841

 

Reply | Quote

From End of servicing notification for Windows 10 Versions 1507, 1511, and 1607:

‘Symptom: Customers with managed PCs running Windows 10 Versions 1507, 1511, or 1607 may experience prompts to update Windows on some of those PCs.

Workaround: Microsoft has resolved the issue, and users receiving update notifications should select “Not right now” to dismiss the update. Cached settings will clear no later than March 31, 2018.’

Reply | Quote

From KristoferA on Twitter:

weirdly: my machine with defer updates enabled suddenly installed 4023057 a week ago without any warning.

 

Reply | Quote

Version 1703 x64.  After being wiped out and getting rid of the “Assistant”, when I redid my updates, I got KB4023057 reinstalled minus the “Assistant” . Have there been any confirmed reports that this new release of this KB contains this “Assistant” malware ?

1 user thanked author for this post.

woody

Reply | Quote

None that I’ve seen.

Thanks for the notice!

1 user thanked author for this post.

bobcat5536

Reply | Quote

Just got this email from MG:

I couldn’t find anything on the web related to my experience, so I figured I would try you. I enjoy following you as I get a sense of insider information!

We applied the following patches or a hyper-v host server and when it rebooted, the nics lost their ip address, subnet mask, and default gateway (dns was fine).

• KB4088875
• KB4089187
• KB4088878
• KB890830

It unfortunately took a little longer than I would have liked to realize the issue, but without knowing what the actual cause was, I’m not sure how to explain this to my management team.

Can anybody confirm?

1 user thanked author for this post.

JDeC

Reply | Quote

The culprit is KB4088875 – as you reported on:
https://www.askwoody.com/2018/buggy-windows-7-monthly-rollup-kb-4088875-no-acknowledgment-from-microsoft/
https://www.computerworld.com/article/3263645/windows-pcs/microsoft-stops-pushing-buggy-win7-patch-kb-4088875-hopefully-as-a-precursor-to-yanking-it.html

Note that (AFAIK) it still hasn’t been yanked.
MS has given a workaround to one of the vNIC issues, and has basically thrown their hands up about the other issue. Our WU pilot patch is on hold because of this mess.

Reply | Quote

Only certain builds of Windows 10 Versions 1507, 1511, 1607, and 1703 require this update.

You have to be a Microsoft groupie to keep all of this straight. And I’m not.

The whole Windows “10” ecosystem is mass confusion. Likely by design. So glad I’m using Linux Mint and not Windows “10”.

Group "L" (Linux Mint)
with Windows 8.1 running in a VM

2 users thanked author for this post.

HiFlyer, Cybertooth

Reply | Quote

The original concept of Windows 10 as a single unified OS that would make life easier for both Microsoft and users alike seems ever more divorced from the reality of the situation with every passing month.

6 users thanked author for this post.

anita.yk, HiFlyer, Cybertooth, dononline, Elly

Reply | Quote

By putting a single number (“10”) in the “title”, and by putting the actual version number in the “subtitle”, they make everyone subconsciously think of it as a single unified OS, when it is anything but.

Microsoft should include the theme and overall purpose of Windows “10” whenever they refer to Windows “10” — “Windows 10 — a whole new way of computing”. Along with that, they should let you choose whether or not to be a beta tester:
* Windows 10 Home is free; by using it, you are agreeing to be a non-paid beta tester.
* Windows 10 Pro is discounted, and you get only tested and proven updates. But you can’t turn off updates.
* Windows 10 Enterprise and above are non-discounted; you get only tested and proven updates, and you can control which updates get installed on your computer.

If they would do Windows 10 in that way, they would have thousands and thousands of people enthusiastically opting for the “free” route; and all of the IT writers, Woody included, would be singing the praises of Microsoft for making a way for people to get a free copy of Windows 10, and for giving people a reasonable way to avoid being force-fed every update.

Instead, we have the mess that is commonly referred to as “Windows 10”.

If Microsoft doesn’t quickly realize the error of their ways, they will at some point find themselves on the outside looking in. I don’t think they have passed the point of no return; but the hour is very late for them.

Group "L" (Linux Mint)
with Windows 8.1 running in a VM

5 users thanked author for this post.

anita.yk, johnf, flackcatcher, HiFlyer, Seff

Reply | Quote

Woody asked in his Computerworld article “When did Microsoft become the enemy?”. I think that was rhetorical. We all know when it happened.

8 users thanked author for this post.

anita.yk, johnf, windows7forever, JDeC, Cybertooth, HiFlyer, Seattle27, satrow

Reply | Quote

For some reason my comment was eaten but…

Apparently in response to the multiple screw-ups, it looks like KB 4088875 now appears as an “Important” update in the Windows Update list, but isn’t checked by default, and doesn’t install automatically, even with Automatic Update enabled. I’m seeing conflicting reports about whether KB 4088875 currently appears on the WSUS list.

This must be why i’m not being offered anything, the february rollup is still there but not march. Which i haven’t installed of course because i’m group b. Also in the uk and i’ve seen comments from other UK people on here saying the same thing.

Reply | Quote

Your comment was automatically marked as spam. We would have un-spammed it for you but you beat us to it. 🙂

cheers, Paul

1 user thanked author for this post.

T

Reply | Quote

I can’t really think why though since i didn’t include any external links. Maybe it was because i tried editing it several times in short order but no matter, thanks for letting me know.

Reply | Quote

Also of note with KB4023057 it appears to install an application named

Update for Windows 10 for x64-based Systems (KB4023057)

This seems to be the application, GWX style, that is forcing the installing outside of a Windows Update service

2 users thanked author for this post.

anita.yk, HiFlyer

Reply | Quote

Even with my ‘tinfoil hat’ removed, I’m suspicious that Microsoft’s long-term goal is to eventually deprecate and ultimately remove local WU management from any and all non-Enterprise versions of Windows 10. Update Assistant may be a symptom of that intent, a proof of concept trial.

Financially and strategically, Microsoft may simply no longer care about ‘Personal’ in the phrase Personal Computer.

Microsoft says: “You’re either on the bus or off the bus. If you’re off the bus, then you’re road-kill. So sorry.”

Please, tell me why I’m wrong.

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

3 users thanked author for this post.

HiFlyer, anita.yk, johnf

Reply | Quote

More new updates (on a Friday!):

March 23, 2018—KB4088881 (Preview of Monthly Rollup) (Windows 7)

Cumulative security update for Internet Explorer: March 23, 2018 (Windows 7)

Issue added to March 13, 2018—KB4088875 (Monthly Rollup) (Windows 7): “After you install this update, security settings in some organizations that are running Windows 7 SP1 or Windows Server 2008 R2 may prevent Internet Explorer 11 from starting because of an invalid SHA1 certificate.”

1 user thanked author for this post.

woody

Reply | Quote

So they finally rolled it out.

I don’t see any change in the status of 4088875 – still “Important” and unchecked on systems.

What’s really strange is that MS hasn’t fixed any of the bugs in 4088875, at least according to the bug list in 4088881.

Meh.

Reply | Quote

KB4088881 causes the same crashes as KB4088875/8 on Windows 2008 R2 Terminal Servers, alas

1 user thanked author for this post.

MrBrian

Reply | Quote

There is a note in both March 22, 2018—KB4088889 (OS Build 14393.2155) and March 22, 2018—KB4088891 (OS Build 15063.994) that those getting these updates from the Catalog need to install the new SSU (Servicing Stack Update) before installing the LCU (Latest Cumulative Update). I am guessing the reason is that the new SSUs fix this serious issue.

1 user thanked author for this post.

woody

Reply | Quote

So 4023057 is the reason Windows keeps re-enabling all the disabled services and tasks related to windows update and telemetry?

Every day it would reset them, no matter what I disabled within the scheduled tasks.  Even went as far as to start deleting the tasks, only for it to still be restored.

Wasn’t like this before.. Even uninstalled the update and still found things running again.  This time I outright deleted the telemetry services and update tasks.. seems to have held for 2 days.

Windows 10 is just absolutely absurd.  Disgusting that we’re forced to use it for proper software (and now hardware) compatibility.

1 user thanked author for this post.

johnf

Reply | Quote

Some days I laugh at Microsoft. Other days I fume with fervor.

If Windows 10 was like the Titanic, the bridge crew (e.g. Microsoft) would be running around attempting to plug all the sink and shower drains to prevent sea water from coming inside…while ignoring the enormous gash in the hull of the sinking ship.

Windows 10 is a metastasizing disease, and one day we won’t be able cut off enough to save the patient.

 

5 users thanked author for this post.

Norio, anita.yk, johnf, flackcatcher, Cybertooth

Reply | Quote

Patch for IE 11 fixes crash on Win 7
Internet Explorer Update KB4096040 (March 23, 2018)

Preview Rollup Update for Windows 7 with many issues

Windows 7: Preview Rollup Update KB4088881 (03/23/2018)

To me, it seems that Windows 7 and Windows Server 2008 R2 users /admins are guinea pigs for Microsoft.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

woody

Reply | Quote

Each month I hope that there’s going to be a solid reason to consider more seriously upgrading from Windows 7 to Windows 10 in or before January 2020, and that there will be less cause to consider retaining Windows 7 as a no-longer-supported OS beyond that date, yet each month I find myself even more disappointed than the month before, and certainly none the wiser.

For “disappointed”, also read “frustrated” – not to mention “annoyed”. Microsoft’s shenanigans these past months are simply beyond rational explanation.  Can they truly not have a clue how bad their reputation is these days, or is it simply that they don’t care any more?

I find the whole thing completely mystifying.

Thanks to Woody and the team for trying to direct some light into the innermost dark corners of Microsoft’s world, but I’m sure that even they are baffled as to what Microsoft’s motivation is these days. None of it makes the slightest sense!

2 users thanked author for this post.

anita.yk, Cybertooth

Reply | Quote

Thanks for this ROTFLMAO, Woody:  “When did Microsoft become the enemy?”  Haven’t seen a softball this sweet in a looong while!  But I won’t swing at it…  you and the lounge have better things to do, and so do I!

Reply | Quote

Are you using the stock “Windows Defender” security/AV app included with Windows 10, or some other 3rd party AV program? If so, which one? Any idea what might have deleted the QualityCompat registry key (other than KB4089848)?

Reply | Quote

Hi Capella, I know a couple of days latter you have likely fixed this to your satisfaction. I’ve seen this a couple of times now, and have wondered at the scenario involved. Chasing it through as a mental experiment, a machine with a brand new operating system has not yet been cleared by full scan of its resident antivirus, no matter first- or third-party origin. I wonder if that step had been done, then would the registry key have been reset again upon completion?

My thought being that in the protocol of establishing compliance, Microsoft would desire to satisfy several conditions: 1. the antivirus definitions include a specified set of signatures compliant to MS standards; 2. a successful scan with current definitions has been performed recently enough to be considered current by MS standards; 3. the publisher of the antivirus has pinky-sworn to behave by MS standards in the future; X. whatever else MS may require.

I believe that simply having a compliant application listed is insufficient. It needs to also be used as designed.

Reply | Quote