11th Gen Intel Core BIOS 3.10 Release

BIOS 3.10

We are happy to release BIOS 3.10. This fixes a charging bug in 3.09. If you are using a version less than 3.09, we strongly suggest you update due to security vulnerabilities present in older versions.


Windows Installer


Instructions for Windows:
Plug your system into a charger before updating firmware.
Download the installer and run the exe, your system will restart and finish updating the firmware.


EFI Shell

Instructions for EFI shell update:

  1. Extract contents of zip folder to a fat32 formatted usb drive.
  2. Disable secure boot in BIOS.
  3. Boot your system while pressing F12 and boot from the thumb drive.
  4. Let startup.nsh run automatically.
  5. System will reboot, you can unplug the thumb drive.

LVFS update

Updating via LVFS is available in the testing channel
You can enable updates from testing by running

fwupdmgr enable-remote lvfs-testing

Currently LVFS support has regressed due to fwupdmgr defaulting to file based capsule update on newer versions which is not supported in our BIOS.

Please set DisableCapsuleUpdateOnDisk=true in /etc/fwupd/uefi_capsule.conf before applying this update, otherwise the update will fail.

LVFS may not update if the battery is 100% charged. LVFS uses the battery status to determine if it is safe to apply updates. However if our battery is at 100% and the charger is off, we set the battery charging status to false. In this case you can discharge your battery a few percent, then plug in AC again and run fwupdmgr update.

Warning! Update may cause your system to lose boot entries.

Updating the BIOS firmware will erase NVRAM boot variables, This can cause some alternate bootloaders or operating systems to fail to boot. This may impact users of rEFInd and some Linux distributions. If your system reboots after updating and cannot find a bootable device, you can manually select a boot device by using the one time boot menu by pressing F3 during boot, and manually selecting your EFI boot file. After this you may need to reinstall grub. See Lost GRUB dual boot after updating to BIOS 3.07 - #6 by XADE
This should not be an issue for Fedora/Ubuntu unless they are installed along side a windows partition.

Downgrading firmware

You can downgrade your firmware by running fwupdmgr downgrade and selecting the version you want to downgrade to. Please note that versions before 3.09 do not have the F3 one time boot file menu if you need to select an alternate bootloader after downgrading.

Security Fixes

BIOS 3.09 update patches a number of important security issues. It is recommended to update to patch these vulnerabilities.

A big thanks to the team at https://www.binarly.io/ who found these issues and worked with us to verify they were fixed.

CVE Binarly
CVE-2021-42059 BRLY-2021-021
CVE-2021-42060 BRLY-2021-022
CVE-2021-42554 BRLY-2021-027
CVE-2021-33625 BRLY-2021-029
CVE-2021-43615 BRLY-2021-028
CVE-2021-43323 BRLY-2021-031
CVE-2021-45969 BRLY-2021-016
CVE-2021-45970 BRLY-2021-015
CVE-2021-45971 BRLY-2021-012
CVE-2021-33626 BRLY-2021-013
CVE-2021-33627 BRLY-2021-011
CVE-2021-41837 BRLY-2021-026
CVE-2021-41838 BRLY-2021-030
CVE-2021-41839 BRLY-2021-017
CVE-2021-41840 BRLY-2021-019
CVE-2021-41841 BRLY-2021-025
CVE-2020-27339 BRLY-2021-020


  1. Fix battery not charging when system is off.

Known Issues

  1. Thunderbolt devices may not be recognized on S4 resume in some cases. But will be detected by replugging the device.
  2. Touchpad PS2 fallback mode may not work if the user is in an OS that supports the SerialIO driver, and then restarts to an OS that does not support the SerialIO driver, such as trying to reboot into the Windows 11 Installation media. Workaround is to power off the laptop and perform a cold boot into the installer/os to enable PS2 mouse fallback mode if necessary.

Link to Previous BIOS Release:


Great to see such a fast response to the charging bug, thanks!

1 Like

Successfully updated to 3.10 using LVFS. Unfortunately that doesn’t solve my LUKS+Yubikey issue. Aside from that seems to work fine.

1 Like

Updated via Windows. No issue there.

Thank you for the quick turnaround.

