Thanks Woody.

Even if MS only have a couple of QA testers left, you’d think one of them would have tried the update on an AMD machine, wouldn’t you!

via Windows Update KB 4056894 + Microsoft Windows 7 Ultimate Service Pack 1 6.1.7601.23915 (Win7 RTM) + DualCore AMD Athlon 64 X2, 2600 MHz (13 x 200) 5000+ = BSOD 0x000000C4

1 user thanked author for this post.

woody

“Important: Windows security updates released January 3, 2018, and antivirus software” in “https://support.microsoft.com/en-us/help/4072699/important-january-3-2018-windows-security-updates-and-antivirus-softwa”

Microsoft’s KB patch (for a kernel bug not relevant to AMD CPUs) definitely has been killing Win OS powered by AMD CPUs …

Intel-Meltdown Bug Patch – Hall of (Additional) Latest Casualities
(as of: 06 Jan 2018, 02:15 UTC)

At MS TechNet:

• Win 7 Pro x64 + AMD Athlon 64 x2 Dual Core 4800+ CPU + WSUS: BSOD
• Win 7 x64 + AMD Athlon 64 x2 Dual Core + WSUS + Norton AntiVirus: BSOD

At Microsoft Answers:

• Win 7 x64 + AMD Opteron 285 Dual Core + WSUS: BSOD
• Win 7 Ultimate x64 + AMD Athlon X2 6000+ Dual Core CPU + ESET NOD32 Endpoint Antivirus v6.6.2052.0: BSOD
• Win OS + Intel CPUs: rebooted w/o problems
• Win Server 2008 R2 + AMD Operton Dual Core: BSOD
• Win OS + AMD Athlon 64 Dual Core 4600+: BSOD

Also said to be affected by BSOD:

• AMD Athlon X2 4800+
• AMD Athlon X2 4600+
• AMD Athlon X2 BE-2400
• AMD Turion X

At OverClockers UK:

• Win Server 2008 R2 x64 + AMD Operton Dual Core CPU + WSUS: BSOD
• Win Server 2008 R2 x64 + Intel Xeon CPU + WSUS: rebooted w/o problems

3 users thanked author for this post.

HiFlyer,

AJNorth,

woody

I installed the security only update for W7/32 and had no problem. Not sure if that means that the BSODs are being caused by something in the non-security portion of the monthly rollup. My gut says no – kernel updates can be fickle.

I just noticed that the monthly rollup for W8.1 has just been released as V2. Odd.

Correction: that should be security only update for W8.1 (my mistake).

All of this sounds like a “super bork” by Microsoft. Yet of course everyone knows that MS is in bed with Intel. This weekend, I will see what happens on my Win7 machines which have both AMD and older Intel CPUs, after performing incremental backups of the OS hard drives and then installing the January update. Note that my AV program is compatible as long as I manually set the required registry key. Thus whatever happens after that will potentially be a riot of fun.

Note that I will not test the Monthly Rollup, KB 4056894. Instead I will test the KB4056897 (Security-only update).

Whatever happens is whatever happens. Yet from the above, I am not too optimistic.

• This reply was modified 1 year ago by
  
   GoneToPlaid.

3 users thanked author for this post.

SueW,

HiFlyer,

amraybt

HP G60 laptop test device x86 intel core2duo with Windows 7 Pro 32bit installed (not a VM)

Installed patch 2018-01 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4056894)
Installation date: ‎05/‎01/‎2018 06:46 PM

no ill effects whatsoever after hours of use with shutdowns/restarts done and no errors.

edit: Holding off x64 W7 device as per MS-DEFCON

• This reply was modified 1 year ago by
  
   Microfix.

2 users thanked author for this post.

JDeC,

HiFlyer

Following update of KB4056894, computer crashes on restart, and goes into repair mode. Once completeled, reboots correctly, but patch still not installed. Tried several times, with same result.

Details:
Intel processor
Windows 7 64-bit pro
AVG free version, with full updates
Updated automatically.
(NB: the registry entry MS say is the flag to indicate the computer is suitable for an update was the correct value to allow the update!)

