Fixing “Bootable Device Not Found” on Laptops & Desktops (NZ Guide)

Why this happens (in plain English)

That message means your computer can’t find something it can start Windows from. Common reasons include:

• Boot order changed (e.g., trying to boot from a USB stick or network first)

• Drive not detected by BIOS/UEFI (loose connection or failed drive)

• Corrupted Windows boot files (after an update, power cut, or crash)

• Switched between Legacy/CSM and UEFI modes, or MBR/GPT mismatch

• Failing SSD/HDD (SMART errors, sudden slowdowns beforehand)

• Encrypted disks (BitLocker) not unlocking after hardware/firmware changes

TL;DR (quick wins) ✅

• Remove any USBs/SD cards & restart.

• Enter BIOS/UEFI and choose Windows Boot Manager (if present).

• If the drive isn’t listed at all, stop and protect your data—seek help.

• We can diagnose, recover data, and repair quickly in East Auckland.

Step-by-step: Safe checks you can do (no tools required)

1) Power & peripherals

• Unplug extra USB devices (thumb drives, external HDDs, printers).

• Check there’s no disc in the DVD drive (if you have one).

• Try a full power cycle: shut down, unplug charger/power for 30 seconds, then restart.

2) BIOS/UEFI basics (safe to view, not breakable)

• Tap F2 / Del / F10 / Esc (varies by brand) right after powering on.

• Confirm the date/time looks normal (wildly wrong time can hint at CMOS battery issues).

• Under Boot:

  • Set Windows Boot Manager (for UEFI systems) to the top.

  • If you only see “Network/PXE” or a USB entry—and no internal drive—the laptop/PC isn’t seeing the disk. Stop here to avoid data risk.

3) Try Windows recovery (if available)

• If you see Automatic Repair or Advanced options, choose:

  • Startup Repair → follow prompts.

  • System Restore (if you had restore points).

  • Uninstall updates (Recent quality/feature update) if the error started after an update.

  • Command Prompt (advanced users only—if you’re unsure, skip; we’ll handle safely).

4) Signs your drive may be failing

• Prior slow boot, clicking/grinding sounds (HDD), random freezes.

• Drive not detected in BIOS/UEFI at all.

• Repeated recovery loops.
  If any of these fit, avoid repeated power-ons—they can worsen failures.

Real-world examples we see in Auckland

• Laptop after Windows update: Boot order flipped to a USB recovery entry; we restored Windows Boot Manager and updated firmware—no data loss.

• Gaming PC after moving house: Impact caused a marginal SATA connection; drive intermittently vanished. We reseated, tested, then recommended an SSD upgrade with data clone.

• Small business workstation: Ageing HDD with rising reallocated sectors; cloned to a new SSD, repaired boot records, zero downtime next day.

Quick self-checks & tips (easy, safe) 🧪

• Try a different power outlet and original charger (voltage dips can cause odd boot issues).

• If you have a docking station, undock and boot standalone.

• Listen quietly: HDD spinning/clicking vs SSD (silent). Clicking often means “stop and seek help”.

• On laptops with function-row boot menus (e.g., F12), briefly check if “Windows Boot Manager” appears. If not, don’t force it—get a diagnosis.

When to call a pro (to protect your data)

• BIOS/UEFI doesn’t show your internal drive.

• You suspect BitLocker or company encryption is enabled.

• You see repeated Automatic Repair failures or blue screens.

• There’s valuable data and no recent backup.

• You changed settings and now see different errors—it’s time to stop and get help.

What we do at AEPC (Auckland East PC)

• Same-day diagnosis: Hardware vs software in ~30–60 mins onsite.

• Non-destructive tests: We check SMART health, interface, and firmware safely.

• Boot repair: UEFI/MBR rebuilds, BCD fixes, Windows repair installs.

• Data-first approach: If the drive is failing, we stabilise and clone before repair.

• Part sourcing: Quality SSDs/HDDs from trusted vendors; firmware updates applied.

• Migration & optimisation: Seamless move to SSD, latest drivers, fast boot.

• Warranty & aftercare: Parts warranty + clear backup plan recommendations.

Prevention & best practices (NZ-focused)

• Use an SSD for the OS; they’re faster and more resilient to bumps.

• Keep Windows updates current, and install OEM firmware/BIOS updates carefully.

• Enable regular backups (File History or cloud). Test restore once.

• Avoid cheap USB hubs as permanent boot devices—they can confuse boot order.

• On desktops, use a UPS if you’re in a power-fluctuation area.

• After any repair or move, do a quick BIOS check to confirm your drive is listed.

Call, visit, or book today

AEPC – Auckland East PC
📍 9/28 Torrens Road, Burswood, Auckland 2013
📞 0279-088880
📧 akleastpc@gmail.com
🕘 Mon–Fri: 9:00 AM – 5:00 PM
🕘 Sat & Sun: 9:00 AM – 4:00 PM (reservation required)

Walk in with your device, or call ahead—we’ll prioritise data safety and get you booting again fast.

FAQ

Q1: I only see “PXE” or “Network boot”. What does that mean?
Your PC is trying to boot from the network because it can’t find a local bootable drive. Often the internal drive isn’t detected or the boot order changed.

Q2: Will I lose my data?
Not necessarily. If the drive is healthy, we repair boot files. If it’s failing, we clone first. Turn the device off and bring it in to improve your chances.

Q3: Is this a BIOS battery (CMOS) issue?
A flat CMOS battery can reset time and boot order. We can replace it and reconfigure settings; desktops are more prone due to age.

Q4: Can I fix this with a Windows USB installer?
Sometimes, but creating/installing incorrectly can overwrite data. If you’re unsure, let us handle a non-destructive repair first.

Q5: My drive shows in BIOS but not in Windows.
That points to partition/bootloader issues. We rebuild UEFI/MBR structures and verify file system integrity.

Q6: Should I upgrade to an SSD now?
Yes—faster, more reliable, and ideal if your old HDD shows early health warnings. We can clone your system as-is to minimise downtime.

Q7: Do you support Macs with this error?
Yes. Macs show it as a flashing folder or “No bootable device”. We handle APFS recovery, macOS reinstall, and SSD swaps.