Windows 10: Cumulative Update KB4089848 Windows 10 v1709 Build 16299.334 - Mar. 22

This is the second cumulative update that has not been picked up by Windows Update despite the fact that I am an Insider and have manually checked updates - I am told that everything is up to date. Yet I downloaded this update from the link and it is proceeding to install after first requesting if I wanted to.

Previous cumulative updates prior to 16299.309 have always installed on release so why haven't these? Have Microsoft changed the way they roll out these updates? I am in the U.K.

 

One of the machines that did not get the WU, the key is not missing.
There is no error message, no 3rd party A/V installed.
It just keeps saying "Up-to-Date".
Did not have this problem with previous WU (...309).
Therefore, it is something else.

 

Just like you I only have WD and MBAM and at some point in the past I had the registry key (QualityCompact) and its values in the right pane, but it is not there anymore. I was not the one to remove it. I suppose Microsoft did.
Unlike you, I had to download this update from Microsoft Update Catalog in order to install it. This is really getting confusing and is like a cat and mouse game. Microsoft has got to get its act together. Do we need this key or we don't?.
As of this writing, my machine is still without this key, but I am at OS Build version: 16299.334.

 

Two of my PCs did not detect this update, two did. So I manually did it with no problems. Maybe they like to spread updates around a little at a time.

 

Two days later on the East Coast, WU throws an unknown feature update and to make you laugh, KB4088776=*309 with no restart.

Still at *309 and we don't have a good feeling for the catalog. Yes, we tried the troubleshooter twice in 2 days. No, we don't have the mysterious key and Defender's alone.

As usual, we don't any bugs and we won't force this one.

 

But but but...

https://support.microsoft.com/en-gb/...virus-software

Q2: What is Microsoft doing to help mitigate issues caused by these unsupported applications?
A2: To help protect our customers from "blue screen" errors and unknown scenarios, Microsoft is requiring all antivirus software vendors to attest to the compatibility of their applications by setting a Windows registry key.

OK, but:


Q3: How long will Microsoft require setting a registry key to receive the Windows security updates?

A3: As of March 13, 2018 Microsoft is lifting the AV compatibility check for the March 2018 Windows security updates for supported Windows 10 devices via Windows Update. We continue to require that AV software is compatible and in cases where there are known issues of AV driver compatibility, we will block those devices from receiving Windows updates to avoid any issues. Microsoft will continue to enforce this requirement for older versions of Windows until there is high confidence that the majority of customers will not encounter device crashes after installing the Windows security updates.

Oh dear...

 

After working this issue for a few weeks here is what I found.

One system running Norton Security will set the key after a main SDS definition update.

Second system with Windows Defender would also set the key after a definition update. Today I found that it is not setting the key anymore. MS must of changed it.

Neither system will offer cumulative updates without the key being set.

Both systems run Windows 10 1709 fully updated so I don't try and understand MS intentions and just set the key if it is missing and it works for me.

Here is a reg file to set the key if anyone needs it.

 

Thanks for help, but the file does not open. Could you please paste the content so that we can do it manually.

Edit: The given method in post #58 doesn't work here.

 

Here is a screen shot of the file....opened.

 

I ran updates on all four of the AV packages I have installed (MBAM,Spybot S&D, NIS, and MSERT). NIS is the only one active. After the MSERT update, WU automatically ran a search for updates and found none. System is still at .309. I looked at the reg key listed above and the data value was 0. I ran PhoneMan's reg key and the above listed reg key still shows a data value of 0, but WU is downloading the update. Be afraid, be very afraid. Thank goodness I have a System Image from right after .309. 15 minutes later, the system is at bld. 16299.334. Now I have just enough time to do another system image save before next week's cumulative update is released.

 

How did you try to open it. If your right click under Open With it should default to Registry Editor. On my system I use a double left click and Registry Editor will open. I am getting a unsigned warning. I downloaded the reg file from Bleeping Computer from this article. Scroll down and it is right above the RED Warning banner.

https://www.bleepingcomputer.com/new...tre-cpu-flaws/

Jim *Cool

 

Yea, this quality compatibility by Microsoft on this issue appears a bit confused in implementation on their part. You are at 334 without the key being present. I did not have the key and the KB update would not install or even be seen by Windows Update. All is well now with this machine but many will not get things right, especially if they don't seek help like that found in this thread. We'll see going forward if this continues to plague folks with Windows Update and as you say, "do we need this key or we don't?"

 

The machine didn't like it at all. CPU Fan went crazy, lost internet and the network switch after reboot. Shutdown to stop the fan from running at high speed after deleting the key.

Is that key usually there (QualityCompat)?

Got it from the catalog and no issues. Same as usual for a 700+MB file, about 10 minutes. QualityCompat still not there

 

I haven't been offered this update yet on any of my 3 PCs running v1709 Build 16299.309. I wonder why not?

 

I had the same issue and found the QualityCompat reg key mentioned in earlier posts which I definitely had before had been deleted. I'm not sure whether it was a previous Windows update or Malwarebytes update which did this.

I added the reg key back and KB4089848 started downloading immediately when I checked for updated in Windows Update.

Judging by the number of people reporting the same issue I think Microsoft screwed up big time when they released KB4089848. Windows Update is clearly still checking for the existence of the QualityCompat reg key which they now say is no longer required.