Windows 10: how much can I sue microsoft for if windows update bricks my UEFI firmware?

If windows update renders my Lenovo Legion 5 15ACH6H useless like the one in this video, how much can I sue microsoft for?https://www.youtube.com/watch?v=oPvm4B4s2Cw

:)

 

Microsoft Surface Pro 4 UEFI Firmware driver installs but firmware does not update

Microsoft Surface Pro 4 UEFI Firmware driver installs but firmware does not update

• The OS is Windows 10 Version 1607
  
• Current version - Surface UEFI firmware: 106.1624.768.0
  
• Attempted update - Surface UEFI firmware: 107.1741.768.0
  

The UEFI Firmware driver window shows the following after installation and two subsequent restarts:

The UEFI Firmware driver window shows the following after installation and three subsequent restarts:

Attempts to install the UEFI firmware through the Surface Installer and manually in the device manager have installed the driver but the firmware does not install upon restarting. After restarting twice, the driver reports that it is a different version than firmware on the device and stops presenting an option to restart.

Installing Surface Pro Firmware with WinPE on a USB drive also does not result in the UEFI firmware being installed, though another firmware update successfully applied via this process the first time the device rebooted from WinPE.

The driver can be rolled back to the version which matches the actual version of the firmware.

Searches on other forums suggest that when this occurs, that the device is defective and needs to be replaced by Microsoft.

Device Manager

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



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

 

UEFI Forum Releases UEFI 2.3.1 Specification Update

The UEFI Forum has ratified an update to the UEFI 2.3.1 Specification that adds important firmware considerations and addresses numerous engineering change requests. The updated Specification will be referred to as “UEFI 2.3.1C”.

• UEFI 2.3.1C adds: An OS Indications Variable - OS/FW feature & capability communication – when implemented, allows end-users to make an OS menu request to enter BIOS setup after next reboot.
• UEFI 2.3.1C adds: A mechanism which, when implemented, facilitates Open Source Operating System installations and OS- agnostic end-user configurations of retaining the factory default keys while in Setup Mode (see Specification for full technical detail of Setup Mode).
• UEFI 2.3.1C removes: Runtime driver requirement on Network UNDI drivers - this allows UNDI drivers to be delivered in EFI Byte Code (EBC) Virtual Machine format supporting systems based on different processor architectures.

Complete details on UEFI 2.3.1C are available here.

The UEFI Forum’s UTWG (UEFI Test Working Group) is currently working on updating the SCT (Self-Certification Tests) to align with the latest spec changes. Please see www.uefi.org for more updates.

UEFI Summer Summit Interoperability & Education Event:
Specification Update Benefits Windows 8 & Open Source OS Implementations Microsoft to Host UEFI Summer Summit, July 16-20, 2012 in Redmond, WA

The UEFI Testing Work Group (UTWG) and the UEFI Industry Communications Work Group (ICWG) from the Unified EFI (UEFI) Forum invite you to register for the upcoming UEFI Summer Summit: An Interoperability and Education Workshop being held this July at the Microsoft Campus in Redmond, WA.

• Hosted by Microsoft, the event is sponsored by AMD, AMI, HP, Insyde, Intel, Microsoft & Phoenix.
• Online registration for the UEFI Summer Summit can be found at here and here. Please note registration is scheduled to close on July 9th.

The organizers specifically wish to encourage add-in card vendors to attend the Summit. This is the last planned Forum-sponsored opportunity to test Secure Boot functionality and the interoperability of cards with UEFI-compliant systems for 2012. With the serious industry interest in Secure Boot functionality, this Summit is an excellent opportunity to test interoperability, as well as discuss the technology with other industry members.