1 Rookie
•
4 Posts
0
42219
April 22nd, 2020 06:00
No boot device found after changing boot mode from Legacy to UEFI in DELL 5559
DELL Inspiron 5559: No boot deice found when boot sequence changed from Legacy to UEFI mode . After the original harddrive crashed, Hard drive was replaced with new Seqate 1TB Barracuda and installed windows 8.1 which later was upgrated to windows 10PRO. Not sure if the windows 8.1automatically set to Legacy boot. It worked in legacy mode until now. As more partitions were needed, now, removed all logical partitions, kept 'C' primary partition , two system partitions and converted the drive from basic to GPT which was done successfully. After that, tried to change the BIOS boot option from Legacy to UEFI, then the system sends the error message: No Boot Device Found. Needed Help!!



jphughan
9 Legend
•
14K Posts
0
April 30th, 2020 12:00
@Old FarmerAs I said in my earlier post, when dealing with a disk that contains an OS, a simple conversion from MBR to GPT isn't enough to make your OS disk bootable in UEFI mode. As for creating a path to Bootx64.efi, you can't just type that and expect it to work. The Bootx64.efi file you're pointing to has to actually exist on your disk, specifically residing in an actual ESP (EFI System Partition). That is created by default when you install Windows in UEFI mode in the first place, and it also would have been created if you had used the MBR2GPT utility I mentioned above, which takes additional steps to convert an OS disk from supporting Legacy BIOS booting to UEFI booting. But it would NOT have been created on a disk originally set up for Legacy BIOS booting, nor would a simple GPT conversion have created it. And since Legacy BIOS mode doesn't support booting from GPT disks and you can't convert a GPT disk back to MBR, you're basically stuck. In theory you might be able to manually create an ESP on your GPT disk and get the necessary bootloader files copied onto it, but I'm not sure that would work, and it would almost certainly be impractical to try to help you to do that over an Internet forum. For one thing, Microsoft's guidelines specify that an ESP has to be located before the OS partition, not after it, which is harder to achieve when you have existing partitions on disk.
At this point I would probably recommend that you back up whatever data you need on your disk, then switch your system to UEFI mode, boot Windows 10 installation media, and at the step in the wizard asking you where to install Windows, delete ALL partitions on your internal disk until it shows as just a single "Unallocated space" entry, then choose to install there. Windows will set itself up properly for UEFI booting upfront in that case, including creating the appropriate partitions. If you know what you're doing, you could first capture an image backup of your Windows partition before performing a clean installation, so that AFTER you complete a clean installation, you can restore just the Windows partition from that image backup over the new one that was created during the clean installation, WITHOUT touching any of the other partitions created on the disk. In that case, your system would maintain UEFI boot support, because your disk will now have an ESP that you would NOT be overwriting during the image restore, but you'll have your Windows environment back rather than having to rebuild everything. But if you DON'T know how to do that, then that too is something that's probably more than I really want to try helping someone achieve by posting back and forth on a public forum. I just wanted to suggest that in case you would know how to take that idea and run with it. Macrium Reflect is a popular imaging tool and it has a free version that would be perfectly usable for this purpose, fyi.
Clintlgm
3 Apprentice
•
1.5K Posts
0
April 22nd, 2020 15:00
You will need to set up an EFI partition making your current windows OS bootable in UEFI mode.
https://www.tenforums.com/installation-upgrade/52837-moving-recreating-efi-partition.html
Some people have figured out how to boot to safe mode then on the next boot there UEFI OS booted? I have no Idea how that works
I know you can use Macrium Reflect to create a Disk Image or just a C: Partition Image to an external drive.
The do a quick install of Windows 10 shut down after the install do not up date.
Use Macrium Reflect to Restore your C: Image to the C: of the new OS it should boot after with you old C drive data and OS
jphughan
9 Legend
•
14K Posts
0
April 22nd, 2020 16:00
@Old Farmer when you're dealing with a disk containing a Windows installation, you can't just convert the disk from MBR to GPT. In order to boot an OS in UEFI mode, the disk needs to have an EFI System Partition that contains UEFI bootloader files. Windows has a utility called MBR2GPT that can convert the disk in a way that adds that partition. Despite the name of that tool, it actually does more than just a simple MBR to GPT conversion. So switch your system back to Legacy mode, boot into Windows, and use that utility. It will perform the conversion, and at that point you'll have to switch your system to UEFI mode before you'll be able to boot from that disk again. You can find full documentation of the MBR2GPT utility here: https://docs.microsoft.com/en-us/windows/deployment/mbr-to-gpt
Old Farmer
1 Rookie
•
4 Posts
0
April 22nd, 2020 20:00
OK, It all started when I changed the Hard drive from MBR To GPT !
As the harddrive gave up on my DELL notebook (2017 with i7 processor), I have replaced it with a 1TB harddrive and installed Windows 10 on it with Legacy boot option. Worked fine till today. As Dell sent an update on the BIOS, when I recognized I have a LEgacy boot instead of UFEI boot option, I deleted all partitions and kept three primary partitions and converted the disk from MBR to GPT. I saw the message that the disk was converted successfully, change the boot options to UFEI. SO, I booted the notebook and changed the boot option to UFEI. THen, I got the dreaded message, " No boot Device Found" because I didn't see no bootable device under UFEI boot option listed! So, I added the boot option with the file: /EFI/BOOT?BOOTX64.EFI and gave the name, "WIndows Boot Manager". That didn't work. So, I switched back to Legacy mode by disabling the secure boot mode as all the boot options were listed under Legacy mode. ( I had a hunch that disk conversion from MBR to GPT is creating the problem). THat didnt work either. I see the message No bootable device. What should I do
Old Farmer
1 Rookie
•
4 Posts
0
April 30th, 2020 12:00
Sorry the link you gave didn't work!
nyc10036
4 Operator
•
5.6K Posts
0
April 30th, 2020 12:00
@Old Farmer
I deleted all partitions and kept three primary partitions
is confusing