So for anyone having troubles these are the steps I had to take to get an update working (using Ubuntu 22.04):

  1. You do have to re-enable lvfs-testing even if you already did for a previous update. It will ask you if you are sure, and then if you it should update the repo. Yes to both. Then close the terminal window.
  2. if you make the DisableCapsuleUpdateOnDisk change it will persist, and you don’t need to do this again.
  3. open another terminal window. Now with your battery under 100% and charging, type fwupdmgr update, and you should be prompted to proceed with the update. Say yes here, and then yes again in a moment to restart.

You should be good to go then.


That was the key for me, although I arrived at it inadvertently. fwupdmgr was indicating no updates were available and when I tried to update (fwupdmgr update) I was just bounced back to the prompt. I had closed the lid (putting the laptop to sleep) and the next time I tried the process hung. I had to restart (force power off first because it was still hung).

On restart it worked fine but this was because I had opened a new terminal window.

Everything’s good now although I’ve lost my fingerprint reader and can’t seem to get it back.

I seem to run into some kind of silent failure when updating from 3.9 to 3.10 on Fedora 36 via lvfs. The previous update (3.8 to 3.9) went just fine when I did it a week or so ago, but this time I see the system booting into fwupd-efi 1.3, then the screen turns black and a reboot into Fedora starts.

I’m pretty sure I followed all the steps correctly and avoided any gotchas, still won’t work no matter how many times I try it. Any ideas?

Downloaded and installed, no issues thus far.

Had no issues with fedora 36

1 Like

Alright, I’m trying it. The update through LVFS went fine. I just had to do a “fwupdmgr refresh” before I could see 3.10 as being available.


I’m having a similar issue, but I also had the same issue when I tried updating from 3.07. I’m also on Fedora 36, and I’m truly at a loss here.

I’ve made sure of the following

  1. DisableCapsuleUpdateOnDisk=true in /etc/fwupd/uefi_capsule.conf persisted (no hashtag) after reopening and closing the file
  2. fwupdmgr enable-remote lvfs-testing completed without error.
  3. The battery was not fully changed, AND it was plugged in with a USB-PD adapter, and the Laptop was charging.
  4. I closed the terminal, reopened, and fwupdmgr update was executed without any error (so far as I can tell)

When the laptop restarted, it just sent to the Fedora log in screen.

I tried manually selecting the update manager from the F12 BIOS menu upon boot. The screen turned black and read “fwupd-efi version 1.3 WARNING: No updates to process, exiting in 10 seconds.” After waiting it out, the screen briefly flashed blue before booted back into Fedora.

Anyone have any suggestions?

Doesn’t the update image get stored in a EFI partition? …and if that partition is nearly full…it can’t store the image for update? (I could be really wrong here).

Maybe check how much diskspace you have left on your EFI partition?

Just to clarify, the latest beta BIOS is 3.10, but the latest stable release is 3.07. Is this correct?


UEFI upgrade from 3.07 to 3.10 went without a hitch.

  • Intel i7-1165G7
  • 32GB RAM
  • Intel® Wi-Fi 6E AX210 No vPro
  • Linux Mint 20.3

I did have to reset

  • Maximum battery charge limit (it had reset to 100%)
  • Power button brightness (it had reset to max brightness)
1 Like

Went from 3.09 to 3.10 smoothly

The only issue, is when I press f12 it freezes. Have been like this with 3.03, 3.09 too

@Denes_Adam_Dolhay black screen freezes? Do you have quiet boot disabled?


Depends on when I push it. If I push before anything appears on the screen, then it remains black. If I press it when the POST is already visible, then it freezes on that screen

Yes, quiet boot is disabled

The only thing that is not stock is a 2TB Toshiba SSD KXG50PNV2T04 NVMe TOSHIBA 2048GB I carried over from my last machine

I was very happy to see the 3.10 BIOS release to fix the charging bug in 3.09. I have a dual boot system but this time I chose to run the .exe rather than the EFI version.

All went quite smoothly including recovery of the grub menus. When the install completed and the laptop rebooted it went (again) to Windows. But this time I had a suspicion so I shut it down entirely and then rebooted. The grub menus were right where I expected. Yay.

Now I cannot say whether the EFI path would have had the same effect because I didn’t reboot manually after it first came back from an EFI install.

On the (unsupported) assumption that it does not matter which path I take, I now prefer the .exe path because no USB boot and generally easier. Obviously, if I had a no Windows system installed that would not be an option.

Thanks for pushing out this fix! I was just troubleshooting this last night and confirmed the behavior with a charging meter. Great job, team!

1 Like