No bootable device found is one of the most alarming messages a computer can show.
One moment your PC or laptop is working.
The next, you turn it on and see a black screen telling you it can’t find anything to boot from.
To most people, this feels like the computer has completely failed.
The good news?
In many cases, the “no bootable device found” error is fixable, and data is often still safe.
This guide explains what the error really means, why it happens, and what we check first when a device with this problem arrives at our repair shop.
When a computer starts, it looks for something called a boot device.
This is usually:
The boot device contains the operating system — Windows, macOS, or Linux.
When you see no bootable device found, the computer is saying:
“I turned on, but I can’t see anything I know how to start.”
That does not automatically mean your data is gone.
This message appears before Windows loads, which instantly makes it feel serious.
There’s:
Just a blank screen and the words “no bootable device found.”
For many users, this is the moment they realise how much they rely on that internal drive.
Photos, documents, work files, emails — everything feels suddenly out of reach.
Because the system stops so early in the startup process, it gives the impression that nothing is working at all. There’s no chance to save files, no warning, and no obvious way forward.
That uncertainty is what makes this error so unsettling.
From a repair perspective, however, no bootable device found is a very common error. We see it regularly, and in many cases, the underlying problem is far less severe than it first appears.
There isn’t one single cause behind this message.
The no bootable device found error can appear for both simple and serious reasons — from a misconfigured setting to a failing drive.
That wide range of possibilities is exactly why proper diagnosis matters.
Without checking why the system can’t find a bootable device, it’s easy to assume the worst — or to attempt a fix that makes the situation worse.
This is one of the simplest causes.
The computer is told to:
This can happen after:
The drive is still there — the computer just isn’t looking at it.
✅ Yes
This is often a quick settings fix.
https://support.microsoft.com/windows/change-your-pcs-boot-order
If the drive doesn’t show up at all, that tells us a lot.
At this point, we check:
⚠️ Depends
If the drive is loose or not seated properly — easy fix.
If the drive has failed — repair may not be possible, but data recovery often is.
https://www.kingfishercomputers.co.uk/data-recovery/
This catches many people out.
The system was fine, updated overnight, and now it won’t boot.
The drive still works — Windows just can’t start from it.
✅ Very often yes
Rebuilding boot files frequently restores the system without data loss.
https://support.microsoft.com/windows/fix-windows-boot-problems
Boot files tell the computer where Windows lives and how to start it.
If they’re damaged or missing, the system stops immediately.
This is more common on systems that were already behaving oddly.
✅ Yes
In many cases, boot repair tools or manual fixes solve the issue.
This surprises people.
A brand-new PC or new SSD can still show this error.
To the computer, an empty drive is not bootable.
✅ Yes
This usually just requires correct setup and installation.
This is the more serious scenario.
Eventually, the drive fails completely and disappears.
❌ The drive itself usually isn’t
But data recovery may still be possible, depending on damage.
https://www.kingfishercomputers.co.uk/hard-drive-recovery/
Many guides online jump straight to “reinstall Windows”.
This can:
When no bootable device found appears, diagnosis comes first.
At Kingfisher Computers, we don’t guess, and we don’t jump straight to reinstalling Windows.
Every no bootable device found error is approached methodically, because the cause can range from a simple setting change to a failing drive. Guessing at this stage can cost data and make recovery harder.
We start by checking:
By working through these steps in order, we can clearly identify whether the problem is repairable, recoverable, or not economically worth fixing — and we explain that outcome in plain English before any work goes ahead.
Before panicking or assuming the worst, there are a few safe checks you can try yourself.
These won’t damage your data and won’t make the problem worse.
It sounds simple, but it matters.
Shut the computer down fully.
Wait 30 seconds.
Turn it back on.
Sometimes the error appears due to a temporary firmware glitch, especially after updates or sleep mode issues.
USB sticks, external hard drives, and memory cards can confuse the boot process.
If the computer tries to boot from:
You may see the no bootable device found error even though the internal drive is fine.
Unplug everything except:
Then try again.
Most computers let you open a one-time boot menu by pressing a key like:
If you can see your internal drive listed here, that’s a good sign.
It means the device is detected, and the issue is likely boot configuration, not drive failure.
This part is important, because well-meaning advice online can make things worse.
Reinstalling Windows without understanding the cause can:
If your files matter, pause first.
Repeated power cycles can:
If the error appears consistently, stop and assess.
Switching options like:
without knowing what they do can hide the drive or make the system unbootable even when the drive is healthy.
Sometimes, the focus shifts away from repairing the system and moves toward saving what matters most — your data.
This usually happens when the problem is no longer just a boot issue, but a sign that the storage itself is failing.
You’re likely in a data recovery situation if:
In these cases, the operating system cannot load because the computer physically cannot read the drive properly.
At this stage, continuing to power the device on, forcing restarts, or running repair tools can reduce recovery success by placing extra strain on already failing components.
This is why we often recommend stopping immediately and having the drive assessed professionally, rather than risking permanent data loss by continuing to experiment at home.
If the data is important, careful handling at this point makes all the difference.
https://www.kingfishercomputers.co.uk/data-recovery/
When a system comes in with this error, we follow a strict process.
We don’t guess.
We don’t rush.
When a device comes in with a “no bootable device found” error, we follow a structured diagnosis process rather than jumping to conclusions.
We check:
Each of these checks gives us a clearer picture of what’s actually going on.
Together, they tell us exactly which category the problem falls into — from a simple configuration issue to a more serious hardware failure.
Once diagnostics are complete, we don’t overwhelm you with technical jargon or worst-case scenarios.
We explain, in plain English:
If the honest answer is “don’t repair it”, we say so.
Our goal isn’t to sell unnecessary repairs — it’s to help you make the right decision with clear, honest information.
These aren’t rare edge cases.
They are situations we deal with every single week in the repair shop.
They also show why the “no bootable device found” message doesn’t always mean the worst.
A customer brought in a laptop that suddenly displayed no bootable device found after being left unused for several weeks.
The laptop would power on, but it went straight to the error message.
After checking the system, we found:
The computer had simply forgotten which drive to boot from.
Once the correct boot order was restored, the laptop started normally.
Outcome:
✅ Fixed in minutes, no data loss, no parts required
In this case, a Windows update had installed overnight.
The next morning, the laptop showed no bootable device found, even though it had worked perfectly the day before.
Our checks showed:
This meant the system could not start, even though the drive itself was fine.
We rebuilt the boot files and repaired the startup configuration without touching the customer’s data.
Outcome:
✅ Boot files rebuilt, system fully restored, data preserved
This was the more serious scenario.
The laptop powered on, but the drive:
This indicated a failing SSD rather than a software problem.
At this point, repair was no longer possible, but data recovery was still achievable.
We recovered as much data as possible and replaced the failed drive with a new, reliable SSD.
Outcome:
⚠️ Data recovered where possible, new drive installed, system rebuilt
Fixing a no bootable device found error is usually worth it when the problem is isolated and predictable, rather than a sign of wider failure.
Repair often makes sense when:
In these situations, repairs like boot file rebuilding, configuration fixes, or drive replacement can restore the system reliably without unnecessary expense.
Sometimes, the most sensible option is not to repair.
Replacement may be the better route when:
In these cases, repairing the boot issue alone may not prevent further problems down the line.
We’ll always explain this clearly and honestly, helping you decide whether repair, replacement, or data recovery is the best next step — without pressure or guesswork.
That message looks serious — and in some cases, it really is — but it’s not always the end of the road for your computer or your data.
In many situations:
What matters most is not rushing into the wrong action.
Jumping straight to reinstalling Windows, changing random BIOS settings, or repeatedly forcing restarts can turn a fixable problem into a much bigger one. The key is proper diagnosis before action, so you know whether you’re dealing with a simple configuration issue, corrupted boot files, or genuine drive failure.
If your computer won’t boot and you’re stuck staring at this message, bring it in and let us take a proper look.
We’ll carefully assess what’s still working, explain what’s gone wrong in plain English, and help you choose the right next step — whether that’s a quick repair, a safe data recovery, or honest advice on whether repair is worth it at all.
No guesswork.
No pressure.
Just clear answers and the right solution for your device.
