Last reply by 05-10-2022 Unsolved
Start a Discussion
1 Copper
1 Copper

No bootable device found


  •  LATITUDE E5440
Replies (3)
8 Xenon

Go into setup (f2 at powerup).  Does the hard drive show in setup (look under Drives)?

If it does not, shut down, remove the battery and hold the power button for 30 sec.  Disconnect and reconnect the drive - if it still does not show, it's toast and will need to be replaced.

If it does show, restart, press F12 and run the Dell diagnostics, which will test the drive.  If it fails, replace the drive; if not, you're in for a Windows reinstall.


5 Tungsten

The first thing to check is which device is selected as the primary boot. To do a quick check please use F11 to launch the manual boot selection.

  1. Restart the system
  2. Press F11 during POST to enter the Boot Manager
  3. Select the correct Hard Disk drive (Virtual Drive), where the OS is installed
  4. Boot from this device

If the system now boots into the operating system, the hardware is fine and there is a boot order conflict in the BIOS settings. The most likely cause for this is that the system is set to boot from CD/DVD and/or USB before the drives, which is a logical setting. To resolve this, just ensure you do not have a USB or CD/DVD inserted into the system.

Note: The Error can be caused by wrong settings in the boot mode, too. An OS installed in UEFI mode cannot boot in BIOS mode and vice versa.

You can change the boot order setting permanently in the System Setup to boot from the drive first. To change this:

  1. Restart the system
  2. Press F2 during system start to enter the System Settings
  3. Change the Boot Sequence in the Boot Settings
  4. Leave the menu via Exit in the upper right corner of the screen

Note: After this, you will require pressing F11 if you wish to boot from a CD/DVD or USB at a later date.

3 Argentum


Quite a common occurence.


A BIOS update can reset parameters and "lose" an EFI drive, reverts to legacy mode and defaults to network PXE booting.  Solution adjust BIOS accordingly.


The drive may have failed and others, in this thread, have covered that far more eloquently than I could.

Latest Solutions
Top Contributor