Recent Windows Update KB3064209 causes Windows 7 to not boot

Page 4 of 7 FirstFirst ... 23456 ... LastLast

  1. Posts : 3
    Windown 7 Ultimate x64
       #31

    Cetus35 said:
    "I thought an updated UEFI BIOS update was what I might need but when I checked, I already had the newest one. ... Apparently a couple of folks here have gotten their systems to work ... 1 person by updating their BIOS then applying the update."
    Sorry to see that you are still out of a fix. In the meantime, I thought I'd interject a couple small clarifying points:

    The MS update was already in place when I performed the BIOS update. I could not roll the MS update back because I had no restore points, nor had I imaged my drive prior to the MS update. So the MS-KB update was still in place when the BIOS update was applied, after which the system came back up AOK with the MS-KB update still in place.

    One way for you to more closely reproduce my scenario would be for you to roll back your BIOS, install the update, then after the Windows boot-crash, re-update your BIOS. Not sure how constructive or effective that would be, unless there is something peculiar about the order of operations. Weird, yes, especially if it works.
    Last edited by Tone Ranger; 27 Jul 2015 at 13:47.
      My Computer


  2. Posts : 17
    Win7 x64
       #32

    Hah, I didn't even touch my 4.6GHz OC when I installed this update successfully. Manual vcore at 1.345v that passes a 48-hour prime95 blend validation. PLL/VTT voltages are on auto. "Adaptive" vcore won't even post on my z87 sabertooth (pre-this update). Ram is on XMP just below rated 1866. Other hype settings like "asus multicore enhancement" and "SVID control" are on auto (and are very poorly explained I might add.) LLC=level1, cpu spread spectrum disabled (I don't live underneath a power line,) EIST enabled (because it's summer herpa-derpa), and the rest of the c-states disabled (not gonna deal with increased ssd latency.)

    The one downside of owning an Asus board is they simply refuse to release a bios with an "ata password" that would allow for hardware ssd encryption instead of relying on MS's bitlocker which I mean, come on. But that's beside the point here and I'll probably get misquoted again about how this all relates to a bricked boot so I'll stop again.
      My Computer


  3. Posts : 1
    Win 7 Enterprise x64
       #33

    I have a G3258 on a Gigabyte H81M-DS2V latest BIOS F5, not overclocking, and optimized defaults loaded, and installing this update breaks Windows 7 Enterprise x64 for me. It reboots while booting (during the Windows splash screen), and then prompts to try a repair or try booting again, the repair is unable to repair startup. I booted to the Windows install DVD and its repair function also failed to repair. Getting back into Windows is possible with a revert to the preupdate restore point, assuming System Protection (aka System Restore) is on.

    Another thread had some talk that if you disable core #2 it might work, and the problem is something to do with the this cpu's unlocked multiplier, and how windows throttles the CPU to save power and turbo's (supported) CPUs under load.
      My Computer


  4. Posts : 9
    Windows 7 Ultimate x64
       #34

    So does this update actually improve anything for my 3570k? otherwise I am ready to remove it.
      My Computer


  5. Posts : 4
    windows 7 home premium 64bit
       #35

    Great thread.

    I've got this problem on windows 7, and worse still it's carried over to windows 10 - since build 10240 - without any recourse.

    https://www.reddit.com/r/buildapc/co...currently_not/

    I have a g3258 and gb b85m-ds3h r3. Stock or overclock does not matter. Setting the number of cores to 1 does allow windows (7 and 10) to work; this could allow you to at least get into win7 to try to uninstall the update.

    I encourage everyone to report this bug to either microsoft or intel. It's a pretty significant one, but very hard to pin down.
      My Computer


  6. Posts : 17
    Windows 10 Pro x64
    Thread Starter
       #36

    I knew it!

    As you can see from my previous posts I have predicted the the freaking Update KB3064209 update would cause problems in the 'future' (which is now).

    I say cause problems in the future because most of us agreed here before that simply not installing that Update was a 'fix' to the problem of it causing a G3258 processor with Windows 7 to boot to a black screen.

    NOW, the wonderful, shiny, new, Windows 10 INCLUDES THAT UPDATE BY DEFAULT! It's not even an update you can opt out of, IT'S INTERNAL TO WINDOWS 10 !!!!

    Thus, if you try to install Windows 10 on a system with a Pentium G3258 CPU, you will see the much- talked-about 'booting to a black screen'.

    During the attempted Windows 10 install, you only see that problem for a second then the install will fail and revert back to the original Windows 7 (which you have hopefully left the Update 3064209 off of, or it won't boot either).

    The installation fails with this error:
    "We couldn't install Windows 10
    0xC1900101 - 0x20017
    The installation failed in the SAFE_OS phase with an error during boot operations"

    There is much talk on other forums which say that most motherboard companies have known about this for months and have not released an updated BIOS which will reportedly fix the problem. Intel is blaming Microsoft for the problem and Microsoft is blaming Intel, neither of which have issued a fix.

    Reportedly, Intel has agreed to "check into it, but it may take weeks."

    There are only two 'fixes' that occur with some frequency on the forums. Some say that removing ALL overclocking will allow Windows 10 to install successfully (mine still fails the Windows 10 install using this 'fix', by the way) OR to go into UEFI BIOS and disable 1 core of the CPU.

    ALL that have tried this particular bullshit fix say that Windows 10 will install 100% of the time doing this.

    Re-enabling the 2nd core or trying to re-apply any overclock will immediately cause Windows 10 to not boot.


    Did I not say that simply not installing the ****ing update may be a fix for now but it would later come back to bite us in the ass?

    G3258 owners, if you want Windows 10 and you wish to run with more than 1 core of a dual core CPU or to apply an OC to said CPU, you are shit out of luck.




    .
      My Computer


  7. Posts : 1
    Windows 7 Professional x64
       #37

    I just want to post that I have encountered the exact same scenario as the OP on one of my kids' PC. G3258 with ASRock H81M, the KB3064209 update causes Windows boot failure. This caused a major failure for me about a month ago, since I run nightly backups on all PC's I have system restore disabled. For some reason the image wouldn't restore and I ended up doing a clean install, leaving restore enabled. Twice I have run this update and both times it requires a system restore to boot again.

    I also tried to update to Windows 10 but encountered the "We couldn't install Windows 10
    0xC1900101 - 0x20017" installation errror.

    I agree with jdorje, we should all be reporting this error. Maybe we could all report via the same channel and post the link here?
      My Computer


  8. Posts : 4
    windows 7 home premium 64bit
       #38

    GIGABYTE - eSupport

    You can also search "g3258" in the "windows feedback" app on win10 to find a number of related tickets. Most likely simply upvoting them all is the right move.

    Possible fix/workaround for windows 10...for win7 you're better off just not installing that update though. https://www.reddit.com/r/buildapc/co...ly_not/ctnuduk
    Last edited by jdorje; 02 Aug 2015 at 00:18.
      My Computer


  9. Posts : 23
    XP MCE/32/64 Vista 32/64 Win7 Ubuntu Linux Mint
       #39

    Windows 7 installed this update on my AMD notebook (no Intel CPU). I am having the "install failed in the safe os phase" while attempting Windows 10 updates on Win7. Could this update be the culprit. Will uninstalling the update cause problems with my upgrade. I tried it 3 times manually getting this boot error each time. I have the upgrade reserved now.
      My Computer


  10. Posts : 1
    Windows 7 Home Premium 64 bit
       #40

    I have the same problem as described, except that when the "throbbing" welcome item appears on the screen, it stays there and does not proceed to the next step. The only way I can shut down is manually.

    I am not a tech person, but I did figure out that the KB3064209 update was causing the problem and was able to go back to a point prior to its installation, using the "last successful restart" approach. Interestingly, that worked when using system restore would not.

    This is similar to a problem I have had with another update, one related to something that happened with the Russian ruble. I have that update number somewhere. Because it keeps showing up on the update list, I have set my computer to tell me when updates are available, but to install only ones I have selected. Then, I have put that update into "hide" and it stops bothering me. The only problem is that when I do certain maintenance functions, the hiding command gets cleaned out and I have to hide the update again the next time my computer checks for updates. Now, I'm going to have to add KB3064209 to Russian ruble update.

    I use Windows 7 Home Premium, with SP1. I update regularly. My processor is: Intel (R) Core (TM) i5-2450M CPU @ 2.50 GHz. Not being a tech person, that means nothing to me, so I don't know if this is the same type of processor others have talked about or not.
      My Computer


 
Page 4 of 7 FirstFirst ... 23456 ... 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 09:16.
Find Us