Recent Windows Update KB3064209 causes Windows 7 to not boot

ThrashZone said:

I haven't used or tried win-10 on this system but the update loaded on 6/26 on a new build and installed 7 os :/
I'm still flipping coins on win-10 anyway as to how or if I use 10 at all
This issue will go in the negatives section lol :)

Wouldn't win-10 load that update anyway it is an os that picking and choosing updates is not all that possible.

Hi ThrashZone,

What you said is pretty well a summary of this whole thread. Yes, Windows 10 DOES load that 'update' (which is no longer an 'update' in Windows 10, it's built in) and no, you can not pick and choose what to install.

Windows 10's 'Windows Update' completely sucks, too. It checks for updates and if there are any, they get installed. It's no longer broken into 'Important', 'Critical', etc.

Like I said, it's as simple as this, it checks for updates and automatically downloads and installs each and every one that is available.

There are very, very few options regarding Windows 10's 'Windows Updates':
1) Notify you if an update requires a restart,
2) Restart automatically,
-or-
3) Defer upgrades altogether.

That's it.

Here's the happy info regarding what happens if you DARE to question Microsoft's decision to send you what you need, not let you choose what you think you need:

"Some Windows 10 editions let you defer upgrades to your PC. When you defer upgrades, new Windows features won’t be downloaded or installed for several months. Deferring upgrades doesn’t affect security updates. Note that deferring upgrades will prevent you from getting the latest Windows features as soon as they’re available."

So, a pretty dire warning that you had BETTER NOT change the default settings of Windows Update unless you want to miss out on any and all cool new things Redmond packs into Windows 10.

.

alsochuckles said:

We just had another batch of updates install over night (not including 3064209) and guess what? 32 BRIX that wont boot in the same fashion as before.

Anyone know where to these beta bios versions from so I might be able to avoid it again in the future?

Hi alsochuckles,

Good luck with getting an updated BIOS.

The huge majority of posts I've seen by people that installed a 'new BIOS update' to fix their problem are saying that it just makes the computer basically operable. Turns on, works (kind of), turns off. No overclocking, or any other BIOS tweaks, in other words. For the sake of not making a long post longer, that's all I'll say about that. However, just don't think that "I don't overclock, so I'm good to go" is fine, either.

Anyway, I bet I could count on two fingers the number of people that bought the G3258 CPU with no intention of overclocking it. The thing was MADE to be overclocked (just like the Intel i5 and i7 CPUs with 'K' in their name)

EVGA is my motherboard manufacturer and here's what the dummies said to me regarding a BIOS or driver update:

Me:
Hi Chris, as per my subject line, will EVGA be releasing Windows 10 drivers or BIOS updates for the Z87 series of motherboards?

Them: (and this is so weird I can't understand it)
Hello, unfortunately we have no information or news for unreleased products at this time.
We sincerely apologize for any inconvenience this matter has caused.
Please let us know if you have any other questions in order to support you further with your
EVGA Product.


Me:
Hi Gabriel, Are you serious?
You have no information or news for 'unreleased products'?
Windows 10 ships in 4 days from now. Your company has had months upon months to build the
Windows 10 drivers for all your products.
You do have Windows 10 drivers for other products including the X97 Classified and X99 on the driver and BIOS download page so how can you consider Windows 10 (specifically it's EVGA product drivers)
to be an 'unreleased product'?
Are you implying that if Windows 10 were released, THEN you would have drivers for my product?

Them:
Hi,
We apologize for the confusion, Windows 10 should automatically install all the necessary drivers to have a working system; there is no need to download additional drivers since it's a motherboard. Furthermore, only video cards require specific Windows 10 drivers.


So there you have it. My motherboard doesn't NEED a BIOS update nor even drivers for that matter. Silly me.

In fact, these guys didn't know what they were talking about because Windows 10 did not install several of my drivers. NIC, Bluetooth, sound, and even the chipset, for God's sake. It did, somehow or the other, install a brand spanking new just-released video driver.

Luckily I had seen on some forum or the other that some guy had used Windows 8.1 drivers in Windows 10 with a great deal of success. I tried it and sure enough they all worked.

Anyway, even if your mobo manufacturer DOES release a BIOS update, it's likely that it will be some crippled up shabby piece of code that indeed allows you to install Windows 10, but a lot of previously available BIOS settings grayed-out (just read the forums of people complaining about this exact thing).

(I still can't get over that "We have no news for unreleased products" debacle. lol)



.

I had exactly the same problem on my ASUS GL502VS. Tried everything, but didn't work. After every failure the system would soft-reboot and I would get a 0xc000000f error (Boot media selection failed). Then I would do a hard reboot not expecting it to boot, but for some reason it would boot successfully and the setup would continue to restore my previous windows version.

(Btw, I had the system restore turned off so the setup was restoring using it's own backups created during installation, rather than a restore point)

After attempting many things, eventually the following worked.

1. Install latest BIOS from ASUS that is supposed to fix the Intel micro code issue.
2. After update disable SMART from BIOS.
3. Use Microsoft Media Creation tool to update windows.
4. Stay vigilant and upon every soft-reboot by Windows setup, go into BIOS and choose Save and Exit, hence forcing a hard reboot.

I also tried normal windows update at step 3 above, but it failed. Not sure if one or more of the above steps was necessary, but this is what worked for me

Before above solution, I tried every solution provided by MS at below link (except the last one of course )but nothing worked, however some parts may have contributed towards the fix that I may not be able to identify. So if above doesn't work, try all solutions at below link, followed by the above solution.

https://support.microsoft.com/en-us/...-update-errors

Hope this helps.