mediumMultiple Choice
220-1201 Practice Question: After updating the firmware on a workstation, the…
After updating the firmware on a workstation, the system fails to boot and displays a 'Boot Device Not Found' error. The hard drive is detected in UEFI settings. What is the most likely cause?
⚠ Common exam trap
220-1201 often tests the tendency to blame hardware failure for boot errors — candidates pick 'hard drive failed' even though the drive is detected, missing the firmware boot-mode mismatch.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The boot mode changed from Legacy to UEFI (or vice versa)
A firmware update can reset or change the UEFI/BIOS boot mode setting, causing the system to look for an EFI System Partition (ESP) when the OS was installed in Legacy/CSM mode, or vice versa. Since the drive is detected in UEFI settings, the hardware is fine — the mismatch between the configured boot mode and the installed bootloader is the most likely cause of 'Boot Device Not Found.'
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The hard drive has failed due to the update
Why it's wrong here
A firmware update primarily affects the motherboard's basic input/output system and its integrated components, not the physical integrity or data on a storage drive. If the hard drive is still detected within the UEFI/BIOS setup utility, it indicates that the drive's controller and basic hardware are functional. A boot issue immediately after a firmware update is far more likely related to system configuration changes rather than a sudden, catastrophic hardware failure of the drive itself.
- ✗
Secure Boot is blocking the bootloader
Why it's wrong here
Secure Boot is a security feature within UEFI that prevents unauthorized operating systems or bootloaders from loading during startup by verifying their digital signatures. If Secure Boot were blocking the bootloader, the system would typically display a specific error message indicating a "Secure Boot Violation" or "Invalid Signature," rather than simply failing to find a boot device. Furthermore, Secure Boot primarily affects unsigned bootloaders, which is less common for standard Windows installations.
- ✓
The boot mode changed from Legacy to UEFI (or vice versa)
Why this is correct
Firmware updates often reset UEFI/BIOS settings to their default values, which can include the crucial boot mode setting. If the system was previously configured to boot in Legacy BIOS (CSM) mode with an MBR-partitioned drive and the firmware update defaults to UEFI mode, the system will fail to find a bootable operating system. Conversely, if a GPT-partitioned drive was set up for UEFI boot and the system reverts to Legacy mode, it also won't recognize the boot partition, leading to a boot failure.
- ✗
The CMOS battery needs replacement
Why it's wrong here
The CMOS battery powers the real-time clock and retains UEFI/BIOS settings when the system is unplugged from power. While a dead CMOS battery can cause settings to revert to defaults, this issue typically manifests after the system has been powered off and unplugged for an extended period, not immediately following a firmware update. A firmware update itself is a controlled process that writes new settings, making a dead CMOS battery an unlikely immediate cause for a boot error.
Go deeper
Related to this question
Learn chapter
BIOS/UEFI Update Procedures
Key term
BIOS
BIOS (Basic Input/Output System) is the low-level firmware stored on a motherboard chip that initializes and tests hardware components before loading the operating system.
Key term
Unified Extensible Firmware Interface
UEFI is the modern replacement for BIOS that controls how a computer starts up and loads the operating system.
About these practice questions
One of 871 original 220-1201 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on 220-1201
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. After replacing a motherboard, a technician installs Windows but the system will not boot from the SSD. The drive is detected in UEFI. The technician recalls the previous motherboard used Legacy BIOS. What is the most likely issue?
medium- A.The SSD is not getting power
- ✓ B.The UEFI is set to UEFI mode but the drive uses MBR
- C.Secure Boot is blocking the Windows bootloader
- D.The CMOS battery is dead
Why B: The most likely issue is a mismatch between the UEFI firmware mode and the partition scheme on the SSD. If the previous motherboard used Legacy BIOS, the drive was likely initialized with an MBR partition table, which requires Legacy/CSM boot mode. A UEFI system expects a GPT partition table with an EFI System Partition, so it cannot boot from an MBR drive unless CSM is enabled.
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This 220-1201 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1201 exam.