How To Fix No boot device found
Fix No boot device found Windows 10 problem
No boot device found or No bootable device found is a common error that can occur when trying to start your Windows 10 computer.
There are a number of potential causes for this error.
Mean of No bootable device found.
This message means that your
computer could not find a healthy boot device. This problem can occur if the
files needed to start the computer cannot be found.
A bootable device is any piece of
hardware that contains or can read the files needed to start a computer. A hard
disk, CD-ROM drive, DVD drive, and USB thumb drive are considered bootable
devices.
Why does Windows 10 display the error message No bootable devices found
Your computer's boot sequence is in
error.
Your bootable installation is not
recognized by your machine.
Your bootable devices are damaged or
corrupted.
It's not active on your Windows 10
system partition.
Your BIOS or CMOS settings are
incorrect.
Your device's boot disk MBR sector
is damaged.
Follow the steps given below to resolve this No boot device found issue.
Method 1- Remove and connect back all hardware components
You can first turn off your
computer, remove all hardware devices, then put
them back all properly. That can help check whether the BIOS
did not detect the system hard drive due to a loose connection and led to no bootable device issue. If
this doesn't solve your problem, move on to the next method.
Method 2- Reset the primary partition as active
The primary partition is the
partition where the operating system is installed. To start the operating
system successfully, it must be set to active. If it is accidentally set to
disable, it will bring up the No boot device found the issue. So,
please enable it again.
Step 1: Boot your PC up using the
Windows installation DVD. Click Repair your computer, then Language and Keyboard Layout to make your selections.
Step 2. If you are using Windows 10
and 8 installation DVD, click Troubleshoot and then Command
Prompt. If you are using Windows 7 installation DVD, in the System
Recovery Options screen, select the first choice Use recovery tools
that can help…, Windows 7 OS, and click "Next". Select Command Prompt on the subsequent window.
Step 3: Type the following commands
one at a time in the elevated Command Prompt window and then hit
"Enter."
lit disk
select disk 0: 0 is the disk number
of the system hard disk.
list partition
select partition 1: 1 represents the
number of your system
partition.
Active
Method 3 - Check the internal hard disk status
During Windows starts, the no bootable device found problem may appear if the internal hard
disk has some disk errors. By using the CHKDSK.exe tool, you can determine its
state. You can achieve this by using method 2 to open the Command Prompt
window. The Windows operating system is typically installed on the C drive,
therefore run the command "chkdsk c: /f /x /r" to check for faults
and, if necessary, rectify them.
Method 4 - Check for corrupted files using SFC
You can also use the SFC commands to
scan and fix corrupt files.
First, open a command prompt window
and enter the following command. Change C and D to the relevant drive letters
for the system-reserved partition and your current Windows installation.
sfc /scannow /offbootdir=C:\ /offwindir=D:\Windows
Press Enter to begin running
the command. Exit once the process is complete, then restart your computer.
Method 4 - Repair corrupted MBR
Windows 10 may not have a bootable
device due to a corrupted MBR. You can fix the MBR in this case by taking the
following actions:
Insert the Windows installation
media into your computer and boot from it.
When you see the "Install
now" window, choose the language and location, and then click "Repair
your computer."
Select Troubleshoot and then Command
Prompt on the Advanced options screen.
Enter each of the following command
lines in the Command Prompt. Type "y" and press Enter if you are
asked if you want to add a new installation to the boot list.
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Restart your computer after quitting
Command Prompt.
After following the above steps, I think your No boot device found the problem is solved.
No comments