Though we don’t normally report on Windows updates, we’ll make an exception on this one. AMD sends word this evening that they are advising users to remove update KB3004394, which was released as part of this week’s Patch Tuesday, due to driver installation issues this update is inflicting.

The update, designed to update Windows’ root certificate store, has apparently been causing havoc on some Windows 7 configurations. In AMD’s case what they are finding is that the update prevents the installation of new graphics drivers on affected systems, with both AMD and NVIDIA drivers refusing to install. More broadly, Infoword is reporting that KB3004394 is also being blamed as the culprit behind certain issues affecting Windows Defender, Task Manager, and other software.

At this point this looks like the update only affects a small number of systems – Windows 8 is not affected, and even then most Windows 7 systems appear to be fine – but Microsoft has not taken any chances and has pulled the update. In the meantime for those users that are affected, uninstalling the faulty update reportedly fixes the issue.

Source: Microsoft

POST A COMMENT

50 Comments

View All Comments

  • cbuchach - Friday, December 12, 2014 - link

    Yes the MS update was the issue. I uninstalled it and re installed the Catalyst software and now the driver can successfully load. What a disaster and huge waste of time and money..... Reply
  • optimus1883 - Friday, December 12, 2014 - link

    Same issue and result here, it was very confusing since I have been changing a few things on my HTPC recently. Reply
  • Vault76 - Friday, December 12, 2014 - link

    Both of my Windows Media Center PCs stopped working this week and it has been driving me crazy. I'm glad this was posted. One has an Nvidia card and one has an AMD card though. Both are having Playready issues on encrypted channels and "display driver errors" on clear channels. I'm not sure what the issue is yet but it seems like too much of a coincidence that they both stopped working this week. Reply
  • aodxxl - Friday, December 12, 2014 - link

    The update also Screws with Autocad 2010 . After the update the program refused to start and gave me allot of headaches untill i read about ths update. Reply
  • ssddaydream - Friday, December 12, 2014 - link

    This update also kills the ability to install any other Windows updates after it, causing any new update to fail. I reformatted my machine, and alas, ran into the same thing after installing the updates. I only figured it out because of some forum member on some site posting about the error.
    Definitely lost some sleep to this one...
    Reply
  • yannigr2 - Friday, December 12, 2014 - link

    If drivers from both AMD and Nvidia are not installing and other issues are reported, why the hell is AMD's name on the title? Don't you know that putting AMD's name in the title gives the impression that
    "Oh look! AMD's drivers problems again. HAHAHA".

    Stop creating bad image for this company for no reasons. You should have the opposite attitude except if you hope for monopolies in the future.
    My God. We had Ubisoft, now we have Anandtech too...
    Reply
  • yannigr2 - Friday, December 12, 2014 - link

    And this title comes after AMD's Omega drivers where published. Coincidence? Sure.... Reply
  • Ryan Smith - Friday, December 12, 2014 - link

    This literally came at the request of AMD, who asked that we inform our users about this. So I am giving them source credit where they are due. Reply
  • yannigr2 - Friday, December 12, 2014 - link

    In that case I own you an apology.
    I am sorry for my comments.

    As a second comment I would have to say that they are morons. I have to give them credit for been honest and thinking their customers, but they are morons when they put their name next to a Microsoft's problem voluntarily.
    Reply
  • prime2515103 - Friday, December 12, 2014 - link

    They did it because of the driver being released on patch Tuesday. Everyone was blaming AMD for a bad driving when it had nothing to do with the quality of the driver (this problem effects all drivers, not just AMD, among other things [that involve root certificates]). Reply

Log in

Don't have an account? Sign up now