Pattern to record: Windows Boot Manager or the expected loader is absent despite a healthy drive.

Record the boot configuration

Record the laptop model, current firmware settings and whether the SSD is detected before changing boot options. Preserve any BitLocker recovery information so a firmware change does not turn a startup fault into a data-access problem. One possible explanation is that the reference to a valid operating-system loader has been deleted or reordered.

Preserve recovery options

Keep stable power and do not interrupt a firmware write. Selecting an unrelated entry may hide the real storage problem.

Firmware and hardware checks

1. Record current settings, check hardware detection and compare a known recovery path before updating firmware.
2. Verify the loader on disk and inspect the UEFI boot list.

Recovery and startup checks

If the checks support this cause, recreate the correct signed entry and place it in a sensible order. Verification should cover cold boot, restart, storage detection, security state, sleep and Windows loading.

For an assessment of your Windows laptop, contact AEPC in Burswood or call 027 908 8880. Provide the model and the conditions that reproduce this problem. Workshop visits are by appointment.