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

[Seffrid]

All the troublesome Meltdown patches have today been pulled by Microsoft in respect of what they describe as (but do not define) all devices with impacted AMD processors. Needless to say, they're blaming AMD for the mess despite having themselves tried to patch AMD machines when the Meltdown threat only significantly affects Intel machines.

 

[Nitesco]

I still have not installed this update.

I've seen on the news this morning that intel processors are at risk from the Meltdown issue but patches/updates (?) are being issued for intel processors that are up to five years old. My trusty laptop is 6 years plus old.

Then there's the issue of whether McAfee have released the update for the registry part.

I don't know whether to install this update or not, even if I do, will it protect my laptop and now given this latest intel issue, whether it could potentially wreck my laptop.

Can anyone help?

LevelBest

I'm holding off on updating for the same reasons. I have an older Intel CPU, but for the amount of issues that I've seen happen with other CPUs, I'm waiting for more details and possibly another updated patch before I go any further. More so after spotting this news with some Windows 7 users getting BSODs as a result of the 2018-01 Monthly Rollup: Buggy Win7 Meltdown patch KB 4056894 throwing blue screens | Computerworld

In any case, I'm definitely keeping a close eye on any news with this issue.

 

[LevelBest]

Thanks, at least I'm not the only one. That link is really concerning with the number of people affected. I think the main problem is that there are several different issues/fixes needed; Microsoft, anti-virus software and processors with Microsoft putting out an update without knowing whether the anti-virus is ready for the update.

How does the processor get fixed (for those that have processors that are five years old or less)? Does than come via a windows update or a software update in the background or do users have to update themselves? Also, what of the peeps who have processors that are more than five years old. I've seen no references as to what they're supposed to do.

I'm going to hang fire until I see how this pans out.

LevelBest

 

[Brds7t7]

Thanks, at least I'm not the only one. That link is really concerning with the number of people affected. I think the main problem is that there are several different issues/fixes needed; Microsoft, anti-virus software and processors with Microsoft putting out an update without knowing whether the anti-virus is ready for the update.

How does the processor get fixed (for those that have processors that are five years old or less)? Does than come via a windows update or a software update in the background or do users have to update themselves? Also, what of the peeps who have processors that are more than five years old. I've seen no references as to what they're supposed to do.

I'm going to hang fire until I see how this pans out.

LevelBest

If it's one of the processors that Intel has promised to fix then I think it'll most likely be a firmware/BIOS update needed, along with Windows update. Keep an eye out on both Intel and the manufacturer of your PC/Board.

If it's an older CPU - then you'll have to just rely on the software updates to patch it.

The ideal solution would be both BIOS and software updates, but if that isn't an option the software update should be enough.

 

[Riley7]

I think I read something here that stated the January security only update does not include patches for the meltdown issue. Only the monthly rollup has them.
Do I understand this correctly?

This Intel security issue has me confused. I run a core2 duo from 2009 and doubt there will be an update from Intel for it.

Any comments appreciated.

 

[Brds7t7]

The Security fixes in the rollups should be the same as the Security-only update - that's how it's been for every previous month's updates. They've always included the same security fixes, just the rollups have other fixes or added "features" included in the patches.

 

[lehnerus2000]

All the troublesome Meltdown patches have today been pulled by Microsoft in respect of what they describe as (but do not define) all devices with impacted AMD processors. Needless to say, they're blaming AMD for the mess despite having themselves tried to patch AMD machines when the Meltdown threat only significantly affects Intel machines.

Someone has to protect poor defenceless Intel.

A generic question about pulled patches.
If MS pulls a patch, should users uninstall the patch, even if is not causing issues?

 

[Anak]

I wouldn't.

Searching your question (google): If MS pulls a patch, should users uninstall the patch, even if is not causing issues? comes with different answers. Usually MS will announce either publicly or at the beginning of the patch process whether or not you should uninstall before applying a corrected version of the same update/patch.

The ones I'd have some concern about are the ones that D/L'd the standalone patch through the update catalog but if MS is up to speed that scenario should also be covered by an installer that checks your logs and if it finds an older version of itself it should/would be removed before the updating.
The same goes for doing the patch through Win Updates, but in this day and age of computing it seems that all bets are off and the best defense is to remain vigilant.

 

[ethel]

