220-1102 Question 581
Single answerBoot issuesA Windows 11 laptop displays "No bootable device found" immediately after the manufacturer logo. The user says the issue started right after replacing the internal SSD with a new one and restoring an image from the old drive. In UEFI setup, the new SSD is detected, but Windows Boot Manager is not listed in the boot order. Which action is the BEST next step to restore normal startup?
- A
Run Startup Repair from Windows installation media to rebuild the EFI boot files on the system partition
- B
Disable Secure Boot in UEFI so the restored image can load unsigned boot files
- C
Change the SATA controller mode from AHCI to IDE/Legacy to improve compatibility with the restored drive image
- D
Flash the laptop BIOS/UEFI firmware to the latest version so the SSD can be recognized as bootable
Show answer and explanation
Correct answer: A
Explanation
This scenario tests practical diagnosis of a UEFI boot issue after disk replacement and image restoration. The key evidence is that the SSD is detected in firmware, but Windows Boot Manager is absent from the boot order. On modern Windows systems using UEFI, booting depends on a valid EFI System Partition and boot files such as the Microsoft boot manager, along with a firmware boot entry that points to them. If imaging or cloning does not correctly restore the EFI partition or boot configuration, the device may appear in firmware but still fail with a "No bootable device" message. The best practice is to boot from Windows installation or recovery media and use Startup Repair first, because it is designed to fix common boot problems automatically. This aligns with Microsoft guidance for repairing Windows startup issues using Windows Recovery Environment tools before attempting more invasive changes such as firmware updates or storage mode changes.
- A. Correct.
Correct. In a UEFI-based Windows installation, the system normally boots using Windows Boot Manager entries stored in the EFI System Partition (ESP). If the SSD is detected but Windows Boot Manager is missing from the boot list after imaging or drive replacement, the boot files or boot configuration on the EFI partition may not have been restored correctly. Running Startup Repair from Windows installation media is the best next step because it can detect and repair missing or damaged boot files and rebuild the boot configuration for UEFI boot.
- B. Incorrect.
Incorrect. Secure Boot can block untrusted bootloaders, but in this scenario the stronger clue is that Windows Boot Manager is missing entirely from the boot order. That points to a missing or damaged EFI boot entry or boot files, not primarily a signature validation problem. Disabling Secure Boot is also not the preferred first troubleshooting step for a standard Windows restore.
- C. Incorrect.
Incorrect. Changing the controller mode to IDE/Legacy is not an appropriate fix here and can create additional boot problems. Modern Windows 11 systems normally use UEFI with AHCI or NVMe storage, and switching modes can prevent Windows from loading storage drivers correctly. The SSD is already detected, so the issue is not basic controller compatibility.
- D. Incorrect.
Incorrect. Updating firmware may be useful in some hardware compatibility cases, but the SSD is already visible in UEFI, which means the firmware recognizes the hardware. The more likely issue is that the restored image did not properly recreate the EFI boot structure or boot entry. A firmware update is not the best immediate action for this symptom.