Recent Windows Update KB3064209 causes Windows 7 to not boot

I also have a computer with a Pentium G3258, and I had the same failure to boot as others have reported, right after I tried to install KB3064209. In my case, I was lucky enough to have a recent backup of the C drive with Acronis True Image, so I restored it. I had originally installed three different updates with Windows Update at the same time, so after restoring the hard drive, I went back and installed them one by one, and only KB3064209 caused the problem to recur. Also, I have two other computers with nearly identical software installed, and both of them had different CPUs, and they both ran the KB3064209 update with no problem. So the logical conclusion is that that particular patch is not compatible with the Pentium G3258. Has anybody else had a similar problem with KB3064209 with a CPU other than the Pentium G3258?

Many years ago I learned one important lesson concerning any type of hardware fix from Microsoft, DON'T INSTALL IT, chances are it will crash your system. Instead go to the manufacturer's website to see if they have any recommended updates for the hardware mentioned in the Microsoft "fix".

In a couple of cases, the manufacturer did have a fix for my particular hardware component but after installing their fix Microsoft Update still insisted they had a fix. Just for sh$%^ and grins, I installed a couple of them and sure enough, my system crashed.

Bob - Retired IT Professional 46 yrs

Since there hasn't been a single person yet in this thread who reported a successful installation with this update and a g3258 as their cpu, I'm looking for backup options and need help choosing the least painful and (somewhat) easy ones. I don't have a lot of hdd space to store a full image of the C drive (although the C drive is only a 128GB SSD.) I also don't have an optical drive either (lol -- they said it was antiquated technology by now, like floppies.) Here's what I'd like to do (in case the update bricks the system, even safe mode) and see if this remotely possible:

• re-enable MS "System Restore/Protection" (I've had so much God-awful trouble with it in the past so I disabled it)
• make a single restore point right before installing this update
• convert an available 8GB usb drive as a "MS recovery cd"
• copy the restore point over to the usb drive as well (so the MS recovery can "see" the restore point when it runs)
• if the update bricks the system, restore from the restore point and then boot into Windows right before you isntalled the update

Remotely possible? A better option?

jewishnigra said:

• re-enable MS "System Restore/Protection" (I've had so much God-awful trouble with it in the past so I disabled it)
• make a single restore point right before installing this update
• convert an available 8GB usb drive as a "MS recovery cd"

Ok I've done these items already with the help of this guide, (note in step 5 of that guide: "FORMAT FS=NTFS" should be replaced with "FORMAT FS=NTFS QUICK" -- otherwise you're gonna be needlessly sitting there for hours and hours.)

Now I have a re-enabled system restore and made a restore point, but it's sitting on the C drive so I'm assuming if the system is bricked, it SHOULD see and revert back to that restore point on the C drive right? (It's only 360MB btw.)

Layback Bear said:

Yes Restore Points should be on the "C" partition.
If the drive dies you will need to use a Backup you have made on a external drive.

Well, in this case we're just talking about a rogue update that can potentially brick a system, not kill a drive. Although, given my luck with System Restore, it probably won't work anyway, ESPECIALLY when switching to a new drive that isn't the same capacity/model/ssd/etc.

Isn't the answer to this issue not to install what is only an optional update? It simply isn't worth the risk unless you have a specific reason for installing it.

Seffrid said:

Isn't the answer to this issue not to install what is only an optional update? It simply isn't worth the risk unless you have a specific reason for installing it.

Well I mean if there's true "performance enhancements" as Microsoft claims that results in a faster OS, then I don't want to miss out on that, especially for my lowly $45 cpu that's only a dual-core Hawsell. I'd like to hear Intel's side of the story though to see if they agree.

How many people NEVER install "optional" updates regardless of what the KB articles say? 50%?

Ok, after taking the necessary backup precautions and after installing this update, my system appears to be fine. I'll let you guys know if I run into trouble in the near future. Thanks for the support along the way. #sarcasm

@ jewishnigra

Since you're the one and only person here who says they have successfully installed the KB3064209 (Intel microcode update) with an Intel G3258 processor, it sure would be very handy if you could describe here what you did to accomplish that.

I mean "Ok, I have it working now" is not the most helpful post in the world :)

You did say that you had taken steps to ensure a good backup before an install attempt, but just about everyone here has done that and it hasn't helped a single thing.

Somehow this thread has wandered away from the original problem posted and has almost (but not completely) become a discussion on how and why to make Restore Points, emergency recovery CDs/USB flash drives, and regular backups.

Part of that may be my own fault because I did veer away from the topic myself earlier in recommending everyone always use System Protection and the fact that it wasn't a good thing to turn it off.

Ok, to gets things re-clarified:

When you have an Intel G3258 CPU (aka the Anniversary Edition Pentium) AND install an 'Optional' update
suggested by Windows Update, specifically KB3064209 (named 'Intel microcode update'), then upon a reboot your computer boots to a black screen and restarts.

The only way to get it to boot normally is to remove the update via System Restore, reverting to an earlier backup, or booting with a recovery CD/flash drive, etc.

Do take notice that booting with a recovery CD/flash drive results in the exact same fix as when it comes to the 'automatic problem fixer' that sometimes starts automatically after a failed boot.

They both resort to using a System Restore Point.

So like I said earlier, if you have System Protection turned off, neither of those methods will result in fixing the problem i.e. boot like normal.


Last note: All of us here admit that not installing the thing would prevent all the problems, but although Windows Update has it listed as an 'Optional' update, the description for the update sounds ominous:
(and there are also concerns that future Windows Updates may demand that this update is installed as a prerequisite)

"This update improves the reliability of systems that use certain Intel processors. This update also fixes
some issues that could cause the operating system to function incorrectly."

Without it, the operating system could possibly function incorrectly and be unreliable!?

I mean, that's what the worst virus in the world does, causes your operating system to "function incorrectly and be unreliable".



.