Thursday, May 5th 2016
Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards
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.
Sources:
InfoWorld, Forbes
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.
46 Comments on Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards
But just how far can it go........................
Anyway is still a RED brick :banghead: sneaky MS My grandson, his name is Mason LOL, and he's pretty good boy !:toast:
was
UPGRADE TO WINDOWS 10
www.theinquirer.net/inquirer/news/2457031/updategate-microsoft-suggests-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
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!!!! )
then the system proceeds to repeatedly crash with little chance of restoring
Microsoft suggests updating to Windows 10 to patch Windows 7
@ChrisTheDJ
- Tweet
- Facebook
- Google plus
- Send to
9 CommentsMICROSOFT 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 obsolescenceto 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
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.
I also have the option of never checking for updates. W7 OEM. Home Premium