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

[Anak]

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". :shock: Well at least they and MS are offering fixes I just wish they were more transparent about it.

@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.

 

[Brink]

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

 

[Anak]

Shawn, Thanks for the update!

 

[antioch]

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.
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?
Before 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?
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

 

[Anak]

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.

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.

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.

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.

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?

 

[antioch]

Hi Anak
Many thanks for your post and clarifying matters I raised.
I was so confused I thought the Bios flash sorted Meltdown but there was currently nothing yet for Spectre.
My CPU is an Intel.
I hid 6894 the roll-up - I install the security only on black Tuesdays - it is never on offer so I get it from MS Catalogue each time. So neither have been installed yet.
I will install the security only 6897.

Many thanks again for your help
Antioch

 

[Anak]

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

 

[antioch]

Hi Anak


This is what I did regarding the Bios flash. Also I am not too sure if the flash was for Spectre or not - who would know?
1. Dll and installed the update for the Intel Management Tool - Windows 7 Link
2. Then I went to this link here for the ASUS H110M-R 3405.CAP which I unzipped and copied to a flash drive.
3. Then I restarted the computer hitting F2 which opened the Bios EZ Mode - pressed Advanced Mode then Tools.
4. I selected the update Bios Flash drive then the .CAP file and proceeded. Less than a minute later the process finished and I exited the Bios saving changes.
5. I then went to this link http://dropcanvas.com/s2lha unzipped the contents and ran the MEUpdate Tool.
I then watched out for an update from Avast which did arrive and after the update I checked the registry to see if the entries were there - Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc" - Type="REG_DWORD”
Data="0x00000000”
They are present as per the above January 3, 2018—KB4056897 (Security-only update)

I hope the above is what you require - let me know if not.
Thanks for doing this.
Rgds
Antioch

 

[lehnerus2000]

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.

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)

 

[Anak]

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.

 

[Seffrid]

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
KB4073578 Update to Fix Unbootable state for AMD devices in Windows 7

Have you tried installing KB4056894 yet? My main desktop has the same processor as you so I'd be interested to know how you got on. I'm leaving well alone for the moment, and the other update for .Net Framework (KB4055532) is unchecked so shouldn't be installed at the moment anyway.

 

[Anak]

Hi antioch,

How do you know?

• Intel and the OEM's are handling spectre.

• MS and WU are handling meltdown.

I looked over your files and links and the only thing I can see is the version doesn't match, you're showing 3405 when on the asus site I see 3601, scroll down a bit to see your MB. I wouldn't be too concerned though, this situation is pretty fluid and even in the past 10days version numbers are bound to change.

FOR THE MOST UP TO DATE INFORMATION, PLEASE REMAIN CURRENT WITH UPDATES AND ADVISORIES FROM ASUS REGARDING YOUR EQUIPMENT AND SOFTWARE. THE INFORMATION PROVIDED IN THIS ADVISORY IS PROVIDED ON AS “AS IS” BASIS WITHOUT ANY WARRANTY OR GUARANTEE OF ANY KIND. ASUS RESERVES THE RIGHT TO CHANGE OR UPDATE THIS ADVISORY AT ANY TIME WITHOUT NOTICE.
asus site

Just keep checking this won't calm down for awhile:

Forget about planning just for Patch Tuesday, the second Tuesday of every month when Microsoft issues security updates to Windows users. As companies scramble to mitigate Meltdown and Spectre, you should be planning for Patch January, and maybe February as well. Case in point, ASUS, Gigabyte, and MSI have all now released firmware updates for a whole bunch of motherboard models.

https://hothardware.com/news/asus-gigabyte-msi-spectre-meltdown-exploits-motherboard-bios-updates

You look good to go if you haven't installed 6897 already.

 

[lehnerus2000]

Monthly Security-Only Updates

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.

I manually download/install the W7 Monthly Security-Only Updates these days (usually after Brink has posted the links).

Have you tried installing KB4056894 yet? My main desktop has the same processor as you so I'd be interested to know how you got on. I'm leaving well alone for the moment, and the other update for .Net Framework (KB4055532) is unchecked so shouldn't be installed at the moment anyway.

It seems that the auto-title retrieval function screwed up the links.
They work in Preview mode but they break once they are Posted.

