Cumulative Update KB4056892 Windows 10 v1709 Build 16299.192

I got it to trigger in WU!

Avira users, you need to make sure you're on 15.0.34.17; after updating Avira to .17, it will create the required Registry keys. I was on 15.0.34.16 as of this morning, but forcing Avira to check for updates prompted the .17 update which did take ~5 minutes to install on an i5-8600K / 250GB 960 EVO / 16GB RAM system.

After you get the .17 update, it will create the required Registry keys. I did not have the keys before the Avira update; immediately after the update, the keys were automatically made properly.

So, PSA: update your antivirus. It must create the new Registry keys and most AV are just updating today, or maybe not even yet. Only after those keys are present, apparently, will you be offered the WU prompt. And this makes sense: without the Registry keys, the fix actually does not activate, per MS's article.

I'm off to reboot and begin this long journey of chipocalypse.

kado897 said:

Have you read the notes at the beginning of the thread?

Yes - No magic Anti-Virus here - Defender.

jrolson said:

If you run a third party antivirus you may not get the update until the antivirus is updated.

Source,
http://www.zdnet.com/google-amp/arti...our-antivirus/

Haha, ninja'd! I just discovered this. And I think this is a critical point as apparently these pre-updated AVs can cause BSODs:

"Microsoft's testing revealed a "small number" of antivirus programs are making unsupported calls into Windows kernel memory, which result in blue screen of death (BSOD) errors. To avoid causing widespread BSOD problems Microsoft opted to only push its January 3 security updates to devices running antivirus from firms that have confirmed their software is compatible."

storageman said:

Yes - No magic Anti-Virus here - Defender.

Eh, isn't your issue one of the "Known issues" for this update? See the first post; it's got a list of workaround instructions.

no1yak said:

Here's a screen shot of the KB that was installed at the same time as 4056892



Attachment 170862

This KB4058702 apparently is freshly baked and out of the oven. It has to do with some serious security vulnerability speculation on some Intel CPUs. All that I am saying is that I didn't get it, meaning I am probably not concerned. I will trust MS on this one. If you got it and it installed successfully, that's a good sign and you are good to go. Like you said, there is not much detailed information about this critical update..:)

Josey Wales said:

That happened to me and then it BSOD'd and when I restarted the Update was in a loop. I reset WU but that did not help. I restored 15063 and deleted the image of the FCU.

Yup. It's most likely your AV. I suggest checking if your AV is compatible with these kernel upgrades; see my previous few posts.

Can the OP please add this very important disclaimer?

If your AV has not been patched:

You risk BSODs and bootlooping your system.
You didn't even get patched. MS will not activate the Meltdown/Spectre fixes until your AV has been patched.

This patch does nothing unless your AV has also been patched.


Brink, I highly recommend add the disclaimer above or something to that effect so that people actually know whether they have been patched.

Simply installing this KB does not actually offer any protection. Even worse, it might cause BSODs and bootloops.