For what it's worth, in my day job we deploy bios updates via windows update to our fleet of about 175 computers and have for years and have never once run into an issue.
Bios updates are not the scary thing people like to make them out to be.
Discussion around the Framework mission of building products that last longer by making them upgradeable, customizable, and repairable. Consumer electronics can be better for you and for the environment.
For what it's worth, in my day job we deploy bios updates via windows update to our fleet of about 175 computers and have for years and have never once run into an issue.
Bios updates are not the scary thing people like to make them out to be.
Bios updates are ~~not~~ no longer the scary thing people like to make them out to be.
FTFY
bios updating the hba (array controller) on your primary sql server during a 30 min maintenance window at 2am is still a bit never wracking.
But yeah, pushing out bios updates to desktops/laptops has become a near-non issue. That combined with the decline in device cost and the rise in backup and cloud-based apps make replacing a died-during-update machine a lot less onerous.
I would still prefer to be in control of what my device is doing. I've also had machines at work fail in the middle of a bios update, i didnt really care then because it was one of the many computers we have and it was just replaced but if i had spent multiple thousands of dollars on it i would be pretty crushed.
BIOS updates via Windows Update are, as far I as understand, completely industry standard. Most BIOS updates are focused on security risks, and they shouldn't be skipped due to perceived inconvenience. The people rolling them out probably know more than you or I do. I would strongly suspect that there is a higher statistical risk of wrecking your computer or introducing malware by running a BIOS .exe than by using Windows Update.