stu

2 users thanked author for this post.

rontpxz81,

woody

Yep, another AMD one here.

AMD Athlon 300+.

Following update of KB4056894, computer crashes on restart, and goes into repair mode.  Reboots again and just tried to repair start up.  Tried several times, with same result.

Tried everything listed here and eventually gave up.

Have just reinstalled Win7 from scratch.

Not a problem as PC is only an old test box that Im always trying to break.

Usually I can repair after “playing software games”. But this time it was really beyond an easy fix.

2 users thanked author for this post.

BackStop,

woody

Have installed 2018-01 Security Monthly Quality Rollup for Windows 7 x64-based Systems (KB4056894) on my Dell XPS8300 Intel Core i7-2600 machine, running Win 7 Pro SP1 + Microsoft Security Essentials.

No ill effects noted so far.

Edit to remove HTML
Please convert to plain text before cut/paste

This update seems to be totally bricking AMD machines. I think this rates a MS-DEFCON 1. This time MS really stuck it to the average Joe Blow user who has no idea on how to recover.

8 users thanked author for this post.

HiFlyer,

walker,

fk5353,

JDeC,

OscarCP,

BackStop,

woody

My ISP branded version of McAfee Internet Security [Win 7 – 64bit] updated and placed the proper registry entry. Windows Update now shows KB4056894. Since we are at defcon 2 I will hold off applying the patch for a bit.

The McAfee page also had a zip file with the reg code for those with older unsupported versions of their products.

-firemind

It has only ill effect on windows 7 with AMD cpus in our company.

3 users thanked author for this post.

HiFlyer,

MrBrian,

BackStop

I have to agree with the anonymous poster who suggested a DEFCON 1 level for now.  This mess looks like it may wreak havoc.  And not only with those who don’t know how to recover!

I have no present intention of trying the monthly rollup out, of course, but I have noticed that on my Intel machine it is checked, while it is unchecked on my AMD machine.

With regard to the anonymous comment above about the error message indicating a driver issue, it’s possible although (a) I’ve seen different error messages being reported, (b) I’ve never personally found any particular rhyme or reason to BSOD error messages, and (c) I’ve yet to see any report of a successful installation on an AMD machine or an unsuccessful installation on an Intel machine.  It may well be that this update is messing with drivers and that is causing the crashes, but do we yet really know anything beyond the fact that it’s an AMD issue?

Incidentally, while there are a number of separate threads on the MS Community Forum about the AMD issue, it’s worth noting that I’ve not previously seen such high numbers in the “I also have this question” line – over a hundred on one thread.

Talking of the MS Community Forum, it’s times like this that remind us why we miss PA Bear so much…

With regard to the DEFCON rating, it sounds to me like it’s 2 for Intel and 1 for AMD so an overall DEFCON 1 rating would certainly seem warranted. For AMD users the DEFCON 2 description doesn’t really cut it.

4 users thanked author for this post.

MrBrian,

OscarCP,

Bill C.,

BackStop

I have tried installing the 4056894 five times, but it always fails.

W7U x64 SP1.

BackStop wrote:

Intel or AMD processor?

Intel i7-6700K.

1 user thanked author for this post.

BackStop

In the UK. Four Windows 7 Pro 64bit computers, 2 AMD, 2 Intel. All have compatible antivirus and the requisite QualityCompat Registry key. I’m not seeing KB4056894 on any of them yet. Not that I want to install it, and anyway prefer the security only updates, but shouldn’t I be seeing it by now?

From the reports it appears to be mostly AMD, however, when posting about these types of issues, I believe folks should be including at minimum their CPU make (and number if known) and Windows version (and build if known).

I know many are already doing this, but for major hardware/software issues like this, the empirical data would be helpful in defcon determinations and debugging assistance.

