A technician is troubleshooting a Windows 11 workstation that fails to boot after a firmware update. Upon powering on, the system displays the error message 'An operating system wasn't found.' The workstation uses UEFI firmware and a GPT-partitioned NVMe boot drive. The technician boots into the Windows Recovery Environment (WinRE) Command Prompt and confirms that the main Windows installation partition (C:\Windows) is healthy and accessible. Which TWO of the following steps should the technician take to regenerate the boot files and restore bootability? (Select TWO.)
- Use diskpart to locate the hidden FAT32 EFI System Partition (ESP) and assign it a temporary drive letter.Cevap
- Execute bcdboot C:\Windows /s <drive_letter>: /f UEFI to copy the boot environment files to the EFI System Partition.Cevap
- CExecute bootrec /fixmbr from the Command Prompt to overwrite the Master Boot Record on the NVMe disk.
- DExecute sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows to repair corrupted EFI bootloader binaries.
Cevap
The correct steps are to use diskpart to locate and assign a drive letter to the hidden FAT32 EFI System Partition, and then execute bcdboot C:\Windows /s <drive_letter>: /f UEFI to recreate the boot environment files.
On Windows workstations configured with UEFI firmware and GPT partition tables, boot execution depends on files residing in the FAT32 EFI System Partition (ESP). When the main C:\Windows directory is intact but the system displays boot errors, a technician must mount the hidden ESP using diskpart to assign a drive letter, and then run bcdboot targeting that partition to generate fresh UEFI boot files and configuration data.
Adım Adım Çözüm
Anahtar Kavram
Repairing UEFI/GPT Windows bootloader files using diskpart and bcdboot