Hi Everyone, Today I have been offered the Windows Malicious Software Removal Tool x 64 January 2018
(KB890830) and it is the only update Microsoft has offered, it downloaded and installed, but when I open
it, it does not run. I am using Panda Free Antivirus, I have a key under Quality Compat, but it only looks
like part of the key. I normally install the Quality Monthly Rollups but it does not look like it is being offered
this month.

 

[Anak]

Hi ethel,

When you installed the MSRT (Malicious Software Removal Tool) did you notice that it took awhile to finish and close out windows updates? If it did that indicates that it ran; The MSRT will automatically run after installation without any intervention from the user, and it's designed to purge itself after running.
I'm close to doing my updates and I'll post back on how it went.



According to this site Panda was supposed to have the key ready on the 9th scroll down a bit to see panda on the left and it looks like they did by your screen shot. In all the posts I've seen that key never describes what AV set it, it is enough to know that it is there. You can also check the link to panda on the far right for more.

To check the name go back to the key and do you see the faint vertical line?


Place your cursor over it until it changes to this then double click to expand the column, that should enable you to view the whole name. That column line can also be expanded by click/and hold then drag to the right to expand.

I haven't seen any mention of the QMR (Quality Monthly Rollups). MS has been so busy getting the out of band update on the 3rd ready they may forgo the QMR. Because of the Intel situation I wouldn't doubt IMHO that updates will be in a state of turmoil for at least another couple of months.

 

[BlueGuy]

Well, just did it with my x86 system. No BSOD, but as Anak said, it was an unusually long reboot. Despite being a geek since 1980, my heart attack, surgery and long recovery has really frelled up my wetware.
This old brain just not as acute in solving mysteries as it once was, which is why in 2013 I gave up hacking and splicing 2000 Pro, with kernel mods and the like, as the gang at MSFN are still doing.

You all made me frelling nervous about this update. This CPU used to be a Sempron 145, but when I decided not to install my second legacy MyHD MDP-130 tv tuner and capture card, I used the ASUS utility to unlock the other cores, making it an Athlon series. Instead keeping it to run in another XP HTPC.

I wasn't presented with any update on the third, just this morning at 03:32 Eastern Standard.
So far, so good, no need apparently to use the restore point, I might actually be glad when 2020 gets here, then it will be MY responsibility to keep this machine secure, but I'd like to build my first x64 machine to try out Poser and Blender, not necessary for now, as my spheres and cylinders are quite crude and need practice.

With my Ataris it was Motorola, and I didn't have to worry about CPU flaws, flawed CPUs were simply junked. Then Intels became too expensive for my budget, so moved to AMD. I'm getting way off topic, as I tend to do. Basically, I had no problems with this Patch Tuesday and glad to see everyone else getting through also.

 

[Hellriser]

I haven't seen any mention of the QMR (Quality Monthly Rollups). MS has been so busy getting the out of band update on the 3rd ready they may forgo the QMR. Because of the Intel situation I wouldn't doubt IMHO that updates will be in a state of turmoil for at least another couple of months.

So the January 2018 SQMR (Security Quality Monthly Rollup) hasn't rolled out yet? Because nothing has appeared on my up update window except the .Net Framework one. And I'm a bit reluctant to install the out-of-band patch.

 

[Brds7t7]

So the January 2018 SQMR (Security Quality Monthly Rollup) hasn't rolled out yet? Because nothing has appeared on my up update window except the .Net Framework one. And I'm a bit reluctant to install the out-of-band patch.

The monthly rollup did show up on all my systems yesterday, mine are all Intel CPUs though. Not sure if it's been pulled since then as I haven't been home to check. Are you using an AMD processor?

 

[Anak]

So the January 2018 SQMR (Security Quality Monthly Rollup) hasn't rolled out yet?

Yes it has, I'm taking the out of band update on the 3rd as the SQMR, see post #1

Improvements and fixes

This security update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Security updates to Microsoft Graphics Component, Windows Graphics, Windows Kernel, and Windows SMB Server.

For more information about the resolved security vulnerabilities, see the Security Update Guide.

~~~ ~~~ ~~~

Because nothing has appeared on my up update window except the .Net Framework one. And I'm a bit reluctant to install the out-of-band patch.

