Courseiva
Software Troubleshooting →hardMultiple Choice

220-1102 Software Troubleshooting Practice Question

A Windows 10 workstation displays 'Bootmgr is missing' upon startup. Which of the following is the most likely cause of this error?

⚠ Common exam trap

Many exam-takers confuse MBR corruption with BCD corruption, but the specific 'Bootmgr is missing' message points directly to a BCD issue, not the MBR, which would produce a different error.

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 configuration data (BCD) is corrupted

The 'Bootmgr is missing' error typically occurs when the Boot Configuration Data (BCD) store is corrupted or missing. BCD contains critical boot parameters for Windows Boot Manager (bootmgr.exe), and corruption prevents bootmgr from locating the boot partition. This is a common issue after improper shutdowns, disk errors, or failed updates.

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 Master Boot Record (MBR) is corrupted

    Why it's wrong here

    A corrupted MBR is an earlier-stage fault: the MBR lives in the first sector of the disk and its code must hand execution to the active partition's boot sector before bootmgr is ever located. When the MBR is damaged, firmware typically reports 'Missing operating system' or 'Invalid partition table' because bootmgr.exe has not yet been found, not 'Bootmgr is missing.'

  • ✓

    The boot configuration data (BCD) is corrupted

    Why this is correct

    The BCD store is the boot-time database that bootmgr queries to find the Windows boot loader and the partition containing the OS. If the BCD entries become corrupted or point to a nonexistent device, bootmgr cannot locate the OS and aborts with the exact 'Bootmgr is missing' message. Rebuilding the BCD with bootrec /rebuildbcd is the standard repair.

  • ✗

    The hard drive cable is loose

    Why it's wrong here

    A loose SATA/IDE cable typically prevents the firmware from detecting the hard drive at all, which produces a 'No bootable device' or 'Disk read error' at POST. That failure occurs before bootmgr is even loaded, and it would not normally generate a literal 'Bootmgr is missing' text prompt. Additionally, a loose cable would likely cause inconsistent, intermittent disk access rather than a clean missing-bootmgr error.

  • ✗

    The Windows Registry is corrupted

    Why it's wrong here

    Registry hives are not touched until ntoskrnl.exe and the session manager (smss.exe) load them during kernel initialization, which happens long after bootmgr and winload.exe have already run. A corrupted registry causes stop errors, boot loops, or the 'Windows failed to start' recovery screen, not the 'Bootmgr is missing' text message. Because bootmgr itself never reads the registry, registry damage lies outside this error's cause.

Go deeper

Related to this question

About these practice questions

This 220-1102 question is part of Courseiva's 925-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This 220-1102 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-1102 exam.