Intel i7-960 CPU, Intel X58 MB, and Windows 7-64 Pro SP! here (all old legacy stuff) and even though my gut tells me the Security Only patch would “probably” be OK, I am definitely holding aff on this patch for a while. I suspect a v2 may be in the cards (or at least more info than the AV registry caution).

2 users thanked author for this post.

HiFlyer,

BackStop

What is the registry key for this?

Group A   Win 7X64,  AMD Sempron 145 processor ,  Microsoft security essentials.   NO  PROBLEMS, no slow down.

2 users thanked author for this post.

HiFlyer,

BackStop

I have my settings to “never check for updates”.  So after reading this thread I deceided to check updates.
Kb4056894 (important) is unchecked.  Date 1/4/18.

computer info:
Dell Inspiron 660 (purchased in 2013) just replaced hard drive in November 2017 and had Windows 7 reloaded.
Windows 7 Home Premium 64 bit SP 1
Server 2008 R2 x64
Processor:  Intel i3-3240 (ivy bridge 3rd generation)
chipset Intel (R) 7 series/C216
chipset family SATA AHCI Controller -1 E02

After new hard drive installed went to
Group A

Will not update until defcon is 3 or higher…
even then……………..?

ETA:
MSE for antivirus

• This reply was modified 1 year ago by
  
   dgreen.

2 users thanked author for this post.

HiFlyer,

BackStop

Updates are not yet showing up here ( last successful check, this morning. Win7 x64 ). Somehow I have always the feeling that Europe gets them slightly later

Just checked a client with a mix of Intel I5 and I7 all Win7x64 Pro. Update is offered but NOT checked on all systems. We’re holding off on installing to our clients at this time.

One Win8.1 machine with I5 update not offered.

KB4056894 is no longer ticked on both my PCs as of 07:00 7 Jan (Sydney AUS). M$ must have/are pulling it back.

1 user thanked author for this post.

woody

Very Interesting!

On the 4th or 5th (cannot remember the exact time, but it was late at night) I checked for the registry entry. It was present. I then checked WU manually (set to NEVER check). The January rollup was present and checked. I unchecked it and closed WU.