On occasion this has happened to me; I've seen an update but didn't have the time to install it. Then when I did, it was pulled and I waited until MS was happy with it and re-offered it to me. I would believe you never saw one because it didn't get around to your regional area when MS decided to "pull it". I believe you'll see it once things calm down.
The reason MS pulled it is because there was so much confusion if users of AMD CPU's were affected by Meltdown and when they did install it they were having problems so MS wants to refine the update for them. There'll be a delay even though you show an Intel CPU in your specs. So remain vigilant, don't be surprised if you see another "out of band" update before February.

• The only caveat that I know of for installing the Jan. 3rd update is that, that QualityCompat key needs to be set by your AV as related to in my post #10. You could check This List to see if yours has, I would have for you but you don't have it listed in your specs.

Did you only get one .net update or two like I show in post #50?

~~~ ~~~ ~~~

This is at the bottom of "Known Issues" for the Jan. 8th 2018 Monthly Rollup: This KB only Applies to: Windows 8.1, Windows Server 2012 R2 Standard

Microsoft has reports of some customers with AMD devices getting into an unbootable state after installing this KB. To prevent this issue, Microsoft will temporarily pause Windows OS updates to devices with impacted AMD processors at this time.

Microsoft is working with AMD to resolve this issue and resume Windows OS security updates to the affected AMD devices via Windows Update and WSUS as soon as possible. If you have experienced an unbootable state or for more information see KB4073707. For AMD specific information please contact AMD.

And this in turn has slowed updates for everyone.

 

[LevelBest]

Is AMD the same as Intel? According to my computer I have an Intel Pentium P6200 processor. Purchased the laptop in autumn 2011, so it's over 6 years old. So is possible that if I download this update, it will slow down the whole computer if it escapes the BSOD?

From what I've read on the news, no one has reported being affected by the meltdown or spectre bug.

I've just been through 3 months of issues with my SP which has resulted in me moving to fibre, so I only just caught up with AV and windows updates, done some maintenance on the computer and it's just a relief to get back to normal. Last thing I want is to have more problems by downloading this update.

LevelBest

 

[BlueGuy]

Has anybody posted this?

https://www.amd.com/en/corporate/speculative-execution

 

[Anak]

No, AMD is not the same as Intel.

• You're confusing the two intel problems, this update will patch the meltdown problem. Do yourself a favor and search for: meltdown, spectre, and read, read, read.

• The specter problem is what you're thinking will slow down a machine and you might not be updated with a 6year old machine. I have a 7year old gateway that I seriously doubt acer will touch, they do have 4 gateway machines on their list but not mine. As of my posting the spectre patch has to be delivered by your OEM in your case samsung. I'm using my gateway on-board updater to see if it's available.

• There are slowdowns but they are negligible with the spectre update, it depends on what you use your machine for, do you use any intensive programs like photoshop or database work that have multiple files open?

• There are some intel users that have experienced hangs with the meltdown update, and BSOD's and bricking with the spectre update.

• If you mean affected by hacker exploits, that may be true for now but give the blackhats some more time to figure it out and they will be knocking on your door.

• If you mean affected as in these intel cpu's aren't vulnerable then you should get a better news source.

• I went over this with you back in my post #10, if you have the qualitytcompat key and it is set as shown you should be okay.

BlueGuy: I've seen it, but there's so much posted between z3r010's forums I'm not sure if it has, but you took care of it here...

 

[Nitesco]

So I've got three updates for Windows Update. The most recent update is highlighted in this screenshot.

What's the status on KB4055532? Is it safe to install? I want to be really sure before I go ahead with any updates regarding Meltdown and Spectre.

 

[Brds7t7]

So I've got three updates for Windows Update. The most recent update is highlighted in this screenshot.

What's the status on KB4055532? Is it safe to install? I want to be really sure before I go ahead with any updates regarding Meltdown and Spectre.

Can't speak for your system, but I've installed the .NET Framework update with no issues at all. I can't recall ever having an issue with any .NET Framework update I've installed to be honest.

Just make sure you keep regular system images in case any update does screw anything up.

 

[Nitesco]

Can't speak for your system, but I've installed the .NET Framework update with no issues at all. I can't recall ever having an issue with any .NET Framework update I've installed to be honest.

Just make sure you keep regular system images in case any update does screw anything up.

Making a system image is a good idea. I installed Macrium just for that when I dealt with Windows 10 and had to restore my Windows 7 image because of how badly Windows 10 performed on my system.

Only problem is that I don't have the space to make an image of my Windows drive at the moment. 637 GB used on a 1TB drive. But I can't hold off on these updates forever, so I'll wait for some more clear signs that they don't break anything.