Examkin

Question

Difficulty: MediumTroubleshooting Windows OS Startup and Boot Errors

A technician is resolving a Windows startup failure caused by a corrupted Boot Configuration Data (BCD) store. Operating in the Windows Recovery Environment (WinRE) Command Prompt, the technician attempts to run `bootrec /rebuildbcd`, but the command cannot replace the existing store because the BCD file remains locked and marked as system-protected. Place the remaining steps required to unlock, replace, and successfully rebuild the BCD store in the correct sequential order.

  1. 1Remove the hidden, read-only, and system attributes from the BCD file by running `attrib c:\boot\bcd -h -r -s`.
  2. 2Rename the corrupted BCD file to a backup name by running `ren c:\boot\bcd bcd.old`.
  3. 3Re-run `bootrec /rebuildbcd` to scan for installed Windows operating systems.
  4. 4Press `Y` (Yes) when prompted to add the detected Windows installation to the new BCD configuration.

Answer

The correct sequence begins with removing the file attributes using `attrib`, followed by renaming the corrupted BCD file using `ren`, re-executing `bootrec /rebuildbcd` to regenerate the boot store, and finally confirming the addition of the OS installation when prompted.
When repairing BCD store corruption, `bootrec /rebuildbcd` may fail if the existing BCD file is locked or damaged. The proper recovery procedure requires removing the system, hidden, and read-only attributes from `c:\boot\bcd` using `attrib -h -r -s`. Next, renaming the file with `ren c:\boot\bcd bcd.old` clears the path. Running `bootrec /rebuildbcd` then initializes a new configuration store, and entering `Y` at the prompt adds the operating system to the clean BCD file.

Step-by-Step Solution

1
Clear system file locks and attributes.
File attributes (-h -r -s) are removed from `c:\boot\bcd` so administrative commands can modify it.
Windows protects boot configuration files with System, Read-only, and Hidden attributes, preventing them from being renamed or overwritten while protected.
2
Rename the existing corrupted BCD store.
The file `c:\boot\bcd` is renamed to `bcd.old`.
`bootrec /rebuildbcd` will fail to create a new file if an existing file with the same name exists at that directory path.
3
Initiate the boot reconstruction utility.
The utility scans all connected drives for Windows installations and prompts to add discovered OS installations.
Now that the corrupted file path is clear, running the rebuild command allows the installer to initialize a clean boot database.
4
Confirm adding the detected OS to the new boot store.
The Windows boot manager entry is successfully written to the new BCD store.
User confirmation is required by `bootrec` to finalize adding identified OS installations to the newly constructed database.

Key Concept

Rebuilding Corrupted BCD Files via WinRE Command Line
Rate this question

Topics

Troubleshooting Windows OS Startup and Boot Errors

More questions from this topic