I missed some BIOS updates and tried going from 3.05 to 3.16 directly. I couldn’t find the intermediate versions to do a stepwise update, so I haven’t tested that yet. The Insyde (BIOS installation) window hangs with “Updating” status displayed. I tried leaving it for at least 6 hours. Then I powered off and when I powered on, the Framework logo came up, and then I got a bluescreen, and then I powered up again and got a normal boot. BluescreenView says that the bluescreen was caused by mtkwl6ex.sys.
I then tried the driver install again. It went through the first 10 drivers and reported installing them as if they hadn’t been updated before. Then it got stuck in the same place.
Against my better judgment, I tried the BIOS a second time too. It hung at the same place, so I closed the Insyde software and then restarted the computer. There was no bluescreen. Possibly because I closed Insyde first before shutting down this time.
I can think of a few more things to try, but I thought I would ask whether anyone else has had this problem and already found a solution. I am not sure if I have two problems or if this is all related.
@Brian_Gregory is right that all the BIOS updates are cumulative if I remember correctly. So an intermediary BIOS is not necessarily needed before updating to the latest one.
If you suspect the BIOS did not install fully, you could try the UEFI BIOS on a USB to see if it goes through correctly. Make sure to write down your bitlocker key or have it handy and disable secure boot I think are some of the other cautions if it does not update fully.
Going into the BIOS after updating and setting it back to defaults is a good practice too so that all the NVRAM values are correctly assigned.
Good point about the bitlocker key. I don’t remember what happened when I updated the BIOS on my laptop 13, but I do remember that with most PCs, if you have bitlocker enabled, you will 100% need the bitlocker key (the one that is 8 groups of 5 digits) the first time you boot Windows after a BIOS update.