We’ve seen many reports here on AskWoody. There’s also a thread on Reddit. More on MyDigitalLife. Some reports are detailed. Some are — well, they’re
[See the full post at: Multiple reports of blue screens (BSODs) 0X000000C4 when installing the January Win7 Monthly Rollup KB 4056894]
|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
-
Multiple reports of blue screens (BSODs) 0X000000C4 when installing the January Win7 Monthly Rollup KB 4056894
- This topic has 139 replies, 33 voices, and was last updated 7 years, 2 months ago by
.
AuthorViewing 58 reply threadsAuthor-
-
-
Well, assembly lines switch parts on the fly… so just testing one machine won’t do the job. Also, this seems to be a driver issue…
# for hex 0xc4 / decimal 196 :
DRIVER_VERIFIER_DETECTED_VIOLATION bugcodes.h
# A device driver attempting to corrupt the system has been
# caught.
# The faulty driver currently on the kernel stack must be
# replaced
# with a working version.1 user thanked author for this post.
-
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.
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
- 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
-
I’d say that AMD owners would be wise to avoid the patch, eh?
1 user thanked author for this post.
-
-
-
-
Hello,
I tried KB4056895 today on windows 8.1 pro x64 3 times today. Does not work. Rollback after each reboot. I tried to install it manually after downloading the patch (windows8.1-kb4056895-x64_0cdcb10e40aa019d4934d74cca93f6c36a11e07a.msu). I got the same result (Lenovo X1C gen 3, I7, 8 go RAM).
1 user thanked author for this post.
-
-
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.
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 PMno ill effects whatsoever after hours of use with shutdowns/restarts done and no errors.
edit: Holding off x64 W7 device as per MS-DEFCON
Windows - commercial by definition and now function...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
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.
-
I’ll add: Intel i5 computer
Windows update: Not automatic. Set to check with me before downloading and installing.
The update was set as important but the box was unchecked when I first checked it.
-fm
1 user thanked author for this post.
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.
-
-
-
Pardon my ignorance, but what does this do or fix?
1 user thanked author for this post.
-
-
Intel or AMD processor?
Intel i7-6700K.
1 user thanked author for this post.
-
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?
1 user thanked author for this post.
-
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?
I’m in the US but otherwise much in the same boat. I am running a Windows 7 Pro 64 bit computer with an Intel processor. I am running Avast! antivirus which set the QualityCompat Registry key. And yet, I’m not seeing KB4056894 either. Not that I’m planning to install it anytime soon.
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).
-
I think the Win7 Rollup was initially checked important (providing the Reg key was present). I have now seen reports that is is UNCHECKED on some – which would probably imply MS recommends NOT installing at present (I wonder why!!).
I think the Security-only patch is also at risk. The absence of the Reg key does NOT prevent manual installation of either the SO or the Rollup. I experimented with Win7, Win8 and Win10 1709.
-
-
I can confirm that on my machine (i7-3740QM Win7 x64 Ultimate) KB4056894 was checked but as of today (Sat. Jan. 6) it is unchecked. The registry key is present. Of course I always follow MS-DEFCON, so I did not take my chances…
1 user thanked author for this post.
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 E02After new hard drive installed went to
Group AWill not update until defcon is 3 or higher…
even then……………..?ETA:
MSE for antivirusKB4056894 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.
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.7Definitely holding off on this mess.
-
This is essentially exactly what happened to me, also. The only exception is a slight difference in timing: I noticed last night (around 7:00 pm PST if I recall correctly) that the January Rollup had been replace with the old December Rollup.
Win 7 sp1 x64 Pro, Group B, Intel core i3-5005U, Up to ate through December, .NET 4.7, Last MSE update was 259.1256
-
Given the extent of the coverage on their own community forums, I think it highly likely that MS are already aware of the issue.
I referred earlier to one of the threads on that forum having over 100 posters saying they had the same question, and that was based on 108 people. It’s now 175 and very likely still rising – and that’s just one of a number of threads on the MS forum with a lot of other sites like this one picking up on the problem. It’s hopefully only a matter of time before the update gets pulled, and in the meantime the best advice is not to touch it – not least as we’re now beginning to see reports of BSODs on Intel machines and not just on AMD ones.
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.
If you are comfortable looking searching your Registry, you can check it yourself:
Click Start in the lower left of your computer, and type “regedit” (without the quotes)
Click on regedit.exe that results from your search:
Your Registry Editor will open and you will see ‘Computer’ with 5 HKEYs below itClick on ‘Edit’ in the Toolbar
A ‘Find’ box will open: just type “QualityCompat” (without the quotes) and click the ‘Find Next’ buttonIf QualityCompat is found, then the Key has been updated.
Extra credit: If you want to confirm that the value for QualityCompat was set properly:
Click on QualityCompat:
On the right pane, under “Name’ you will see cadca5fe-87d3-4b96-b7fb-a231484277cc, and
under ‘Type’ you will see REG_DWORD, and
under ‘Data’ you will see 0x00000000 (0)[Note: Avira updated my Registry thusly on Jan. 5]
Win 7 SP1 Home Premium 64-bit; Office 2010; Group B (SaS); Former 'Tech Weenie'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.
-
Yes. I think you just figured out what my testing was about the last couple of days. The absence of the RegAllow key does NOT stop you from installing either the SO or the Rollup manually – at least in my testing.
But with WU set to “Never” when you do a search and the update is there checked, you figure that the Reg key is present. (Perhaps you should look anyway?)
What worries me is Joe User, with his WU on Automatic, at times like these.
AND, we are still on DEFCON 2.4 users thanked author for this post.
-
You both raise an excellent point. It may be worth, when the time comes for DEFCON 3, adding an instruction to the Group B directions to make sure to check the Registry for this “RegAllow” key prior to installing the SO Update. I just included the instructions in #157000 above.
Win 7 SP1 Home Premium 64-bit; Office 2010; Group B (SaS); Former 'Tech Weenie'4 users thanked author for this post.
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.
-
Well been watching this mess both here and other places……. and also the continual updating/upgrading of Win10 and all the bruhaha it causes, and quite frankly you’ve got to ask yourself: “Is this what you bought a computer for? To continually troubleshoot and fix the problems.” It doesn’t leave much time for you to do the things you originally intended to do on your computers – plus all the things you do in real life.
So I don’t think it behoves people to bear that responsiblity of double checking things……… why should they…… I know it’s probably for their own good……… but it was not written in the mandate when they bought their computers. People don’t expect to have to do this. This is something by way of extra effort that needs to be put in to keep their computers running efficiently……… and to my mind they should not be made to be as though they aren’t up to it. And I would humbly suggest that they are not the problem. LT
May your choices reflect your hopes – not your fears! Nelson Mandela
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.
Win 10 Pro v.20h2
-
I installed it on a Intel I-5 2500k with Asus MB, Win7 pro SP-1 and had no problems
1 user thanked author for this post.
-
-
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
fpefpe
1 user thanked author for this post.
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..
Windows - commercial by definition and now function...1 user thanked author for this post.
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
-
-
HP XPS desktop w/ Win7 Ultimate SP1 (almost fresh install with all recent updates), Intel i7 860, nvidia GPU. similar story, kb4056897 installed (no problem initially), subsequently random BSOD – first one, same day (but not immediately after installation!); later, time to time; sometimes a few days – nothing, and sometimes – every day.. and weird issues (like, when waking up from sleep mode, saying “computer recovered from unexpected shutdown”). I think I’ll uninstall the patch and see if it changes for the better
1 user thanked author for this post.
-
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.
-
-
woody said:
So you take the hard drive from the bluescreened PC, take it to a second, unpatched Athlon, and the second Ahtlon will boot?Different anon here. The cross-machine fix apparently works. Yesterday, I came across user kit-guy (who has no recovery disc or startup repair function) post about the “5 MIN FIX” at Reddit:
https://www.reddit.com/r/sysadmin/comments/7ode4s/problems_with_windows_7_quality_rollup_kb4056894/dscfagcUser did not specify the make & OS of the 2nd PC, although he described the affected PC as “the AMD machine”.
You have to boot the BSOD HDD into Safe Mode on an unaffected PC, which will announce “Failed update installation”. After the 2nd PC automatically reconfigures the BSOD HDD, reinstall the HDD back in the affected PC.
The initially-affected PC should be able to boot up normally this time, & inform about a failed Windows Update install. Thereafter, launch WSUS & hide the problematic KB update.
2 users thanked author for this post.
-
MB: Foxconn M61PMV
GFX: NVIDIA GeForce GT430
CPU: AMD Athlon 64 Dual Core 5200+ 2.7 GHz
OS1: Windows 7 Ultimate 64 bit Service Pack 1OS2:Windows 10 Professional 64 bit Version 1511 10586.1259
In his post he basically said to put the hdd/equivalent into a system with a more modern AMD processor and boot in the newer rig to uninstall the update then transfer the hdd back to its original home. His command of the English language is atrocious so it took me a couple reads. Makes sense if you don’t have a restore point to go back to though.
I had the same BSODs on three of my rigs which have older AMD processors. None of my intel based stuff had any issues. So far it seems as though it is just older processors, mainly AMD.
Sorry for the repost. Thought I had a handle on here already.
We want a shrubbery, but not too nice of a shrubbery.
1 user thanked author for this post.
-
-
-
See, this right here is one of the things I wonder about. It may be in my own mind only, but I have thought of the MSRT as being the Microsoft way of assuring your Windows environment is clean, without regard to your preferred 3rd-party protection. Would it make sense to issue a new copy of MSRT to run with the SMQR in order to make sure that key is set first?
Left-hand, meet right-hand. Microsoft.
No. That would defeat the purpose of the key.
-
-
Oh, thank you again for your continued interest in the produce of my thoughts.
But I must admit you have me stumped here. How does setting the registry key through code piggybacked on the MSRT product differ from having any of the other 3rd-party vendors do it through there products? MSRT at least is an in house product.
If you can teach me I am interested. If this is entertainment, I am not.
It’s because MSRT is an in-house product that having it set the registry key would defeat its purpose. The sole purpose of the key is to ensure that the patch does not brick machines with third-party antivirus that makes unsupported calls to the kernel. See the FAQs at Important: Windows security updates released January 3, 2018, and antivirus software
(Could you drop the “idle entertainment” quips, which I really don’t understand or appreciate?)
1 user thanked author for this post.
-
-
@Paul
You may want to check this information.MSRT is delivered once a month with Win Update. If it is checked in the important updates, it is updated and runs during the update process. It is not meant to replace you anti-virus program, it does not run in the background (although you can run it manually). It runs even if you are running a full-time anti-virus program, but only checks for a limited number of things. I do not believe it sets the RegAllow key. If it did, it would defeat the purpose of verifying that the AV is compatible
MSE and Defender (on Win10), on the other hand, are anti-virus/spyware protection that runs in the background. They are meant to replace your anti-virus program – assuming you are not running two anti-virus programs at the same time. As such, they should set the RegAllow key the same way a third-party program would if it is compatible.
1 user thanked author for this post.
-
-
MSRT comes out on Patch Tues which hasn’t happened yet. The SO and Rollup were issued out of band for “emergency” reasons.
Would it make sense to issue a new copy of MSRT to run with the SMQR in order to make sure that key is set first?
Left-hand, meet right-hand. Microsoft.
You weren’t vague. MSRT just doesn’t do that
1 user thanked author for this post.
-
-
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.
-
Thanks for clarifying. No indeed, I wasn’t suggesting that it had any bearing on the substance of your post. I just wanted to make sure that you remained in full control of update installations which isn’t always the case under “Download but do not install”.
1 user thanked author for this post.
Updated two days ago, so far so good. Group-A, Win7 Home x64, Norton, i3, HP.
1 user thanked author for this post.
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.
anonymous #157348 said:
Is anyone else finding that on systems with Intel CPUs but AMD GPU, the AMD GPU driver isn’t loading?What is the exact model-generation & date of release (if you know that) of your Intel CPU & AMD GPU respectively ? Are they still supported by the OEM &/or the firmware manufacturer ?
On a related note, user WakeXT reported over at Reddit that his machine with AMD Athlon 64 X2 Dual Core 6000+ CPU & Nvidia GPU experienced BSOD after installing MS’s standlone security-only Meltdown KB patch.
And guess what … ? Microsoft Customer Rep helpfully advised user that the BSOD could have been caused by the Nividia GPU driver. So user reverted to an earlier restore point & disabled Nividia GPU driver, but still received BSOD after re-installing MS’s Meltdown KB patch.
As user said: “Even if a driver were at fault, it probably wouldn’t get updated anyway due to how long EOL the hardware has been.”
1 user thanked author for this post.
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.
-
@ Jan K:
Thanks for your reply and the fact that you included the CPU and chipset. I to have an i7 of that vintage (i7-960) and an Intel DX58SO2 motherboard. Glad to hear it worked. I am holding off to patch, but was happy to hear from someone using this legacy combo.
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.
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 again1 user thanked author for this post.
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.
-
Avira should have set the RegAllow key in the Registry. Verify that is is there.
If you are running any other security software, verify that it is compatible (firewall, anti-exploit, etc)
Check with the OEM for compatibility of other components – for example, there have been reports of problems with AMD Radeon graphics cards.And last, WAIT to try again. The implications of the vulns have not all shaken out, and we are still on DEFCON 2.
1 user thanked author for this post.
-
-
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.
Viewing 58 reply threads - This topic has 139 replies, 33 voices, and was last updated 7 years, 2 months ago by
Plus Membership
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Get Plus!
Recent Topics
-
Tracking content block list GONE in Firefox 138
by 1 hour, 21 minutes ago
-
How do I migrate Password Managers
by 44 minutes ago
-
Orb : how fast is my Internet connection
by 5 hours, 43 minutes ago
-
Solid color background slows Windows 7 login
by 7 hours, 3 minutes ago
-
Windows 11, version 24H2 might not download via Windows Server Updates Services
by 5 hours, 34 minutes ago
-
Security fixes for Firefox
by 5 hours, 2 minutes ago
-
Notice on termination of services of LG Mobile Phone Software Updates
by 17 hours, 47 minutes ago
-
Update your Apple Devices Wormable Zero-Click Remote Code Execution in AirPlay..
by 1 day, 2 hours ago
-
Amazon denies it had plans to be clear about consumer tariff costs
by 17 hours, 52 minutes ago
-
Return of the brain dead FF sidebar
by 5 hours, 3 minutes ago
-
Windows Settings Managed by your Organization
by 4 hours, 11 minutes ago
-
Securing Laptop for Trustee Administrattor
by 5 hours, 12 minutes ago
-
The local account tax
by 6 hours, 24 minutes ago
-
Recall is back with KB5055627(OS Build 26100.3915) Preview
by 1 day, 15 hours ago
-
Digital TV Antenna Recommendation
by 1 day, 8 hours ago
-
Server 2019 Domain Controllers broken by updates
by 2 days, 3 hours ago
-
Google won’t remove 3rd party cookies in Chrome as promised
by 2 days, 5 hours ago
-
Microsoft Manager Says macOS Is Better Than Windows 11
by 2 days, 8 hours ago
-
Outlook (NEW) Getting really Pushy
by 1 day, 11 hours ago
-
Steps to take before updating to 24H2
by 1 day, 1 hour ago
-
Which Web browser is the most secure for 2025?
by 1 day, 15 hours ago
-
Replacing Skype
by 1 day, 4 hours ago
-
FileOptimizer — Over 90 tools working together to squish your files
by 2 days, 2 hours ago
-
Excel Macro — ask for filename to be saved
by 23 hours, 59 minutes ago
-
Trying to backup Win 10 computer to iCloud
by 1 day, 3 hours ago
-
Windows 11 Insider Preview build 26200.5570 released to DEV
by 4 days, 8 hours ago
-
Windows 11 Insider Preview build 26120.3941 (24H2) released to BETA
by 4 days, 10 hours ago
-
Windows 11 Insider Preview Build 22635.5305 (23H2) released to BETA
by 4 days, 10 hours ago
-
No April cumulative update for Win 11 23H2?
by 2 days, 22 hours ago
-
AugLoop.All (TEST Augmentation Loop MSIT)
by 4 days, 10 hours ago
Remembering Woody
