EFI Shell version 2.31 [5.8] HELP

Question

I turned my laptop on and found a black screen displaying the following:

EFI Shell version 2.31 [5.8]

Current running mode 1.1,2

Device mapping table

 **bik0 :** BlockDevice - Alias **(null)**

           PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x0)

 **bik1 :** BlockDevice - Alias **(null)**

            PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x1)

 **bik2 :** BlockDevice - Alias **(null)**

           PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x2)

Press ESC in 4 seconds to skip startup.nsh, any other key to continue

Shell>

Note: Please kindly help with this

Answer 1

Hi tf_aze,   Welcome to Microsoft Community.Thank you for posting your inquiry regarding device boot issues.

Encountering this EFI Shell screen can be unsettling, especially when you expect your laptop to boot normally into your operating system. What you’re seeing indicates that the UEFI firmware was unable to locate a valid bootloader—its usual instruction for passing control to your OS—and as a result, it has resorted to launching the shell environment.

• At the heart of the matter lies the boot process. When you power on your device, the UEFI firmware scans the connected storage devices (as reflected by entries like "bik0," "bik1," and "bik2") in its device mapping table. These entries show that while the firmware recognizes the physical devices, it can’t identify a bootable partition or a properly configured bootloader on them. This might be due to an altered boot order or misconfigured settings in the BIOS/UEFI—possibly triggered by an accidental change or a reset caused by an internal event. In such scenarios, the system could inadvertently prioritize the EFI Shell, bypassing the normal boot sequence.
• Another significant factor is the integrity of your storage devices. The inability to locate a bootloader could hint at issues such as a corrupted bootloader, missing boot files, or even early signs of physical degradation in the drive (whether SSD or traditional hard drive). As electronic components age, their performance can falter, leading to detection or compatibility issues that prevent the UEFI from successfully loading the expected operating system.
• Security measures within the UEFI framework, including Secure Boot, may also play a role. If Secure Boot is enabled and the bootloader—or any associated startup file—lacks the necessary digital signature, the firmware might refuse to load it, defaulting instead to the EFI Shell as a safeguard. This protective layer ensures that only verified, trusted code is executed during the boot process, but it can sometimes lead to unexpected behavior if the current bootloader configuration doesn’t meet those stringent criteria.
• To visualize this process, consider the following similar flowchart:

Generally speaking, you may need to try to boot into BIOS/UEFI to check if the boot order of the device is correct.

• If necessary, you may need to refer to the product manual or support article provided by the device manufacturer to check options that may affect the hardware check process, such as CSM (Compatibility Support Module, Secure Boot). This is an example of an image from another thread. The style and operation logic of BIOS/UEFI provided by different device manufacturers may be different.
• If the phenomenon occurs after a BIOS/UEFI update, you may need to try to consult the device manufacturer to find out whether BIOS/UEFI downgrade is supported.
• To boot to UEFI or BIOS, boot the PC, and press the manufacturer's key to open the menus.   Common keys used: Esc, Delete, F1, F2, F10, F11, or F12. During startup, there's often a screen that mentions the key.   If there's not one, or if the screen goes by too fast to see it, check your manufacturer's site. If there's not one, or if the screen goes by too fast to see it, check your manufacturer's site.

Disclaimer*:  Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party  linked sites or any support related to technology.*<br>If you are going to modify BIOS Settings, please back up all your personal files first to ensure you do not lose data.

Considering the worst case scenario (physical problems or serious damage to system files), you may need to resort to some special methods to back up your data.

Options for backing up your data include removing the disk and connecting it to another computer as a secondary disk, or using the Command Prompt option provided by Windows Recovery Environment, as shared by other community members in the thread below.

• It relies on an additional bootable USB media. External bootable media has files associated with a separate Windows Recovery Environment. They are similar in function, but it does not directly use the files on the disk where Windows is already installed. You can create the USB media on other working devices. Create installation media for Windows - Microsoft Support
• There is more described in the thread, only the key parts have been captured. You can click on the thread for more information. Rescue Files when Windows Won't Start - Microsoft Community

Thanks for your patience and understanding.Best Regards,Kyo.Y - MSFT | Microsoft Community Technical Support