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

The update was not successfully installed as below. Tried twice. Never had this happen before.

I did the Registry Editor key and Windows Update found and installed the KB. This should not be necessary as I have only Windows Defender and MBAM installed which is supposed to be compatible.

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.

wordsworth said:

I did the Registry Editor key and Windows Update found and installed the KB. This should not be necessary as I have only Windows Defender and MBAM installed which is supposed to be compatible.

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.