KB4073578 Update to Fix Unbootable state for AMD devices in Windows 7 (Post #2)

No I didn't install KB4056894.

I installed KB4056897 (Security-Only Update) & KB4073578.

KB4073578 Update to Fix Unbootable state for AMD devices in Windows 7 (Post #4)


You can get a nifty GUI tool from Gibson Research Corporation to check your PCs for Meltdown and Spectre.
Here is a gHacks article:
https://www.ghacks.net/2018/01/16/gibson-releases-inspectre-vulnerability-and-performance-checker
Download:
https://www.grc.com/inspectre.htm

 

[antioch]

I had no issues with Avast Free AV.

Since updating security only[yes I only do that one on black Tuesdays] with 6897 and after restart and normal start, I now have a series of error events all related to Avast - trying to get that sorted - I may have to uninstall 6897 or do system restore. On the restart it took ages to reconfigure - over 5 minutes - never had that on previous months updates.

 

[antioch]

Hi antioch,

You look good to go if you haven't installed 6897 already.

I don't think I was 'good to go'

See my reply to lehnerus - also after restart I went back to check for any further updates and was offered KB4055532 which I had installed on 14.01.18 along with the other .Net 4054998 which was not on offer and I did not install?? So I am about to flip a coin - heads I uninstall 6897 and reinstall or tails do a system restore.
When I was on XP it was easy to get the update log files to check if install failed - where are they in WIN7?

I hope to get some sense/answers from Avast once I have finished searching their forum.

Hope to update soon.

 

[Anak]

Sorry to hear you had problems it, looked okay, avast was updated and the key was set. If you don't get anything solid from the avast forum I've seen where users had success:

• Using the avast uninstall utility.

• Install 6897.

• reinstall avast.

System restore should remove those avast errors.

The update log files are at: C:\Windows\Logs\CBS For more info see #4 Log Collection: Windows Update Posting Instructions Sometimes you'll see a checksur file, that is created when you run the SURT tool in #1.

This may interest you: Windows Update Manifests - Manually Trace Through Registry

 

[antioch]

Hi Anak
I left 6897 for the time being - but got rid of the .Net which was for Servers only?
Uninstalled - re-installed updated Avast - all seems OK -quality compat is still in the reg.
No errors - have been switching on and off.
Didn't need to do system restore. I have had no further offers of updates - thank goodness.

I looked at the Logs - not user friendly - I could not even spot the KB number - saw a lot of references to AMD64????

Is #4 Log Collection, the 4th folder under CBS @ #1? - no sign of it - a search didn't locate it either.

I am away for the weekend - will give the computer a rest.
Many thanks for your continued help.

Rgds
Antioch

 

[lehnerus2000]

Weird

I had no issues with Avast Free AV.

Since updating security only[yes I only do that one on black Tuesdays] with 6897 and after restart and normal start, I now have a series of error events all related to Avast - trying to get that sorted - I may have to uninstall 6897 or do system restore. On the restart it took ages to reconfigure - over 5 minutes - never had that on previous months updates.

My Event Viewer seems to be displaying the normal warnings.

I did have a couple of BSODs the other day, but I'm sure that was related to a different piece of software (it's caused issues in the past).
A couple of BSODs every few months is an acceptable trade-off for receiving $20/month.

Your issue must be due to the combination of hardware/software on your PC (same as the users who claim Firefox crashes constantly on their systems).

Did MS re-release the Monthly patches (KB4056897 & KB4056894) after the AMD issue was reported?
I deleted the original downloads when I read there were problems and I downloaded a new copy of KB4056897 before I tried installing it.

 

[Brds7t7]

Did MS re-release the Monthly patches (KB4056897 & KB4056894) after the AMD issue was reported?
I deleted the original downloads when I read there were problems and I downloaded a new copy of KB4056897 before I tried installing it.

I haven't seen any mention of either being reissued yet. I just had a look on the Update Catalog and it's still listed as 4th January release date.

So, it's still on my waiting list!

Microsoft Update Catalog

 

[Anak]

My answers are at the bullets.

Hi Anak
I left 6897 for the time being - but got rid of the .Net which was for Servers only?

• Re-read the title it should say, for Windows 7 SP1 and Windows Server 2008 R2 SP1.

Uninstalled - re-installed updated Avast - all seems OK -quality compat is still in the reg.
No errors - have been switching on and off.
Didn't need to do system restore. I have had no further offers of updates - thank goodness.

I looked at the Logs - not user friendly - I could not even spot the KB number - saw a lot of references to AMD64????

• You're right, it's not. It takes a lot of experience to know what looks out of place. This thread may offer insight: How to analyse the CBS.log There are some attachment pix that aren't showing because it is an old thread and I believe the forum team goes through threads that are a year or two old in order to lighten the load on the server.

• What is AMD64? AMD64 is just a reference to AMD's help in building the 64bit architecture.

Is #4 Log Collection, the 4th folder under CBS @ #1? - no sign of it - a search didn't locate it either.

• My apologies I misspoke. No, #4 Log Collection was just a reference for more info at #4 in the Windows Update Posting Instructions tutorial.

I am away for the weekend - will give the computer a rest.
Many thanks for your continued help.

Rgds
Antioch

• You're welcome and enjoy your break!