Recent Windows Update KB3064209 causes Windows 7 to not boot

Page 3 of 7 FirstFirst 12345 ... LastLast

  1. Posts : 63
    Windows 7 Ultimate 32 bit,Chromium OS, windows server 2008 32bit
       #21

    run a system repair in recovery?
      My Computer


  2. Posts : 17
    Win7 x64
       #22

    Cetus35 said:
    Ok, I have it working now
    I never said quoted text. I got spooked because there was multiple people in here with the same cpu and the problem of windows bricking. I generally hate system restore because that's where maleware can hide and it eats up ssd space. The "winsxs" folder is bad enough on an ssd. The only thing I did was made sure I had the precautions on, installed the update, then everything is fine. Like I said, just spooked because of similar hardware and MS's tendency to never properly explain what an update does -- to any sufficient degree. Wanna know my hidden updates so Win10 nagware never appears? Well here they are:

    • kb2952664
    • kb2990214
    • kb3021917
    • kb3050265
    • kb3065987
    • kb3068708
    • any "Windows Malicious Software Removal Tools" because I doubt they're still scanning for worms from 2004 (MS Blaster, Sasser, Mydoom) as claimed in every month's description of the update.

    ^Some of those might be MS/NSA spyware as well versus simply win10 nagware. I apologize for detracting from how solve your problem of a bricked windows boot. Maybe windows isn't the OS for me.
    Last edited by jewishnigra; 11 Jul 2015 at 13:37. Reason: forgot to add kb2952664, this one is NOTORIOUS for "un-hiding" itself
      My Computer


  3. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #23

    Members are just making suggestion on how to get someone back in working order before the problem with the KB.
    Restore point and other methods posted may or may not help. One just has to decide to try the suggestion or not. I personally have lots of restore point that are handy for such problems.


    Take a think on this.

    When was the last time Microsoft had a update that messed with how a Intel processor did it's job before this one.? The best I can remember they never have.

    Why would anybody want Microsoft to be messing with a Intel or AMD cpu in any fashion?
    Because Microsoft is pushing Windows 10 they are doing a lot of strange KB's to Windows 7 updates so one must be watchful of all Windows 7 updates.

    When I want to investigate my Intel cpu I do it the old fashion way.
    I will check with Intel and/or Asus my motherboard manufacture for bios information. Surely not Microsoft. That was my thinking so I didn't install the KB.

    Now here comes more guidance from a simple person, ME.

    When you see a update that sound a little strange or you don't understand just post and ask a question or read through the threads and see if any other member is having problems or questions with the KB update.

    This complete post is just my opinion nothing else. Some will agree and some will not.

    Layback Bear
      My Computer


  4. Posts : 17
    Windows 10 Pro x64
    Thread Starter
       #24

    jewishnigra said:
    I never said quoted text. I got spooked because there was multiple people in here with the same cpu and the problem of windows bricking. I generally hate system restore because that's where maleware can hide and it eats up ssd space. The "winsxs" folder is bad enough on an ssd. The only thing I did was made sure I had the precautions on, installed the update, then everything is fine. Like I said, just spooked because of similar hardware and MS's tendency to never properly explain what an update does -- to any sufficient degree. Wanna know my hidden updates so Win10 nagware never appears?^Some of those might be MS/NSA spyware as well versus simply win10 nagware. I apologize for detracting from how solve your problem of a bricked windows boot. Maybe windows isn't the OS for me.
    @ jewishnigra

    I apologize for misquoting you. It won't happen again.

    However, I at least partially stand behind my paraphrasing because although you didn't say word for word "Ok I have it working now" you did say "after installing this update, my system appears to be fine."

    On this last post you're talking about the NSA and Win10 nagware.

    Are you saying that you installed the problematic update (KB3064209) on Windows 10?

    This thread is concerned with the combination of Windows 7, Windows Update KB3064209, and the G3258 Intel Pentium processor causing the system to boot to a black screen. (Although it does in fact successfully boot to the Desktop because you can hear all the normal Windows sounds going on when it does. The screen is just black.)

    When I first posted the orginal question concerning this matter I kind of expected someone to say "You have to install KB so-and-so first" and that would be that.

    Instead, come to find out that it's a widespread problem that a lot of people are having with this update.

    Per Layback Bear, I'm just simply not going to install it again. Like I've said before, I'm just concerned with two matters:
    1 - What exactly does Microsoft mean that the operating system may be unreliable without it and,
    2 - That a future critical update will fail to install because this one is not installed.

    Until then, heck with it.


    @Layback Bear
    Microsoft has released at least 3 updates/hotfixes regarding processors since 2010, that I know of. I've been scolded for misquoting :) so I'll put in a disclaimer that you said "updates" and "Intel processors".
    1 - KB2493989 - Intel microcode - Windows 7 & Windows Server 2008 R2
    2 - KB936357 - Intel microcode - Windows XP, Windows Server 2003, and Vista (all versions)
    3 - KB2818604 - AMD microcode - Windows Server 2012, Windows 7 & 8.

    I fully agree with what you said about not allowing Microsoft to fiddle around with processor microcode but
    here's their apparent take on that issue (https://support.microsoft.com/en-us/kb/936357 bottom of the
    page, right above where it says "Properties").
    Per Microsoft:
    "The processor manufacturer may use microcode updates to address errata and to make sure that operational behavior is correct. Windows operating systems include a microcode update mechanism that supports Intel processors. This mechanism lets the operating system apply the latest microcode updates to all processors in the system.

    Operating system updates make it possible to apply microcode updates that are later than the versions in the system BIOS. If the processor uses the most recent microcode version, the Windows microcode update mechanism takes no action."

    I'm not 100% sure that I like the idea of that. Microsoft applying microcode newer than the latest BIOS?

    If that were a good idea, why do we check our motherboard manufacturers websites all the time for BIOS updates when Microsoft can just do it with Windows Updates?

    AND, as all of us here know from personal experience with this KB3064209 microcode update BS, it's NOT a good idea.

    As you suggest, the websites of Intel, AMD, and your particular motherboard manufacturer are the legitimate places to check for any "microcode" updates.

    If they don't have any and Microsoft is saying "We have one for you" it is just a little suspect, like you mentioned.

    Thanks for your input. Valuable information for all.


    .
      My Computer


  5. Posts : 50
    Win7 Ultimate Enterprise 64bit
       #25

    I passed on this firstly because there was no mention of specifically which Intel processors the update applied to,and because I never install any updates without searching online first.So,damn good thing I Googled up this little gem,huh?
    Now,it might fly for me because I'm running an older Pentium T-4300,but I'm not going there because "If it ain't broke..."

    Cheers
      My Computer


  6. Posts : 2
    Windows 7 64bit
       #26

    Same problem here, I have a MSI H81m E33 with Pentium G3258 overclocked 4.2@ 1.120v and today it wouldn't boot to windows so I was thinking I needed more vcore so I booted to bios raised vcore in like 0.02v increments right upto 1.25v but still not boot to windows, Reset bios to defaults and windows booted no problem, then I remembered yesterday KB3064209 said CPU microcode update, When I removed KB3064209 windows booted with my overclock no problem, so I wont be putting KB3064209 back.
    Just adding my 2 cents also
    jonny
      My Computer


  7. Posts : 3
    Windown 7 Ultimate x64
       #27

    Fixed on MSI Z97 PC-Mate MOBO


    Found a fix, at least on the MSI Z97 PC-Mate MOBO. This board was exhibiting the exact same issue as the original poster - G3258 in a death loop during windows boot after installing the vile KB3064209 update. This one had me stripping out all hardware (though not any hair, thank goodness), even attempting a PCIe card to bypass the on-chip GPU, all to no avail. To make matters worse, I had already done a lot of configuration and installation that I did not want to repeat, but had not gotten around to backing up the system (I know, I know... face-palming).

    A couple of bright spots that gave me hope: the system would boot into UEFI BIOS (which is really very nice, BTW), and I was able to boot into the memtest86 utility - which passed with flying colors. At that point I looked and saw that the BIOS was a bit out of date. So as a last-ditch attempt before reformatting, I downloaded the latest recommended BIOS (4.9 - the latest one) onto a USB stick and installed it through the (brilliant) M-Flash utility built right inside the BIOS.

    After successfully completing the flash, it rebooted, and Eureka! Windows came back. I now leave you all with the hope of similar success - either with this board or one with a BIOS update available that also has the same sort of fix.
      My Computer


  8. Posts : 2
    Windows 7 64bit
       #28

    Nice fix


    Nice fix, that wouldn't have worked for me because I am already on latest Bios, removing the update will do for me though!
      My Computer


  9. Posts : 1
    NEVADA
       #29

    Pentium G3258 Win 7 Boot loop After Update 06-07/15


    I figured it out guys!!



    so im not sure when the updates came out though it was around this summer 15 and not sure if any one here has figured it out yet sorry no time to read 3pgs of replies..

    any ways i have had this issue with 2 systems both with the pentium g3258 and 270x gpu installed some updates after messing with some fans then bam continuous cycle ITS YOUR OVERCLOCK GUYS

    disabled my oc and was able to boot into windows and remove and hide the updates that caused the issue and then loaded my OC profile and was up and going, luckily for me (first thing i tried) i figured the OC was keeping it from finishing the install after the restart (possibly unstable) so i took it off, later i found that with the update installed, the pc refused to boot with an OC sad i know lemme know if you guys have any ? or what not like i said i have @ of the pent gs and can run test and what ever :) hope this helped
      My Computer


  10. Posts : 17
    Windows 10 Pro x64
    Thread Starter
       #30

    Hi all,

    @ Tone Ranger
    "Found a fix, at least on the MSI Z97 PC-Mate MOBO. ... After successfully completing the flash [BIOS update], it rebooted, and Eureka! Windows came back."

    I thought an updated UEFI BIOS update was what I might need but when I checked, I already had the newest one.

    @SkrillZilla
    "ITS YOUR OVERCLOCK GUYS ... disabled my oc and was able to boot into windows and remove and hide the updates that caused the issue and then loaded my OC profile and was up and going."

    That's the very first thing I thought was causing the problem since OC'ing can cause ALL sorts of weird things to happen if it's not completely stable. SO I removed all overclocking, rebooted, and installed the update again and boom, same problem right back again. So removing my OC didn't help.
    In fact, having Windows run right (i.e. not installing that freaking update), I have set all my OC back with no problems whatsoever. (4.30GHz (up from the stock 3.20GHz), 1.125V, with nothing else changed.) I evidently lost the RAM lottery because even though it's name brand with a great reputation, if you even THINK about a RAM OC, it won't boot.

    For anyone who is doing like some others and, for TL;DR reasons, skipping straight to the end of these posts without reading what has happened in the meantime, here's what this original post concerns:
    If you have a combination of an Intel G3258 Pentium (Anniversary Edition) and Windows 7 and install a Windows Update that came out this June (2015), specifically KB3064209 (Intel Microcode Update), Windows will not boot to the Desktop. It will show a black screen instead which happens immediately after the 'Starting Windows' screen.
    Saying it won't boot to the Desktop is kind of a misnomer because it DOES in fact continue to boot to the Desktop, you just can't see it.

    Apparently a couple of folks here have gotten their systems to work with it by 1 person turning off all overclocking settings then installing the update then reapplying the OC settings and 1 person by updating their BIOS then applying the update. All others have failed to find a fix.


    .
      My Computer


 
Page 3 of 7 FirstFirst 12345 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:50.
Find Us