OUt-of out-of band patches for Win10 1709, 1703 and 1607

Topic

New Reply

Just a heads-up. We’ll have more later. KB 4089848 brings 1709 up to Build 16299.334 – seems to have fixed the problem with the January Delta update K
[See the full post at: OUt-of out-of band patches for Win10 1709, 1703 and 1607]

1 user thanked author for this post.

MrBrian

Reply | Quote

Replies

I imagine that like always, we will have to wait for the MSDEFCON-Level to change, and I guess for those that need urgently to update will wait for Miss.Susan guidance.

I dont like the fact that we have two updates for month. what is Microsoft doing?

 

Just someone who don't want Windows to mess with its computer.

1 user thanked author for this post.

woody

Reply | Quote

For those on Windows 10 and derived server versions, note that those patches are called previews on previous versions of Windows! If there is no urgent need to install, just wait for the next Patch Tuesday.

Reply | Quote

Does the KB4088889 Cumulative Update supersede the KB4088787 Cumulative Update for us 1607 laggards, and should we install ONLY KB4088889 when Woody flips the MS-DEFCON 3 switch for March, and forget about KB4088787? Also, about the Servicing Stack KB4089510, should we install it in March, or hold off until April, since it’s a March out-of band patch?

I’m asking ’cause I’m now going to have to do all of my updating by downloading everything from the Microsoft Update Catalog and manually installing each update, at least for the next couple of months. I’ve never done that before. Now, however, if MS even gets a whiff that my computers are connected to the Windows Update Service, up pops the danged Windows 10 Update Assistant and away goes the upgrade to 1709. I’m not ready to upgrade just yet.

Reply | Quote

“Does the KB4088889 Cumulative Update supersede the KB4088787 Cumulative Update for us 1607 laggards”

Yes. See Package Details tab at https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=c4fe9ff8-acd4-405b-91b5-334daf81ae00.

“[…]  if MS even gets a whiff that my computers are connected to the Windows Update Service, up pops the danged Windows 10 Update Assistant and away goes the upgrade to 1709.”

This probably can be stopped by using the Image File Execution Options debugger method that I mentioned previously on updateassistant.exe. I haven’t tested this yet but I will soon.

1 user thanked author for this post.

dononline

Reply | Quote

KB 4089848 disabled Start Menu, Notification Centre and Settings Menu.  After rollback all enabled again.

1 user thanked author for this post.

woody

Reply | Quote

and people want to convice us to install 1709….what a joke.

Just someone who don't want Windows to mess with its computer.

1 user thanked author for this post.

Cybertooth

Reply | Quote

When you say “disabled” — what does that mean?

Reply | Quote

I apologize for not being clear.  I simply meant that access to Start, Notifications and Settings  was not ‘clickable’.  The only way to open Settings was through Win + X shortcut.  After removing the update, all functions were restored.

1 user thanked author for this post.

woody

Reply | Quote

I think that an update should be considered “out-of band” only if it contains new security fixes and isn’t shipped on a Patch Tuesday (the second Tuesday of each month).

Reply | Quote

You have a point. What of fixes to old security patches?

Reply | Quote

I guess it’s all semantics anyway, but I wouldn’t consider that an out-of-band update either. As you’ve mentioned, it’s not unusual for Microsoft in recent times to ship non-security-related updates on any day of the week except perhaps Saturday or Sunday.

Reply | Quote

Same thing happened to me. Start menu, notifications, etc no longer working. Except when I uninstall the update it reinstalls itself on reboot even when being disconnected from the internet & with updates deferred. Any way to fix it?

Reply | Quote

Just for the record: I am not offered KB 4089848 on my PC

Reply | Quote

I am not offered KB 4089848 on my PC either

Reply | Quote

…but decided to give it a go anyway (via manual download) – and all seems good so far

(one must be really bored on Friday evening!)

Reply | Quote

I see that my qualitycompat key has also been deleted after moving to 1709. Is there a way to get it back without editing the registry manually?

Reply | Quote

Thanks for the reply. I’m only using Defender as AV, so hopefully MS will hear about this issue and reset it via a Defender update. I’m not in any rush.

Reply | Quote

@Seattle27 & Capella:

See “GoneToPlaid”‘s post at https://www.askwoody.com/forums/topic/scan-for-meltdown-and-spectre-with-steve-gibsons-new-inspectre-utility/#post-159881

He discusses the registry entry, and attached a zip file with the registry data in it. That file can be directly imported into the registry after extracting it from the zip file and then double-clicking on the .REG file.

The attachment is down at the bottom of his post, is listed in sort of small print, so you’ll have to look closely.

I downloaded the zip file and checked it, it is the correct entries to re-create the QualityCompat registry entry.

1 user thanked author for this post.

Seattle27

Reply | Quote