means the shell is compliant with Version 2.60 of the UEFI Shell Specification . This specification, produced by the UEFI Forum, sets the rules for the shell’s commands, behavior, and interface, ensuring consistency across different hardware vendors. This version number is independently tracked from the UEFI (firmware) specification itself . For example, a shell following version 2.60 of the shell spec can run on top of a system firmware that complies with UEFI version 2.6 or newer.
If none of the above succeeds, it’s time to check the physical hardware. For desktops, open the case and verify that all SATA data and power cables are secure and that the drive is properly seated. On laptops and single-board computers (like the LattePanda), the drive—whether an NVMe SSD or eMMC—might have failed. Booting from a USB live environment and running disk diagnostic tools ( chkdsk on Windows or fsck on Linux) can help determine if the drive is still functional.
EFI Shell version 260 512 2021 is a specific release of the EFI Shell firmware interface. The version number can be broken down into three parts:
| Command | Function | Example Use Case | | :--- | :--- | :--- | | map | Displays or defines the mapping of drive letters ( fs0: ) to physical device paths. | map -r refreshes the device mappings. This is the first command you should run to see your drives. | | devices | Displays a list of all devices managed by UEFI drivers. | Run devices -b for a verbose, page-by-page list of all recognized hardware. | | drivers | Displays a list of all loaded UEFI drivers. | drivers will show you which drivers are active, their version, and the devices they manage. | | connect | Binds a UEFI driver to a specific device. | connect -r attempts to connect all drivers to their corresponding devices, which can help if a drive isn't appearing. | | dh | Displays detailed information (dumps handles) about UEFI device handles. | dh -p lists all handles and their associated protocols, a powerful tool for deep debugging. | | pci | Displays a list of all PCI devices or the configuration space of a specific device. | pci -i shows a detailed list of all PCI(e) devices, including their bus, device, function, and class codes. | efi shell version 260 512 2021
If the drive is , turn off the PC, unplug it from the wall, open the case, and reseat the data and power cables connected to the drive (or reinstall the M.2 SSD into its slot).
: The BIOS/UEFI settings are prioritizing the internal EFI Shell over your primary drive.
Sometimes, the shell opens simply because a boot delay occurred. You can attempt to force the system to continue booting. Type exit into the prompt and press . means the shell is compliant with Version 2
bootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd Use code with caution.
If it is disabled, try it (or switching Boot Mode from UEFI to Legacy/Dual Mode ).
Older operating system installations require Legacy mode, while newer ones require UEFI mode. For example, a shell following version 2
Your SSD or HDD might be disconnected, loose, or failing.
If the system attempts to boot but fails, your Windows startup files might be corrupted. You will need a working computer to create a bootable Windows Installation USB drive for this step.
If the hardware is detected in the BIOS but still drops into the EFI Shell, your operating system's boot files are likely corrupted. You will need a working computer to fix this.
The simplest way to attempt a bypass is to type exit into the prompt and press . On some systems, this will force the computer to try the next boot device in line. If it simply loops back to the shell, you must adjust your hardware or BIOS settings. Step 2: Fixing Boot Settings in BIOS