Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Multiple reports of blue screens (BSODs) 0X000000C4 when installing the January Win7 Monthly Rollup KB 4056894

    Posted on January 5th, 2018 at 17:01 woody Comment on the AskWoody Lounge

    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 complaints. If you can imagine. AMD machines are being pinpointed.

    If you hit a blue screen, or you know someone who did, please post about it here. Include your processor type (Intel or AMD), which version of Windows you’re using, which antivirus you’re using, and whether you installed the patch manually or via Windows Update.

    UPDATE: Lots and lots of reported problems.

    TechNet: Blue Screen after KB4056894

    Answers Forum: STOP: 0x000000C4 after installing KB4056894 – 2018-01 Security Monthly Quality Rollup for WIndows 7 for x64 

    Overclockers UK: Warning on KB4056894 (Intel/AMD) Fix caused Operton Bluescreen/STOP

    Reddit: Problems with Windows 7 Quality Rollup (KB4056894)

    Thanks for the links, everyone.

    If that helped, take a second to support AskWoody on Patreon

    Home Forums Multiple reports of blue screens (BSODs) 0X000000C4 when installing the January Win7 Monthly Rollup KB 4056894

    This topic contains 140 replies, has 34 voices, and was last updated by  anonymous 3 days, 13 hours ago.

    • Author
      Posts
    • #156724 Reply

      woody
      Da Boss

      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]

      6 users thanked author for this post.
    • #156729 Reply

      Seff
      AskWoody Lounger

      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!

      • #156763 Reply

        anonymous

        that would be nice, however, are we not at defcon 2?

      • #156829 Reply

        anonymous

        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.
    • #156764 Reply

      anonymous

      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.
    • #156761 Reply

      anonymous

      “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”

    • #156777 Reply

      anonymous

      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.
      • #156793 Reply

        woody
        Da Boss

        I’d say that AMD owners would be wise to avoid the patch, eh?

        1 user thanked author for this post.
        • #157537 Reply

          anonymous

          woody said:
          I’d say that AMD owners would be wise to avoid the patch, eh?

          And possibly some users with older Intel CPUs as well …

          At MS TechNet, there is a report from an Intel CPU user (Intel Core i7, exact model not stated) whose Win OS got killed by BSOD, despite the presence of the compliant registry key.

          Note: Intel Core i7 models range from i7-920 (released: Nov 2008) to i7-960 (Oct 2009).

          Wayne Hartell (January 06, 2018 3:40 AM):
          https://social.technet.microsoft.com/Forums/windows/en-US/df98809f-ba87-40b4-a027-fdad302a1d3f/blue-screen-after-kb4056894

          BSOD about an hour after installing the update. My system has the reg key (set by AV vendor) to allow the update, but still got the BSOD none the less. The cure is worse than the problem. Removing the update.

          […] that key was set on my system, but the BSOD still happened. Maybe the AV vendor didn’t realize they actually had to do something rather than just set the key. Ugh. Will be sitting this one out until it’s sorted out. Obviously cannot accept random BSODs, especially on systems that have run flawlessly for years on end.

    • #156781 Reply

      anonymous

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

      • #156794 Reply

        woody
        Da Boss

        … and there it is.

        January 4, 2018—KB4056895 (Monthly Rollup)

        https://support.microsoft.com/en-us/help/4056895

        • #157288 Reply

          EP
          AskWoody Lounger

          Microsoft KB article 4056895 has been posted but KB4056895 for Win8.1 is not available from MS Update Catalog nor Windows Update, maybe until Jan. 9 (1st patch Tuesday of year 2018). I wonder if KB4056895 for Win8.1 will have the same BSOD effect to AMD based PCs as what KB4056894 for Win7 did recently.

          No matter, I don’t need to rush in and get the KB4056894 patch for Win7 since all my Win7 PCs are working fine with the December 2017 cumulative update (and are Intel based and not AMD based).

          • #157773 Reply

            anonymous

            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.
    • #156797 Reply

      GoneToPlaid
      AskWoody Lounger

      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 2 weeks ago by  GoneToPlaid.
      3 users thanked author for this post.
    • #156804 Reply

      amraybt
      AskWoody Lounger

      It seems that the blue screens are happening only with the monthly rollup (KB4056894) and not the security-only rollup (KB4056897), based on the few examples so far. Strange…

      -- Lifelong member of Group B --
      Win 7 x64 desktop (Haswell CPU, AMD GPU)
      Win 8.1 x64 laptop (Haswell CPU, Nvidia GPU)

      2 users thanked author for this post.
      • #156912 Reply

        anonymous

        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

        • #156920 Reply

          PKCano
          AskWoody MVP

          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.
    • #156850 Reply

      Microfix
      AskWoody Lounger

      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

      | 1xPC W8.1 Pro x64 Ivybridge| | 1xPC Linux Hybrid x64 Ivybridge| | 1xPC W7 Pro x32 C2D Test Rig| | 1xPC W7 Pro x64 Haswell|
        No problem can be solved from the same level of consciousness that created IT - AE
      • This reply was modified 1 week, 6 days ago by  Microfix.
      2 users thanked author for this post.
    • #156853 Reply

      anonymous

      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.
    • #156864 Reply

      anonymous

      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.
      • #157185 Reply

        anonymous

        anonymous #156864 said:
        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.

        Wow, I wonder what is the percentage of AMD CPU users who resorted to reinstalling Win OS due to Microsoft’s Meltdown patch. What a meltdown the start of the year has been.

        Some AMD users reported that they rescued the situation by booting with the Startup Repair disk or Win OS installer disk, then go to command prompt to manually uninstall the problematic KB patch. Their otherwise-bricked systems were able to boot into the desktop environment after that.

    • #156865 Reply

      SH2071
      AskWoody Lounger

      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

    • #156883 Reply

      anonymous

      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.

       

      7 users thanked author for this post.
    • #156885 Reply

      anonymous

      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

      • #156945 Reply

        anonymous

        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

    • #156888 Reply

      anonymous

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

      2 users thanked author for this post.
    • #156892 Reply

      BackStop
      AskWoody Lounger

      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!

    • #156902 Reply

      Seff
      AskWoody Lounger

      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.
    • #156910 Reply

      alkhall
      AskWoody Lounger

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

      W7U x64 SP1.

      • #156911 Reply

        BackStop
        AskWoody Lounger

        Intel or AMD processor?

      • #156955 Reply

        Geo
        AskWoody Lounger

        Click on START,  Control panel, upper right hand corner click on category, click on large icons,click on  notification area icons,  check mark “always show all icons and notifications on task bar.  click OK.  Go back to  update page  and retry the update , I have it set for automatic updates.

        • #156963 Reply

          DrBonzo
          AskWoody Lounger

          Pardon my ignorance, but what does this do or fix?

          1 user thanked author for this post.
        • #157007 Reply

          Geo
          AskWoody Lounger

          I had the same problem where my up dates wouldnt install no matter how many times I tried.  Scanned the internet for an answer.  A site mentioned the above  fix, which like you ask it didnt make sense at the time but I tried it and it worked.

    • #156918 Reply

      alkhall
      AskWoody Lounger

      Intel or AMD processor?

      Intel i7-6700K.

      1 user thanked author for this post.
      • #156921 Reply

        PKCano
        AskWoody MVP

        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.
        • #156922 Reply

          Seff
          AskWoody Lounger

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

          3 users thanked author for this post.
    • #156925 Reply

      PatC
      AskWoody Lounger

      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?

      • #156926 Reply

        HiFlyer
        AskWoody Lounger

        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?

        Windows update settings?

        • #156935 Reply

          PatC
          AskWoody Lounger

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

          2 users thanked author for this post.
      • #156959 Reply

        alpha128
        AskWoody Lounger

        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.

    • #156927 Reply

      Bill C.
      AskWoody Lounger

      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.
      • #156928 Reply

        PKCano
        AskWoody MVP

        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.

        2 users thanked author for this post.
        • #156932 Reply

          BackStop
          AskWoody Lounger

          I think it was checked on my system at first.  I really don’t remember now.  I am running another check as I type and will post the result as soon as it completes.

          January roll-up, NOT checked by default.

          Win7 Pro 32bit, AMD Athlon 64×2 Dual Core 6000+ 3.00GHz

          MSSE for AV

          Group A

          • This reply was modified 1 week, 6 days ago by  BackStop.
          • #156936 Reply

            PKCano
            AskWoody MVP

            We don’t check/install items that are unchecked by default.
            This is why!!

            6 users thanked author for this post.
            • #156949 Reply

              BackStop
              AskWoody Lounger

              Yep!  Thanks to this site, I have avoided the BSOD and bricking my PC several times! (grin)

        • #156957 Reply

          Pim
          AskWoody Lounger

          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.
    • #156939 Reply

      anonymous

      What is the registry key for this?

    • #156948 Reply

      Geo
      AskWoody Lounger

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

      2 users thanked author for this post.
    • #156951 Reply

      dgreen
      AskWoody Lounger

      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 week, 6 days ago by  dgreen.
      2 users thanked author for this post.
    • #156960 Reply

      mazzinia
      AskWoody Lounger

      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

    • #156973 Reply

      cyberSAR
      AskWoody Lounger

      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.

    • #156974 Reply

      Pierre77
      AskWoody Lounger

      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.
    • #156975 Reply

      Bill C.
      AskWoody Lounger

      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.
      • #156981 Reply

        DrBonzo
        AskWoody Lounger

        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

        2 users thanked author for this post.
    • #156970 Reply

      anonymous

      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

      • #156982 Reply

        Seff
        AskWoody Lounger

        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.

        • This reply was modified 1 week, 6 days ago by  Seff.
        • This reply was modified 1 week, 6 days ago by  Seff.
        4 users thanked author for this post.
    • #156971 Reply

      anonymous

      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.
    • #156986 Reply

      alkhall
      AskWoody Lounger

      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.

      • #156988 Reply

        PKCano
        AskWoody MVP

        The patch should show up unchecked now – which means don’t install. There is severe problems with the Jan patches. Wait a while

    • #156987 Reply

      alkhall
      AskWoody Lounger

      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.

    • #156992 Reply

      anonymous

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

      • #156994 Reply

        PKCano
        AskWoody MVP

        I would verify it, if I were you.
        But as many problems as we are seeing, now is not a good time to install the Jan patch anyway.

        2 users thanked author for this post.
        • #157244 Reply

          wdburt1
          AskWoody Lounger

          PKCano, thanks for your exertions.  You are working as an emergency responder in this situation, no two ways about it.

          • This reply was modified 1 week, 5 days ago by  wdburt1.
          2 users thanked author for this post.
      • #157000 Reply

        SueW
        AskWoody Lounger

        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 it

        Click on ‘Edit’ in the Toolbar
        A ‘Find’ box will open: just type “QualityCompat” (without the quotes) and click the ‘Find Next’ button

        If 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; Former 'Tech Weenie'

        6 users thanked author for this post.
    • #156995 Reply

      anonymous

      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

      • #156997 Reply

        PKCano
        AskWoody MVP

        I would just leave it alone (and count your lucky stars).

        2 users thanked author for this post.
    • #156999 Reply

      Seff
      AskWoody Lounger

      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.
      • #157001 Reply

        PKCano
        AskWoody MVP

        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.
        • #157046 Reply

          b
          AskWoody Lounger

          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?)

          It would be there. That’s its purpose.

      • #157002 Reply

        SueW
        AskWoody Lounger

        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; Former 'Tech Weenie'

        4 users thanked author for this post.
    • #157005 Reply

      DrBonzo
      AskWoody Lounger

      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.
      • #157049 Reply

        lizzytish
        AskWoody Lounger

        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

        7 users thanked author for this post.
    • #157015 Reply

      rhp52
      AskWoody Lounger

      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.
      • #157020 Reply

        anonymous

        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.
      • #157048 Reply

        woody
        Da Boss

        I keep scanning the Update Catalog, to see if Microsoft has pulled the patch. So far, it’s still there.

        • #157059 Reply

          anonymous

          I have Windows Update set to never download or install, but I check it once a month to see what shows up. Even though Avast has set my Registry Key, WU says there are no updates available for my machine, as of today, Jan. 6.
          Dell Inspiron 3847 (Aug 2015), i3-4170
          Win 7 Prof SP1 x64

          Intel 8 Series / C220 chipset family
          Group B

          EDIT html to text (probably caused by copy>paste not being saved as txt 1st)

    • #157060 Reply

      fpe2fpe
      AskWoody Lounger

      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.
    • #157086 Reply

      Microfix
      AskWoody Lounger

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

      | 1xPC W8.1 Pro x64 Ivybridge| | 1xPC Linux Hybrid x64 Ivybridge| | 1xPC W7 Pro x32 C2D Test Rig| | 1xPC W7 Pro x64 Haswell|
        No problem can be solved from the same level of consciousness that created IT - AE
      1 user thanked author for this post.
    • #157089 Reply

      anonymous

      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.
      • #157204 Reply

        amraybt
        AskWoody Lounger

        Maybe there’s another compatibility issue with older CPUs in general? It seems the older AMD Athlon and Turion chips are most common with BSODs after applying January patches, but I’m not sure.

        -- Lifelong member of Group B --
        Win 7 x64 desktop (Haswell CPU, AMD GPU)
        Win 8.1 x64 laptop (Haswell CPU, Nvidia GPU)

      • #157563 Reply

        anonymous

        anonymous #157089 said:
        It’s a bit worrying that I seem to be the only person reporting a crash with an Intel processor (see stu above). […] Note that it also crashes in the same way with the KB4056897 update.

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

        You’re not the only one (see below). I think those with older Intel CPUs may well have a plausible reason to be concerned. Including users like myself.

        For reference, your Intel Core 2 Quad Q6700 CPU was released in July 2007. Btw is your PC self-built or from an OEM ? If the latter, has the vendor issued a Meltdown-Spectre microcode update for your CPU model ?

        Before I saw your comment, I posted at another askwoody thread about an Intel Core i7 user whose PC went BSOD’ed after installing the Meltdown KB patch.

        As I noted there, Intel Core i7 models range from i7-920 (released: Nov 2008) to i7-960 (Oct 2009).

        Meanwhile, my CPU is Intel Core i5-450M (released: Jun 2010). My laptop’s OEM appears to have no intention of releasing a microcode update for my CPU model wrt the Meltdown-Spectre bug. Likewise, it did not bother to release an update for my CPU model, which is also vulnerable to Dec 2017’s Intel ME bug.

      • #159301 Reply

        anonymous

        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.
        • #159327 Reply

          anonymous

          anonymous #159301 said:
          Intel i7 860, nvidia GPU. similar story, kb4056897 installed (no problem initially), subsequently random BSOD […] I think I’ll uninstall the patch and see if it changes for the better

          Hope to hear better post-uninstall news from you.

          Do you have the compliant registry key & a supported antivirus program version update in place, before installing Microsoft’s Meltdown patch ?

          If yes, I wonder what excuse does MS have in mind wrt various older Intel CPUs being also affected by BSODs … that Intel also provided inaccurate “chipset” documentation ?

          For reference, Intel Core i7-860 was released in Jul 2009.

          • #159401 Reply

            anonymous

            Yes, I have the key (Avast, latest version). It did not help much. Now I have removed the patch, and system is working no problems again, so obviously this was a patch related problem 🙁 Highly possible some features of that processor (and/or chipset), or related drivers either not properly disclosed by Intel, or improperly handled by Microsoft….

    • #157099 Reply

      anonymous

      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

       

      4 users thanked author for this post.
      • #157101 Reply

        woody
        Da Boss

        Interesting. Let me see if I understand. So you take the hard drive from the bluescreened PC, take it to a second, unpatched Athlon, and the second Ahtlon will boot? Once it’s booted on the second Athlon, you uninstall the KB4056894 patch, manually run Windows Update, and uncheck KB4056894. Then you put the hard drive back in the original PC, and the original PC will now boot?

        • #157546 Reply

          anonymous

          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/dscfagc

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

          1 user thanked author for this post.
        • #157549 Reply

          essence_of_dementia
          AskWoody Lounger

          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 1

          OS2: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.

    • #157115 Reply

      James Bond 007
      AskWoody Lounger

      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.

      Hope for the best. Prepare for the worst.

      • #157136 Reply

        James Bond 007
        AskWoody Lounger

        By the way, I went to the Microsoft Update Catalog to download this month’s updates. While I was able to successfully download KB4056894 (Windows 7 rollup), KB4056897 (Windows 7 Security-only) and KB4056898 (Windows 8.1 Security-only), when I searched for KB4056895 (Windows 8.1 rollup) I got the message “We did not find any results for KB4056895”.

        Is KB4056895 not yet released on the Catalog or has it been pulled?

        Hope for the best. Prepare for the worst.

        • #157139 Reply

          PKCano
          AskWoody MVP

          Not yet released. They have released the SO for Win8.1 twice – the latest dated 1/6 I think

        • #157160 Reply

          anonymous

          @james-bond-007

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

          Since you’ve downloaded all the other patches for January, might as well get the patches for IE11 as well (KB4056568), install them and then reboot to see if that changes anything with your Win 7 VM installation. It’s GREAT that you were able to successfully reboot after installing just the Win 7 security patch, but let’s see what happens with the addition of the IE11 patch to the mix. Also might want to install the Dec 2017 rollup (KB4054518) as well and see what happens then.

          So, install KB4054518 and reboot, then install KB4056568 (IE11 patch) and reboot and see if the VM successfully reboots at that point.

          • #157162 Reply

            PKCano
            AskWoody MVP

            I did install both. Just didn’t mention the IE11 patch since it’s not the one causing problems.

            Incidentally, you can install the SO then the IE CU without rebooting in between (if you are not trying to test each patch independently)

      • #157159 Reply

        mazzinia
        AskWoody Lounger

        I have the key set ( avira suppose did it ), but I still don’t see any kind of patch for January , even manually searching with windows update.
        I don’t see even the malware removal for january

        I’m in group B, so I would anyway apply manually later on when is safe, but still I would expect windows update to show what’s new + the malware tool for the month + office ( if office 2010 got some patch this month )

        What’s happening ?

        • #157163 Reply

          PKCano
          AskWoody MVP

          MSRT comes out on Patch Tues which hasn’t happened yet. The SO and Rollup were issued out of band for “emergency” reasons.

          2 users thanked author for this post.
          • #157212 Reply

            Paul
            AskWoody Lounger

            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.

            • #157217 Reply

              b
              AskWoody Lounger

              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.

              2 users thanked author for this post.
            • #157221 Reply

              Paul
              AskWoody Lounger

              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.

            • #157246 Reply

              b
              AskWoody Lounger

              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.
            • #157250 Reply

              Paul
              AskWoody Lounger

              Continuing warm welcome for your view on my opinion. I should apologize for not being more cooperative. Cannot imagine why I would feel that way.

              Yes I did observe how my prior comment did not communicate tone. It would make sense if setting that key was in fact an indication that the responsible vendor has determined the system, and their software, is ready, according to specs provided by Microsoft. But I think field testing has shown what should have become obvious to in-house testing.

              Those specs are insufficient to declare a system ready. Resulting in inoperable hardware.

              If systems are going BSoD even when the MS designed protection engines are giving the all clear and setting the key; then why not just let MSRT do it. My AMD system, protected by MSE, an in-house product, has set the key already. Sometime since last August. Possibly several times since.

              However, by reports widely distributed, I would be foolish to allow this patch onto my system. I will wait for a more stringent test to exclude hazards and assure a clear path ahead.

              My frustration with a flawed test protocol is what prompted the initial post. The salutation of my replies to you are meant to recall a Magrathean style greeting for persistent visitors. This is a popculture/geekculture reference to Douglas Adams’s novel The Hitchhiker’s Guide to the Galaxy. I appreciate your polite request to desist in appearing to be oblivious to meanings of clear intent. Humor was my motivation.

            • #157254 Reply

              PKCano
              AskWoody MVP

              @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.
            • #157261 Reply

              Paul
              AskWoody Lounger

              Thanks, @pkcano , I do get that. And also understand what you meant by MSE/Defender being the ‘native’ ‘replacement’ Antivirus. I continue to not adequately express the frustration of this one check being an inadequate check. That the reports of wasted time spent in recovery shows that additional checks of other conflicts are required. There seems to be a representation that if your AV gives a satisfactory result and sets the key, then all is well. Microsoft’s own protocol is satisfied. Installation clearance given. Go Ahead.

              Reality has shown the protocol is incomplete. And I think it is reasonable to think that 6months or more should have given a better test bed for this discovery.

              If you are pointing out that the AV must abide to new rules to operate conflict-free in the new paradigm after patching, that is clear. But there are more conflicts out in the field. And this single indicator is insufficient clearance to proceed.

              It is actually unusual for Microsoft to be this cooperative with outside vendors. In the past it has been acceptable to simply state that conflicts are the responsibility of the user and their choice of software. To not accept the burden of fixing all cases. But somewhere in this development process, they have missed another, or maybe several other conflicts that result in downtime. I do not know if those conflicts reside in the chip, the engines, or the user-facing interface. And apparently neither does Microsoft.

              Apologies that I was vague in my displeasure.

            • #157266 Reply

              PKCano
              AskWoody MVP

              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.
            • #157315 Reply

              woody
              Da Boss

              The registry key is simply a way for antivirus manufacturers to raise their hand and say that their product doesn’t make any weird kernel calls. That’s all. Has nothing to do with MSRT, Defender, or anything else.

              2 users thanked author for this post.
    • #157146 Reply

      anonymous

      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.
      • #157151 Reply

        Seff
        AskWoody Lounger

        You say “”I have WU set to send but do not install”. I’m not clear whether you have it on “Notify but do not download or install” or “Download but do not install”. You might want to ensure that it is the former, as I have seen reports in the past of the latter setting resulting in updates also being installed rather than just being downloaded.

        • This reply was modified 1 week, 5 days ago by  Seff.
      • #157165 Reply

        MrBrian
        AskWoody MVP

        “Can Windows update differentiate between an AMD system and an Intel system – is this why it is not recommended now?”

        Update Services Privacy Statement

         

    • #157157 Reply

      anonymous

      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.

      • #157176 Reply

        Seff
        AskWoody Lounger

        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.
    • #157193 Reply

      anonymous

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

       

      1 user thanked author for this post.
      • #157558 Reply

        anonymous

        anonymous #157193 said:
        Updated two days ago, so far so good. Group-A, Win7 Home x64, Norton, i3, HP.

        Has HP released (or is it releasing) a microcode update for your Intel Core i3 (what’s the exact model ?) CPU ?

        Ref: Intel Core i3 CPUs release dates = Feb to Sep 2011

        PS: Trying to figure out which older Intel CPUs have been reported as affected (or not affected) by Meltdown KB patch BSOD.

    • #157232 Reply

      anonymous

      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.

    • #157255 Reply

      anonymous

      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+

       

      • #157380 Reply

        anonymous

        I should have said “…was able to…” instead of “…was about to…”  Looks like I got lucky.

        I should have described my machine as Windows 7 Pro with all updates EXCEPT KB4056894 now.

        Also, my AV is ESET Smart Security Suite (up to date).

        P.S. to Woody.  I have tried 3 times now to join but never get a confirmation email.  When I try to join again under the same name, it says there is already an account with that name but won’t let me log it.  For that reason, my posts are “anonymous”.

        • #157385 Reply

          PKCano
          AskWoody MVP

          Check your spamfolder or trash – sometimes the confirmation email ends up there.

          Otherwise, send Woody an email and he can change the password.
          Woody at AskWoody.
          On second thought, might be a good idea to wait a few days – the mail is a flood right now.

          • #157388 Reply

            anonymous

            Thanks PKCano.  I had already checked the spam folder but I did not check the trash folder–things don’t usually end up there on my machine unless I have created an explicit filter.  I’ll check this evening when I get home.

          • #157542 Reply

            anonymous

            Checked the trash folders–nothing there.  I’ll email Woody.

    • #157292 Reply

      Jan K.
      AskWoody Lounger

      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.

    • #157302 Reply

      anonymous

      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!

    • #157308 Reply

      anonymous

      Same Crash here

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

    • #157348 Reply

      anonymous

      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.
      • #157364 Reply

        woody
        Da Boss

        I haven’t seen it reported yet, but man all h$#@ is breaking loose.

        5 users thanked author for this post.
        • #157450 Reply

          geekdom
          AskWoody Lounger

          I believe I’ll wait until after spring thaw to patch.

      • #157567 Reply

        anonymous

        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.
    • #157413 Reply

      Jan K.
      AskWoody Lounger

      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.
      • #157581 Reply

        Bill C.
        AskWoody Lounger

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

        2 users thanked author for this post.
    • #157532 Reply

      anonymous

      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

    • #157578 Reply

      anonymous

      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.
    • #158017 Reply

      anonymous

      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.
    • #158068 Reply

      anonymous

      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.
      • #158076 Reply

        PKCano
        AskWoody MVP

        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.
        • #158679 Reply

          anonymous

          Running on Win7, x64, SP1, Intel i3, Norton AV. I’m a home user, should I run WU? I’m on “never check for WU” so it’s a manual check for me. Would appreciate any advice whether to Run or Not to Run. Thanks.

          • #158736 Reply

            PKCano
            AskWoody MVP

            If you are on “Never check” it doesn’t hurt to “Search for updates”. That just shows you what is available.

            But we are still on DEFCON 2, so you don’t want to install them yet.

            • #159420 Reply

              anonymous

              Thank you PKCano, good advice. I will just hang on then.

        • #158975 Reply

          anonymous

          Both our machines running Avira allowed the update and promptly bricked on reboot!  One was Win7 x64 Intel and the other was Win10 x64 Intel.  The only thing they had in common was Avira.  Will no longer be using Avira, thank you.

          BitDefender and AVG machines didn’t have a problem.

    • #158193 Reply

      anonymous

      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.

    • #158349 Reply

      anonymous

      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.

    • #159665 Reply

      anonymous

      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.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Multiple reports of blue screens (BSODs) 0X000000C4 when installing the January Win7 Monthly Rollup KB 4056894

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information: