Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards

[btarunr]

Microsoft inadvertently bricked a vast number of PCs running Windows 7, by changing the priority of an erroneous software update. Earlier this month, Microsoft changed the priority of an obscure-sounding security update for Windows 7 from "Optional" to "Recommended," (which by default gets automatically downloaded and installed). This update, KB3133977, bricks machines running ASUS motherboards, in the UEFI mode.

Windows 7 inherently does not support Secure Boot, a feature introduced with Windows 8, which takes advantage of UEFI to provide users with a layer of system integrity throughout the boot process. With KB3133977 installed on Windows 7 machines that use UEFI boot, the motherboard senses a Secure Boot violation, and invalidates the boot device (refuses to boot from it). ASUS recommended a BIOS setting with which you can deactivate Secure Boot while making your motherboard continuing to boot in UEFI mode.



View at TechPowerUp Main Site

 

[DeathtoGnomes]

Woohoo! Moar Bricks! Anyone know a good mason ?

 

[ZoneDymo]

Woohoo! Moar Bricks! Anyone know a good mason ?

Bran the builder....wait no he is long gone...maybe his descended Bob?

 

[kylee]

This is exactly why I disabled both Secureboot and Win update on Windows 10.

 

[revin]

This is exactly why I disabled both Secureboot and Win update on Windows 10.

I think It's a Windows 7 issue mostly Asus [micro code ???]
But just how far can it go........................

Anyway is still a RED brick sneaky MS

Woohoo! Moar Bricks! Anyone know a good mason ?

My grandson, his name is Mason LOL, and he's pretty good boy !

 

[TheinsanegamerN]

Another microsoft update bricking systems, and people wonder why I dont like the idea of windows 10 updating automatically, THIS IS WHY. Especially considering some OEM machines permanently enable secure boot, an update like this would be devastating.

 

[dorsetknob]

Apparently Microsofts response to the bricking of Asus based motherboards on Win 7
was

UPGRADE TO WINDOWS 10

 

[AsRock]

Another microsoft update bricking systems, and people wonder why I dont like the idea of windows 10 updating automatically, THIS IS WHY. Especially considering some OEM machines permanently enable secure boot, an update like this would be devastating.

And wait until viruses\malware do it, and now more script kiddie's know about it they be looking more than ever now.

 

[TheGuruStud]

Apparently Microsofts response to the bricking of Asus based motherboards on Win 7
was

UPGRADE TO WINDOWS 10

I don't doubt that this could be the end of an official response by m$. They're that stupid and arrogant.

 

[dorsetknob]

One source to view this problem
http://www.theinquirer.net/inquirer...sts-updating-to-windows-10-to-patch-windows-7

There are plenty of other sources saying basically the Same thing

PS reading between the lines Microsoft are saying F^^^k you win7 Retard we are not intrested in fixing this
Suck it and DAMM well UPGRADE TO win 10

 

[Static~Charge]

PS reading between the lines Microsoft are saying F^^^k you win7 Retard we are not intrested in fixing this
Suck it and DAMM well UPGRADE TO win 10

To which my response would be "Observe my middle finger while I install Linux Mint, you a$$holes."

 

[Drone]

I guess they need a new short error message 'shit happens, upgrade to W10'

 

[xvi]

So, this only happens on ASUS boards, but it's a Microsoft issue? Sounds like an ASUS issue.

 

[dorsetknob]

@xvi
you are incorrect and correct at the same time
It happens to Asus Boards and Boards manufactured by Asus for other OEM makers
and yes its a problem for both Asus and Microsoft ( not our Problem they say upgrade to win 10 you bitch problem solved!!!! )

 

[newtekie1]

I have to wonder how many are actually running Win7 in UEFI mode, I'd bet a good 90% of Win7 installs are using the CSM not native UEFI.

 

[dorsetknob]

running Win7 in UEFI mode, I'd bet a good 90% of Win7 installs are using the CSM not native UEFI.

That appears to be the gist of the problem the update forces UEFI on the system where its not set up for it
then the system proceeds to repeatedly crash with little chance of restoring

 

[newtekie1]

That appears to be the gist of the problem the update forces UEFI on the system where its not set up for it
then the system proceeds to repeatedly crash with little chance of restoring

I don't think so. That isn't how UEFI works. A boot device that is set up for legacy boot can't just switch to UEFI boot. In fact, if you look at the partition structure created when installing a UEFI windows vs. a legacy windows, you'll see they are much different. There is a partition specifically for UEFI that doesn't exist on legacy installs of Windows.

With KB3133977 installed on Windows 7 machines that use UEFI boot

As far as I can tell, Windows 7 already has to be set up for UEFI boot.

 

[dorsetknob]

Microsoft suggests updating to Windows 10 to patch Windows 7

• 
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer

 

[dinmaster]

i personally think its just a ploy to push people to windows 10, if the pop ups weren't enough. this, which probably is the first of many to hit the older operating systems will try and push people to windows 10. nice one microsoft, just my 2cents

 

[Ruru]

But why still use Win7? For me, it's like some people still continued to use XP when 7 (and even when SP1 for 7) came out.

 

[Caring1]

But why still use Win7? For me, it's like some people still continued to use XP when 7 (and even when SP1 for 7) came out.

Because unlike XP, there is nothing wrong with W7, Microsoft continues to churn out new products to keep consumers paying.
I continue to use W7 because I can control updates, without a hack, everything works and works well.
It is no less secure than W10, despite the fear mongering by Microsoft and their lackies.

 

[uuuaaaaaa]

Forced obsolescence...

 

[huguberhart]

Because unlike XP, there is nothing wrong with W7, Microsoft continues to churn out new products to keep consumers paying.
I continue to use W7 because I can control updates, without a hack, everything works and works well.
It is no less secure than W10, despite the fear mongering by Microsoft and their lackies.

Apparently, you can't control updates, even on Windows 7 Home, as it is written in the article. If you have Pro version then it's a different matter for Windows systems.

 

[Caring1]

Apparently, you can't control updates, even on Windows 7 Home, as it is written in the article. If you have Pro version then it's a different matter for Windows systems.

Mine is set to notify me but not to download or install.
I also have the option of never checking for updates. W7 OEM. Home Premium

 

[R-T-B]

This is easily fixable by a bios setting. The definition of "brick" must've changed while I wasn't looking...