[OBSOLETE] BIOS Upgrade for Linux Users



Perfect! Thanks — this is just what I was looking for.

User1209, sorry that you ran into issues with the boot loader.

I did not have any such issues. I left my SSD connected, ran this process, and booted into Linux without issues after the BIOS updated.

I hope others have such good luck!

The two times I booted the W10 installer mentioned in the other thread I linked, I did it without having the drive physically installed in the computer. For the firmware update I just did, I left the drive installed, so it happened in both scenarios (with/without drive installed).

This does not happen at all when I boot up arch install usb stick I’ve been using (it doesn’t mess with any settings at all unless I explicitly tell it to).


Superb! This is exactly what I did last but didn’t have time to write it up. This should be pinned along with the BIOS threads.

1 Like

I finally got around to doing this. It worked perfectly.

Updating the BIOS was fairly quick. I was not expecting the updating EC/updating PD1/updating PD2 procedures and these took long enough to make me uncomfortable, but they completed and everything’s fine.

And Windows did not mess up my bootloader!

Now I wonder if my SSD updater .EXE will work this way?


Worked perfectly for 3.06 bios update.

Used this method to install firmware from windows iso boot. Running manjaro w/ full disk encryption, i7-1185G7, phase 2 release.

The power button is not longer like looking into the sun! (Set power LED display brightness in BIOS).

1 Like

It worked for me as well. Upgrading to 3.06 on an October batch laptop. I had to perform three extra steps to be able to boot from the ventoy USB disk:

  1. disable secure boot in existing bios
  2. install ventoy using MBR partitions. It would not work for me if ventoy was installed with guid partitions
  3. use a USB mouse. The builtin trackpad would not work for me with the windows installer
1 Like

I had a similar experience with @User1209. BIOS and other images were installed correctly. However, a new directory was created by this process named /boot/EFI/Insyde, which wasn’t there before, and the grub got nuked. I followed his recommendation and re-installed grub from a live arch linux installation medium with the following command found at wonderful arch wiki:
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
Please make sure you run this command after chrooting in your system and not from the installation medium. I had a LUKS encrypted drive, there were a few more steps that took me an hour or so to figure out in total.
Hope this helps to the next individual who may experience this issue.

1 Like

Thank you for sharing this!
really looking forward to the official LVFS implementation.
<3 loving my Framework laptop with Pop!_os 21.04


I have a question on this.
So framework does use insyde bios, right? I happen to have a Lenovo Yoga notebook and I am also looking for a solution to update my bios without having to install Windows.
So my question is: is the update program from framework a GUI application or is this just a “dos-like” application? Can you even start graphical programs from Windows Installer command line? Because Lenovo is shipping the updates with a GUI that looks like a program from 1995.

It’s a “DOS-like” command line application.

But you can’t run a Windows GUI application from the Windows installer command line. I’ve tried (WD Dashboard, to flash firmware in WD SSDs).

1 Like

Thanks, that is what I thought. So I have to find a way to get a Windows GUI running off a USB drive somehow which is a PITA it seems. The other option is to boot from Thunderbolt-NVMe enclosure but the external cases are ridiculously expensive, sadly.

You can install Windows (not Windows To Go) on a large enough USB drive and still use the USB drive for other things using Ventoy:

Just watch out for the shenanigans it will pull on your Linux install, but it won’t destroy it and it only needs to be fixed once.

I installed it from a valid Windows 10 Educational VM and it seems to be fully activated. It’s full-fledged Windows and can run any GUI normal windows can.

/me watching intently at this. About to buy W10 pro retail, but don’t want a stain in my framework peeing on it forever. Since w10 will time out and likely get lousier till its EOL, my “free w10” installs in a couple boxes could be used beyond 2025 with a wtg type thing.

Progress for those of us without Windows


I’m using an old Lenovo thinkpad T61 running latest Ubuntu and I followed all the directions except when I booted from the USB drive and selected the Windows 10 .iso, my computer just sat there with a blinking cursor until I restarted it and gave up. Any thoughts? Not enough RAM?

Just a curious question, would this approach from Arch Linux be better?

Doesn’t seem like it will screw up your bootloader.

This techique is obsolete now that the EFI updater and LVFS are available.

Closing this thread but keeping it up for reference.