Search the Community
Showing results for tags 'kb4056894'.
Hi, I've just repaired a Dell Inspiron laptop (Windows 7 Home Premium 64-bit, AMD Turion X2 DC Mobile RM-74 2.20 GHz) that suffered a STOP 0x000000C4 BSOD message on each Windows restart attempt, with no access to any safe modes, I found a fix online... https://answers.microsoft.com/en-us/windows/forum/windows_7-update/stop-0x000000c4-after-installing-kb4056894-2018-01/f09a8be3-5313-40bb-9cef-727fcdd4cd56?auth=1&rtAction=1515190079156 ...that suggested removing the KB4056894 patch using the dsim command from Windows 7 recovery environment. This fixed the blue screen on re-boot. I've now disabled it's re-installation within the Windows Update settings. On further reading... https://support.microsoft.com/en-gb/help/4056894/windows-7-update-kb4056894 it appears that this fix is only applicable (installed?) to PCs "where the Anti virus ISV have updated the ALLOW REGKEY.". According to the ESET forum page on the Meltdown + Spectre CPU vulnerabilities... https://forum.eset.com/topic/14274-esets-response-to-meltdown-and-spectre-cpu-vulnerabilities/ ...ESET have released module update 1533.3 - "to ensure compatibility with Microsoft's updates to the Windows operating systems". The laptop, while running ESET Smart Security version 8.0.316.0, does have module 1533.3 installed. Q1. Is KB4056894 anything to do with patching Meltdown/spectre CPU vulnerabilities? Q2. If so why does the laptop with module 1533.3 installed suffer the BSOD on restarts? Q3. Will this occur on all my client PCs when KB4056894 is automatically delivered over the next days/weeks? Thanks in advance PS: To double check the error, I repeated the KB4056894 install via WU and it resulted in the same BSOD - just in case the ESET module 1533.3 was not installed prior to the Windows update first occurring (last week). Mike