this search on dell.com shows 69.7K results(naturally a better search will narrow down the results):
ttps://www.dell.com/community/en/conversations/search?q=%22reset%20admin%20password%22

would be great if you could figure it out

Regards.

P.S. Only guesses, not claiming to be true.
In my experience, the BIOS recording program will not overwrite the existing one if the versions match, as happened in my case.
Perhaps the reason for the overwrite is that when I deleted the Win boot record using bcdedit, I deleted the usbcd and usbfloppy records, which the meta will not have and which are records of the BIOS itself.
On the first boot after resetting cmos, a “checksum error” appeared and this may be the reason for launching the BIOS recording program.

But games with BIOS can turn your computer into a brick.
Is it necessary to take risks? It’s up to the owner\.

To flash the BIOS, all I had to do was boot Win itself from a flash drive, plug in a second flash drive with the BIOS, and run the installer directly from it. Therefore, language does not matter in this case.

I downloaded Windows-live and launched the BIOS firmware file in it (for mine it’s called 4BCN24WW.exe). The program overwrote it, originally the BIOS was the same version.

The F2 button opens the BIOS.

Repeated the procedure for removing the CMOS battery with voltage monitoring, sealing, etc.
The BIOS remains unavailable, the standard F2 does not work.

But, actually, I have nothing to switch in it, Linux installs and works without problems.

P.S. I don’t know if this has anything to do with my case, but I already had a similar problem.
https://www.phoronix.com/news/Ubuntu-17 … -Corrupter

TC

Regards.

In an attempt to figure out uefi, I installed Win and it blocked entry into the BIOS (Lenovo s205).
No attempts from Win, nor the

 systemctl reboot --firmware-setup, grub firmware  

commands brought success. Even removing the CMOS battery did not change the condition.

At the same time, the boot menu worked and the first entry was Win. I removed it using bcdedit and formatted the disk.
Linux is installed, and the bootloader can be installed in the MBR, or you can install uefi by adding the /boot/efi partition. Both options work without switching in an inaccessible BIOS.

Here is a bios with quirks.
The BIOS reacts to the very presence of /boot/efi and its flags. Without ecp flags, “frozen” appeared in the “disk password” line.
Thanks for your tips, they pushed me in the right direction.

Regards.

Were you able to determine which device has no space left?  Can you please post the output of df -h and fdisk -l?

If you have a uefi-bootable install, you can install all the others without a bootloader and then run update-grub (with os-prober enabled) in the bootable install to get all the others into the boot menu.

Here's the test for efi partition(s). Maybe someone will look at it and get a good idea.

# Check for UEFI boot and EFI partition
if [[ -d /sys/firmware/efi ]]; then
        uefi_boot="yes"
        esp_count=$(env LC_ALL=C fdisk -l | awk '/EFI System/ { print $0 }' | wc -l)

        if [ -z "$gpt_list" ] ; then
                gpt_message=$"There is no disk with a gpt partition table. 
        You should exit this script and run gdisk to create one for uefi boot."
        fi
        if [ "$esp_count" -eq 1 ] ; then
                esp_dev=$(env LC_ALL=C fdisk -l | awk '/EFI System/ { print $1 }')
                esp_dev_message=$"EFI partition found at ${esp_dev}
        If this is not on the first hard disk, something may be wrong,
        and you should investigate the situation."
                if ! blkid -c /dev/null -s TYPE "$esp_dev" | grep -q "vfat" ; then
                        must_choose_esp="yes"
                        esp_dev_message=$"EFI partition found at ${esp_dev}
        will need to be formatted FAT32"
                fi
        else
                must_choose_esp="yes"
                if [ "$esp_count" -eq 0 ] ; then
                        esp_dev_message=$" There is no EFI partition. You will need to create one."
                elif [ "$esp_count" -gt 1 ] ; then
                        esp_dev_message=$"More than one EFI partition was detected.
        You will need to select one. Normally, it's on the first hard disk."
                fi
        fi

Ignore the missing final "fi". The rest of this code block just checks to see which grub is installed and generates some messages.

I'll try.
Although, in my case the problems are due to a specific BIOS.
During the OpenSuse installation, the /boot/efi partition was explicitly specified, so it booted. The rest of the distributions that I tried selected MBR, but when I tried to select efi they reported an error

grub-install: warning: Cannot set EFI variable Boot0007.

Regards.