There are many good reasons to use the new UEFI Secure Boot under Windows 10 but there are also numerous reasons not to. The latest is an issue with a specific Windows Update patch which was recently changed from an optional update to a recommended update. For systems using an ASUS motherboard and running Windows 7 this can be a bit of a bother as your Secure Boot will report that the OS has unauthorized changes and will refuse to boot. If you can get at your UEFI BIOS you can change the OS Type from Windows UEFI mode to Other OS in the boot menu. If this does not resolve your issue The Register has been told you should contact ASUS for support, as opposed to Microsoft since the issues root cause lies in a feature similar to Secure boot which ASUS added to their boards.
"Windows 7 machines that have installed Microsoft's KB3133977 update may trigger a "secure boot violation" during startup, preventing the PC from loading the operating system, Asus said."
Here is some more Tech News from around the web:
- Microsoft: Windows 10 Will Remain Free For People With Accessibility Needs @ Slashdot
- 3D Printing Bone @ Hack a Day
- Acer to launch gaming smartphone in 4Q16, says paper @ DigiTimes
- IBM's POWER cloud powers up almost a year later than promised @ The Register
- A Look At NVIDIA's GeForce GTX 1080, GTX 1070 & New Technologies @ Techgage
- Doom (2016) running on GTX1080 @ Kitguru
- NVIDIA's GTX 1080 & GTX 1070 Detailed @ Hardware Canucks
- Nvidia editors day event gallery featuring GTX1080 @ Kitguru
- AMD's Andrej Zdravkovic @ Kitguru
- TRENDnet TPL-421E2K Powerline 1200 AV2 Adapter Kit Review @ NikKTech
- Luxury all paid trip to see Independence Day 2 in London
[get ready for incoming
[get ready for incoming anti-Ms sh!tstorm]
Here plenty of ANTI-M$
Here plenty of ANTI-M$ sh!tstorm from across the pond! To go along with the ANTI-M$ sh!tstorm from this side of the pond! And each article has over 100 posts, mostly M$ sh!tstorm! posts! Which can be added to MY ANTI-M$ sh!tstorm post! I just had a bathroom ANTI-M$ sh!tstorm! It came out very M$ smelling, started out like soft serve but transitioned to more liquid like stinky M$ smelling sh!tstorm!
Now we need of a M$ ANTI-Trust sh!tstorm! From the ANTI-Trust Division of the US Justice Department, to stop all of this cornering of the third party PC/laptop OEM OS/APU/Firmware/Other market by M$ and its illegal sh!tstorm!
“Microsoft half-bricks Asus Windows 7 PCs with UEFI boot glitch”
http://www.theregister.co.uk/2016/05/06/microsoft_update_asus_windows_7/
“Official: Microsoft’s ‘Get Windows 10’ nagware to vanish from PCs in July”
http://www.theregister.co.uk/2016/05/06/windows_10_update/
That’s funny, considering it
That's funny, considering it is an ASUS issue.
Not really, when you consider
Not really, when you consider M$’s UEFI secure Boot antics with some Linux Builds! He(M$) who controls the software/OS key signing authority on the UEFI firmware on third party PC/Laptop OEM produced products controls what OS/software can run on that third party OEM PC/Laptop hardware!
Especially for the any new PC/laptop OEM hardware where the OEMs have the “option” of not providing a M$ windows secure boot [OFF] switch in their product’s UEFI, on any third party produced OEM PCs/Laptops that come with windows 10 factory installed!
I’ve had this occur 5 times
I’ve had this occur 5 times in the last 3 weeks. Pretty annoying for the customers. All affected had no plans on upgrading to 10.
I encountered this problem a
I encountered this problem a couple of weeks ago with my HTPC. After a Windows update booted straight into the UEFI without a warning (haven’t updated the UEFI for almost 2 years).
To resolve the issue I first set the OS type to “other” and rebooted successfully into Windows 7. Then went back into the UEFI and set it to forget the cryptographic signatures. After that the PC boots properly again with secure boot enabled.
As expected, MS are getting
As expected, MS are getting flack for an issue caused by Asus. Secure Boot state is never something that should be toggled automatically, as doing so rather defeats the entire point of Secure Boot.
Is that you Ed, FOR M$, BOTT!
Is that you Ed, FOR M$, BOTT! He’s the BOTT that’s Paid a LOT to SPIN things Redmond’s way!
There are many VALID reasons to NOT ever TRUST the M$ OS/Firmware/API Standard OIL type of TRUST when it comes to M$’s windows secure boot market cornering apparatus built into the third party independent PC/Laptop OEM’s PC/Laptop UEFI/firmware!