Today (1/6/2018) I checked WU manually at 3:28PM EST and there was no January rollup visible and only the December rollup was present and checked. (I am Group B and have installed the December Security Only patch. The registry entry is still there. My MSE us up to 1.259.1273.0. WU history shows nothing new except MSE definitions

I wonder if the January Rollup was pulled from WU.

The January Security Only for Win7-64 (KB4056897) is still in the Microsoft Update Catalog. The January rollup (KB4056894) for Win7-64 is also still in the Microsoft Update Catalog.

Win7-64Pro_SP1
Intel i7-960 on Intel DX58SO2 motherboard
Group B up to date, all IE updates applied, on .NET 4.7

Definitely holding off on this mess.

3 users thanked author for this post.

HiFlyer,

MrBrian,

DrBonzo

the last Microsoft updates are causing several issues with AMD Athlon 64 CPUs and realtes AMD CPUs with similar architecture, in Windows 7 is causing BSODs after first reboot and in Windows 10 is causing Windows to stuck in Windows logo after first reboot.

can someboy contact a Microsoft engineer / oficial developer and inform him/her about this bugs, because is affecting a lot of machines around the world :S

Experienced the BSOD when installing on Intel Xeon E5506 @ 2.13GHz (2133MHz), 4092 MB RAM.
Windows Server 2008 R2 SP1 64-Bit (6.1.7601).
Running as a VM on Citrix XenServer 6.0 (Build 50762p).

Had to issue “dism.exe /image:C:\ /cleanup-image /revertpendingactions” from CMD prompt of repair/recovery screen.

KB4056894 appeared to have run automatically first time leading to the BSOD but after reverting it is now unchecked.

Registry key is set to permit update so I assume ESET are confident it should would with
ESET File Security for Windows Server” v6.4.12004.0 Virus Signature Database 16693 (20180106)

1 user thanked author for this post.

MrBrian

PKCano wrote:

Are you trying to do a manual install or through Win Update? Did you check to see if your anti-virus has set the Registry key?

Windows update.

Registry key is set.

Seff wrote:

Also, if through Windows Update was the update checked for installation or was it unchecked and you checked it in order to install it?

I believe it was unchecked.

I use MSE for antivirus, I assume ithas the key updated right?

If Monthly Rollup KB 4056894 installed on windows 7 x64 with no issues,  should it be uninstalled for now and then wait till microsoft fixes it

This episode does seem to highlight a problem for Group B users that we perhaps haven’t encountered before. In order for the update to be offered under Windows Update (i.e. to Group A users) the appropriate registry key has to be in place through your AV software, but Group B users can download and install the security-only version direct from the MS Windows Catalog without having to meet that requirement, and failing which we are now seeing reports that it will crash the machine. If Group B users who don’t meet the registry key requirements have disabled Windows Update by switching it to “Never” they might be blissfully unaware that this update is not intended for them.

2 users thanked author for this post.

MrBrian,

SueW

If you remember the TV show ‘The X-Files’, the motto was ‘trust no one’.

Well I trust Microsoft even less. (I do trust the folks on AskWoody, though. Just to be clear. 🙂

I always have Windows Update check for updates but never download or install. It’s helpful to know what WU thinks my computer needs. BUT… I ALWAYS google the KB numbers, see what’s happening here at AskWoody, and check the MS support site before installing anything. The latter is terribly coy and reticent about admitting issues, but much to my great surprise, they did talk about the AV situation.

But I agree, most folks aren’t going to do any of that, if for no other reason than that they don’t know to and just expect their machines to work.

2 users thanked author for this post.

Cascadian,

HiFlyer

I’m running Win7 SP-1 Intel I-5 2500k. I’ve had KB 4056894 in windows update for 2 days, checked, and am  waiting this out. Out of curiosity after reading some posts here i checked WU and the update is now UNchecked.

The reg key is there, by the way.  FWIW

Thanks for all the informative posts on this mess.

2 users thanked author for this post.

woody,

MrBrian

Hello — I too had this issue – my cpu is —

AMD Athlon(tm) 64 X2 Dual Core Processor 4200+

my os is w7/32bit  — this rig is circa 2006

after the update was applied, I reboot and the os did not restart —  a repair screen appeared and I selected repair —  it took about 10 minutes and I think it used  the last restore point

1 user thanked author for this post.

woody

So, reading thru the replies, it seems that if anyone has an AMD CPU, they should hold off as per MS-DEFCON, for everyone really, unless you like a challenge on a test device 😉

My Observations:

(Group A) MSE seems to be ok on intel based hardware.

3rd party AV’s seem to be a lottery irrespective of CPU manufacturer.

Makes me think there are more hidden issues and a blame game about to kick off!

Having stated that, I would definitely hold off this patch and raise to MS-DEFCON 1 as others have hinted at. Awaiting this patch Tuesday for reports, excuses, re-patches and fixes..

1 user thanked author for this post.

HiFlyer

It’s a bit worrying that I seem to be the only person reporting a crash with an Intel processor (see stu above).

My CPU is:  Intel Core 2 Quad Q6700 2.66GHz.

The crash seems to be similar – computer goes into repair mode following reboot, so I’m assuming it’s the same cause, but maybe not.  I’ve never had a problem with an update before.  I’ve now put updates on hold till Microsoft sort it out.

Note that it also crashes in the same way with the KB4056897 update.

Stu

3 users thanked author for this post.

AJNorth,

rontpxz81,

woody

Yesterday we get 9 Computers from Different Clients with same Problem that they get all in BSOD after they Installed the Update KB4056894

Nothing Worked Recovery points was not Found

Windows Repair doesent worked

but at the end we found a Solution it was not the Easiest way and some more things are needed for it but we handled to make our Clients Happy Again i posted under MS Community a Discussion about that Problem with the Update and the AMD Athlon X2 Cpus https://answers.microsoft.com/en-us/windows/forum/windows_other-update/attention-kb4056894-security-update-will-make-your/47cb5507-b1d1-4d15-b719-30d57fc16bde

5 users thanked author for this post.

GoneToPlaid,

HiFlyer,

Cascadian,

AJNorth,

woody

I took a Windows 7 virtual machine running on VMware Workstation on a machine with a Intel Core i7 6800K CPU, which has Windows Defender completely disabled (Disabled via the program and disabled the Windows Defender service), with no other antivirus programs installed, and did the following :

(1) Set Windows Update to “Never Check”.
(2) Checked that it did not have that registry value.
(3) Installed the KB4056897 January Security-only update. (The virtual machine previously was patched to March 2017 using KB4012215.)

Reboot and the virtual machine booted and ran normally.

(4) Reactivated Windows Defender, instructed it to check and install the latest updates, then deactivated it again.
(5) Reboot the virtual machine, and that registry value still has not been set.
(6) Instructed Windows Update to check for updates and the Decemeber 2016 rollup KB4054518 showed up instead of the January 2018 rollup KB4056894.
(7) I then added the registry value myself and reboot the virtual machine.
(8) Checked Windows Update again and KB4056894 still did not show up.

No idea why the January 2018 rollup did not show up in Windows Update after I added that registry value myself. I can say it is not due to the presence of KB4056897 since on the same virtual machine but without KB4056897, KB4056894 did not show up after I added the registry value myself.

I have a business desktop. It is an AMD Athlon/64 Pro and I am very concerned about installing any January update that has been coded by Microsoft to target the Meltdown vulnerability. So far I have received the monthly update from Microsoft – I have WU set to send but do not install. I only use MSE and it is up to date – the register setting for Meltdown is in place.

The monthly rollup patch for W7/64 is sitting in the queue unchecked. When it was originally sent 2 days ago it was checked. I see that there are many BSODs for AMD systems, but not for Intel systems. Can Windows update differentiate between an AMD system and an Intel system – is this why it is not recommended now?

My own opinion(FWIW): Microsoft is very tight with Intel. AMD is a member in good standing but not a member of the cabal. Unfortunately, AMD is not well run and they have suffered from some bozo decisions in the past and it did not help that Intel unfairly and relentlessly pummeled them merely because it suited them.

I think Microsoft developed the meltdown patch for Intel without any regard for the fact that AMD is not impacted by it. The BSODs are a result of a reckless disregard for the customer base. I hope I am wrong.

1 user thanked author for this post.

HiFlyer

in response to Self, Windows Update is indeed set to notify bu do not install.

However, that does not have any baring on the substance of my post.

Updated two days ago, so far so good. Group-A, Win7 Home x64, Norton, i3, HP.

1 user thanked author for this post.

rontpxz81

After the BSOD the AMD based Dell Vostro rolled back the update on its own and an hour or so later rebooted itself where KB4056894 was once again waiting to be applied. Win 7 SP1 Home Premium. Applied via win update. Windows Defender AV. No other AV used.

BSOD here after KB4056894 update.  Able to roll back to restore point just before update. Checked and registry key was set.  Let WU install again with same effect…BSOD.  Thankfully was about to restore again and turned off WU.  Will wait for MS to fix their update.

Windows 7 64-bit Pro with all updates

AMD Athlon 64 4000+

Splendid stuff!

CPUs all work as designed, so of course Intel is miffed by being accused of any “bugs”. Since AMD users seemed quite smugged, Microsoft released a quality patch, that’ll do what it can to brick them, while letting Intel chips escape. What else is friendship for?

But while at it, by all means take down some of the old Intel chips at the same time…

These are my conclusions based on previous days adventures.

I may be off though… but well done Microsoft.

I have two Athlon 64 X2 based systems running 32 bit Win 7 Ultimate. One is a Dell Optiplex 740 with a +4800 chip with 65 nm design rules (Brisbane) the other a Compaq Presario SR1620NX running an older Manchester 90 nm design rule chip. Avira antivirus on one machine AVG on another. Doubt that matters. Both needed a system restore option to be taken on reboot after installing the update here being discussed. Both system restores were successful. I am now personally convinced the same will happen on an system using an Athlon chip. Later AMD? Don’t know. But I wouldn’t try it.
I think the key here is that this “patch” is not only irrelevant to the AMD design, but fatal to its operation. The AMD design (which I read either handles the privileged/user cache split entirely differently, or doesn’t to the cache split, the root cause of the problem, at all) simply hits a fatal error/exception/whatever you want to call it when encounters this patch code which to an AMD processor is unrecognizable nonsense. I also remember reading that an AMD exec said his chips were unaffected by the Spectre/Meltdown problem. So this is entirely consistent with my suspicion here. Bottom line, Microsoft in its haste was sloppy in this distribution. Their “update” should check the CPU and not do the change on AMD chips. Either they forgot, or to save time simply decided to throw AMD useers under the proverbial bus. In either case, if your AMD system is working, don’t waste time with repeated reinstall attempts. Instead be glad that system restore brought back your system. Don’t press your luck!

Same Crash here

Windows 7 SP1
Dell Inspiron 1721
AMD Turion 64 X2 TL-50
ESET Internet Security v 11.0.159.0

Am running a Windows 7 x64 SP1 fully patched. Intel CPU but Intel VGA AND AMD Radeon graphics card (it’s a laptop – Dell Latitude E6440), since the Spectre patch was applied, the Radeon driver refuses to load. Reinstalling it etc (even using DDU) hasn’t helped.

Is anyone else finding that on systems with Intel CPUs but AMD GPU, the AMD GPU driver isn’t loading?

1 user thanked author for this post.

woody

With a typical Group L attitude I went ahead to check for updates…

First click on “Search for updates” gave a read WU text with an errorcode and a link for further explanation of the code. Clicked that and got to a Microsoft webpage, which of course didn’t have that number…

Clicked “Search” again and it now presented KB4056894, an optional .NET 4.7 roll-up, removal tool KB890830 and a compatibility tool for Win 10 upgrade… checked all but the latter and ran the install.

Took a while to finish, but all went well.

As expected, since I run W7 on an Intel Core i7-930 and Intel X58 chipset… fits nicely in my “let’s annoy amd and old intel chips users”-conspiracy theory!

I once here pleaded for a Windows 10 Workstation. Got that, and since that’s just more of the same, I’ll now plead for a Windows 10 Military Grade version!

4 users thanked author for this post.

Noel Carboni,

HiFlyer,

Bill C.,

AJNorth

Do you also have a problem with BSODs on amd phenom/fx ? Or on this CPU the problem does not occur.

Edit to remove HTML

BSOD  (0X000000C4,….) on Win7 pro 64 SP1 + all updates (except 6 optional) and MSE, on  AMD Athlon x2 4850e. PC was able to recover after rolling back KB 4056894.

Are there any AMD Athlon x2 CPU users that succesfully installed KB 4056894?

1 user thanked author for this post.

HiFlyer

BSOD, then freeze with Win logo.

Win10\1709\32bit Athlon X2 5200, after KB4056892, ESET antivirus
DISM /image:C:\ /cleanup-image /revertpendingactions
… Did them working again

1 user thanked author for this post.

HiFlyer

Hi,

I installed yesterday the KB 4056895 on my laptop which has an Intel CPU I7-4500 (no AMD!) on Windows 8.1, Avira Free Antivirus,  and have experienced 4 times the BSOD.

I am very worried about this, since the only Intel owners which reported issues have previous versions of Intel processors.

I think I will uninstall the KB, but will I get in future another one that is fixed?

1 user thanked author for this post.

HiFlyer

I’ve two Desktop machines with AMD chips that made it through Microsoft’s patch. AMD Athlon II X2 CPU and AMD A4-5300 APU. Only my laptop (HP Compaq 6735s Notebook) that has a AMD Turion X2 RM-70 CPU, BSOD’d. System restore on the laptop did report a failure, but on reboot, it said it was successful.

Thanks for covering this Woody. The system I attempted to update is an AMD 64 X2-4600 with Win7 and MS Security Essentials. The first install of KB4056894 via Windows Update resulted in the STOP: 0x000000C4 BSOD. That was the day first released on 1/3/18.  However, for this 1st try, I did not check the registry key due to the fact I wasn’t using any 3rd party AV.  Windows gave the repair option at next reboot and within 15 minutes was back up, minus the update.   Before the 2nd attempt on 1/8, I checked the registry key as informed by MS and it was correct so no changes needed. I guess I’m a glutton for punishment because I allowed Windows Update to do the install again, and again resulted in the same one line 0x000000C4 BSOD. As of today I see Microsoft has acknowledged there is an issue and blocked this specific update until further notice.

If it helps, I’ve been getting this same problem, running an AMD FX-4130. I run Malwarebytes, though I don’t know why that’s relevant, and Windows 8.1 forced the update down my throat. My first error message was a watchdog violation, which I identified as spyware, and got spybot killer for it, but it didn’t fix the problem. The rest of the blue screens have been really glitchy, not even displaying the errors correctly, just that sickening periwinkle with the graphic stretched and warped over it.

walker wrote:

I have no information about a “registry key”, so is it best to just to take a chance and do an install on KB 4056894.

You should follow @mrbrian ‘s instructions. This is what he says

Windows 7 Monthly Rollup (“Group A”) – recommended:

If Windows Update offers KB4056894 then install it. If Windows Update doesn’t offer KB4056894, then if Windows Update offers KB4057400 then install it. If neither update is offered, then wait for the February 2018 Windows updates.

If KB4056894 is not in your “important” updates list, you will need to see if KB4057400 is in the “optional” updates list then check it and click OK at the bottom of the window.
You will need KB4057400 ONLY if KB4056894 is NOT in your update list.
If neither are there, then wait for Feb updates.

1 user thanked author for this post.

MrBrian

Thanks to everyone who have posted and discussed this issue. KB4056894 is exactly what killed one of my computers. But it then triggered something far worse.

This machine has an AMD Athlon 64 dual-core CPU with an NVidia GeForce 7300 display adapter. In safe mode I can see the network driver, but the media section is missing the devices. Before this update, everything was working. HD is working ok, Spinrite shows no errors.

Event log shows that KB4056894 was queued 1/4/18 @ 11:26 p.m. and scheduled for install next day at 3 a.m. Logs show the system never came back after that. I was getting a BSOD with 0xc4 on boot, so I tried the dism uninstall. That got the system to boot, but it’s now badly compromised. Network and media device drivers are not working. Something had the hard disk churning, heavy CPU activity, can’t run anything. Within about 5 minutes I get a BSOD with 0xf4, does a memory dump, then reboots again. Machine is unusable at this point.

BTW, even though I ran the uninstall for the package, my event log shows that “Package KB4056894 was successfully changed to the Installed state,” as of when the uninstall had completed and I finally got a login prompt.

downloaded KB4056897 via Microsoft Update Catalog and installed

black screen after the BIOS POST screen: (windows failed to start etc.) error 0xc0000225

booted Windows 7 Startup Repair and it did a System Restore: its diagnosis and repair log said “Unspecified changes to system configuration might have caused the problem”

rebooted and windows started normally

Window 7 Professional SP1 32 bit

CPU AMD Athlon 64 X2 Dual core Processor 3800+

Avast Free Antivirus

Did you check to see if the Registry key had been set. If it has not, your anti-virus may cause a BSOD after the install.

2 users thanked author for this post.

JDeC,

SueW

“Never check for updates”, I always do it manually.

2 users thanked author for this post.

BackStop,

HiFlyer

yes, the Registry key was already set before I manually applied the patch

I checked it before downloading following what microsoft said here: https://support.microsoft.com/en-us/help/4056897/windows-7-update-kb4056897

The problems seem to be mostly with AMD processors. Wait a while and see if Microsoft sorts things out.