January 3, 2018 - KB4056897 (Security-only update) Windows 7

LevelBest said:

Anak, like you I had KB4056894 rather than 6897 and of the 10 updates, I left that one until last, having at that point created two system images. So it's now in my list of successfully installed updates. I spent a fair bit of time on the computer yesterday and all was well.

I don't blame you for running 6894 last I'd of done the same.

I don't mind being on my machine for a fair bit of time, if, I'm doing work or having fun, it's the maintenance part I don't relish like fixing somebody eles's (intel) screw-up, I end up with eye strain and getting a skull pain in 20". Well at least they and MS are offering fixes I just wish they were more transparent about it.

Hellriser said:

@Anak: I can report successful install of KB4056894. I followed your advice and installed MSE, it created the registry, forced check updates, KB4056894 and KB4055532 appeared, installed, uninstalled MSE, restarted the PC a few times during this process, everything seems to run OK.

The only difference I saw is that Windows takes an extra 1-1.5 seconds to start up.

Thank you very much for your time, you really helped me with this. Too bad I can't rep.

You should be okay then.
1.5 seconds doesn't sound too bad, what was the average total time to start before the update, 30seconds and now it's 31.5 seconds?

You're welcome, no problem with the rep it was my pleasure.

Update: KB4073578 Update to Fix Unbootable state for AMD devices in Windows 7 - Windows 7 Help Forums

Shawn, Thanks for the update!

antioch said:

Hi to all
On 10 Jan I checked for the January black Tuesday updates from MS. I was offered KB4056894[monthly roll-up which I hid] - KB 4055532 .NET [which I installed] and the MRT which I ran. On checking updates installed I found that another .NET had been installed - KB4054998 - Not installed by me though - not the first time?
I waited a couple of days to see if any further updates were offered - nothing to date.

Hi,

There has also been confusion with the .Net updates, I received 5002 and 4852. I can only attribute this to the different permutations that each of our machines have while yours are different than mine they are that way because your machine is different than mine.

antioch said:

Today I have come into the forum to get the latest 'black Tuesday' security update. I cannot see one but there is this thread started by Brink - dated Jan3
I have been reading through this thread but alas, by the time I got to the last page I am completely confused. Is this KB5056897 a release ahead of the normal monthly update?
Discussions in this thread refer to the recent/current Intel Security flaw. So does this MS Update KB5056897 have any connection with/include fixes etc for the Intel problem?

Yes, and yes. Look at Brinks presentations at Improvements and fixes both 6894 and 6897 deal with Kernel updates and that's where the "Meltdown" begins.

antioch said:

Hi to allBefore Xmas - I ran the Intel-SA-00086 Detection Tool - was informed my system was vulnerable. Following the instructions from Intel/Asus and my system builder I downloaded the Asus fix for my system - saved to flash drive and ran it in the Bios. I then downloaded and installed the ME Update Tool, re-ran the Intel detection tool and was informed that my system was no longer vulnerable.
So, should I install KB5056897 because I run Avast Free with which this update caused conflicts - not just to Intel but AMD processors?

There are two separate Intel problems. Your bios update took care of the Spectre side, and 6897 or 4 takes care of Meltdown. The Avast problem has calmed down and doesn't seem as prevalent as before. As long as you have the reg key set you should be okay.

antioch said:

Now there is a fix for this conflict but I have checked my registry and I have the RegKey as per the below links. I see that Brink is on top of the case and has just published the above bug fixes.
An update is available to fix the following issue that occurs after you install January 3, 2018—KB4056897 (Security-only update) or January 4, 2018—KB4056894 (Monthly Rollup) It would appear to me that if I choose to install the security only KB4056897 I will then have to install the fix as per the above? Though I am tempted to ignore 4056897 for a while as I have no wish to mess up what I have already done with a bios flash not have the hassle of a BSOD.
Rgds
Antioch

This situation is in flux for now and I don't expect it to resolve for at least another month or two if that, my suggestion would be to stick with what windows update sends you.

I'd stay away from the update Brink posted above for KB4073578 Update to Fix Unbootable state for AMD devices in Windows 7 if you haven't had the avast problem. Read the thread slowly.

Brink said:

Hey Peter, :)
Correct, but it would be a good idea to install this update if you have an AMD processor no matted if you had the issue.

• Do you have an AMD CPU in your machine?

• What is showing in your updates 6894 or 6897? Have you installed either?

Hi, and you're welcome,

I believe this intel mess has everyone confused, including me.

Double check on that BIOS flash, make sure it was for spectre, If you have the version number and where you D/L'd it (links for the bios and intel cpu) I can try to cross reference it against what your showing for your CPU in your system specs, many thanks for filling them out.

I stay with what windows updates (WU) offers me but it's a "different strokes for different folks" kind of thing, you go with what feels comfortable for you.

My pleasure,

Steve

Anak said:

I'd stay away from the update Brink posted above for KB4073578 Update to Fix Unbootable state for AMD devices in Windows 7 if you haven't had the avast problem. Read the thread slowly.

Brink said:

Hey Peter, :)

Correct, but it would be a good idea to install this update if you have an AMD processor no matted if you had the issue.

• Do you have an AMD CPU in your machine?

• What is showing in your updates 6894 or 6897? Have you installed either?

I had no issues with Avast Free AV.

Note:
My Destop machines have AMD Phenom II CPUs (they may have been immune to these update issues).

See these posts:
KB4073578 Update to Fix Unbootable state for AMD devices in Windows 7 (Post #2)
KB4073578 Update to Fix Unbootable state for AMD devices in Windows 7 (Post #4)

Hi antioch thanks, I'll look everything over and try to get back to you by your mid-evening. I have snow removal in the morning.

Thanks lehnerus I had seen where the avast problem was hit or miss, the same with AMD's. The main reason this problem is so confusing.