Open msconfig and choose boot tab, click safe boot and restart your machine enter the bios when it is starting
once in the bios change from raid to ahci. save changes and reboot open msconfig again select boot tab then uncheck safe boot and then restart your machine. It should have booted normally from your new evo drive.
Check if UEFI boot mode is set and SATA operation (Controller) set to AHCI in the BIOS. Please watch video in the link below for addition information about BIOS settings. Good darn video I like to add....:BigSmile:
How to Fix a Boot Up Problem (Official Dell Tech Support
From within Windows, open Command Prompt and run "bcdboot C:\Windows". That will among other things cause Windows to register itself in the UEFI firmware. What cloning tool did you use? The good ones take care of this.
Thanks for the headups my good friend however, I did shared a video (Dell Tech) in my post that help explained BIOS settings. If you haven't watch it yet, I suggest you do so. Thanks again
@LSUFAN51and @BonesB, please don't suggest tinkering with the SATA mode. The problem is NOT that the cloned instance won't boot from the NVMe SSD. It's simply that it doesn't appear in the boot order. Changing the SATA Operation mode won't change that, and it can create new problems.
Thanks for the headups my good friend however, I did shared a video (Dell Tech) in my post that help explained BIOS settings. If you haven't watch it yet, I suggest you do so. Thanks again
I did watch it, and it doesn't address this scenario. The OP says that he can successfully boot from his new SSD by directly selecting it in the F12 menu, but it's not listed in the UEFI boot order, which means the system won't try to boot from it automatically. That means the Windows Boot Manager needs to be registered in the UEFI firmware, which is accomplished via BCDBoot. You can also use the Add Boot Option in the BIOS Setup, but that's a bit more effort, and the video you linked didn't show how to do that. It showed how to adjust the boot priority of systems that use Legacy BIOS mode, but that isn't helpful for a UEFI scenario.
So why dont you jphughan tell the guy what his problem is and how to solve it. By the way i am writing this on a fully functioning machine with no problems. AW17 R5 with Samsung Evo. Took me 15mins to install and configure.
Command Prompt tells me "Failure to copy boot files" .. What could this be?
EaseUS Todo was the cloner..
How do I set up a new boot option in BIOS setup? I've tried, but it asks me to name a file, and I don't know where to direct it.
Thanks for the help so far!
Looking at my UEFI system, after you click Add Boot Option, enter "Windows Boot Manager" as the Name. In the File System list, you'll need to select your SSD; if that option can't be changed because you only have one drive, then no worries. For the File Name, click the "..." button, change the File System dropdown if needed until you see an "EFI" listing below, then select that, navigate to Microsoft, then Boot, and select Bootmgfw.efi.
You may also want to look at Macrium Reflect Free for future cloning/imaging needs. I'm active on the Macrium forums and I see several users who say they came from EaseUS or Acronis and find Reflect to be a superior product. Their bootable "Rescue Media" even has a Fix Boot Problems function that will fix things like this.
Looking at my UEFI system, after you click Add Boot Option, enter "Windows Boot Manager" as the Name. In the File System list, you'll need to select your SSD; if that option can't be changed because you only have one drive, then no worries. For the File Name, click the "..." button, change the File System dropdown if needed until you see an "EFI" listing below, then select that, navigate to Microsoft, then Boot, and select Bootmgfw.efi.
Hi, I tried as Bootmgfw.efi but that didn't do it. However, I tried everything in there and bootx64.efi worked. It's location was: EFI; Windows; Boot; Bootx64.efi. It didn't work until I disabled something called "Windows Boot Manager" that I found in the F12 menu that also appeared in the F2 menu.
Now it boots from power button on. Does that mean I am booting x64, and is that somehow undesirable?
Looking at my UEFI system, after you click Add Boot Option, enter "Windows Boot Manager" as the Name. In the File System list, you'll need to select your SSD; if that option can't be changed because you only have one drive, then no worries. For the File Name, click the "..." button, change the File System dropdown if needed until you see an "EFI" listing below, then select that, navigate to Microsoft, then Boot, and select Bootmgfw.efi.
Hi, I tried as Bootmgfw.efi but that didn't do it. However, I tried everything in there and bootx64.efi worked. It's location was: EFI; Windows; Boot; Bootx64.efi. It didn't work until I disabled something called "Windows Boot Manager" that I found in the F12 menu that also appeared in the F2 menu.
Now it boots from power button on. Does that mean I am booting x64, and is that somehow undesirable?
Works now so thanks!
In the UEFI spec, the path \EFI\Boot\Bootx64.efi is defined as the standard bootloader path. UEFI-compliant systems are supposed to search the readable partitions (usually just FAT and FAT32) of any detected devices at boot time for that file and list it in the one-time boot menu if they find it. That's why your SSD showed up in the F12 boot menu. As for the existing Windows Boot Manager entry that you disabled, that was probably left over in your firmware from your previous hard drive, and if you had checked the file path for that entry, you would probably have seen it pointing to the same file I mentioned earlier. I'm not sure why that didn't work when you manually created the new one since that's how all Windows environments configure themselves during a clean install, and I have no idea why the Windows bootloader doesn't just use the standard Bootx64.efi file that also exists on that partition, but if your system is booting normally now then I wouldn't worry about it. Glad you're sorted! :)
BonesB
1 Rookie
•
83 Posts
1
May 30th, 2018 08:00
Hi i just installed an Evo 970 in a 17 R5
Open msconfig and choose boot tab, click safe boot and restart your machine enter the bios when it is starting
once in the bios change from raid to ahci. save changes and reboot open msconfig again select boot tab then uncheck safe boot and then restart your machine. It should have booted normally from your new evo drive.
LSUFAN51
4 Operator
•
6.5K Posts
0
May 30th, 2018 08:00
Check if UEFI boot mode is set and SATA operation (Controller) set to AHCI in the BIOS. Please watch video in the link below for addition information about BIOS settings. Good darn video I like to add....:BigSmile:
How to Fix a Boot Up Problem (Official Dell Tech Support
https://youtu.be/uJcqHY7YbmA?list=PLdLDGmnHB07NVpbsbTGeiW-NLjpVZufxB
jphughan
9 Legend
•
14K Posts
0
May 30th, 2018 09:00
From within Windows, open Command Prompt and run "bcdboot C:\Windows". That will among other things cause Windows to register itself in the UEFI firmware. What cloning tool did you use? The good ones take care of this.
LSUFAN51
4 Operator
•
6.5K Posts
0
May 30th, 2018 09:00
:BigSmile:
Hi jphughan
Thanks for the headups my good friend however, I did shared a video (Dell Tech) in my post that help explained BIOS settings. If you haven't watch it yet, I suggest you do so. Thanks again
jphughan
9 Legend
•
14K Posts
0
May 30th, 2018 09:00
@LSUFAN51and @BonesB, please don't suggest tinkering with the SATA mode. The problem is NOT that the cloned instance won't boot from the NVMe SSD. It's simply that it doesn't appear in the boot order. Changing the SATA Operation mode won't change that, and it can create new problems.
jphughan
9 Legend
•
14K Posts
0
May 30th, 2018 11:00
I did watch it, and it doesn't address this scenario. The OP says that he can successfully boot from his new SSD by directly selecting it in the F12 menu, but it's not listed in the UEFI boot order, which means the system won't try to boot from it automatically. That means the Windows Boot Manager needs to be registered in the UEFI firmware, which is accomplished via BCDBoot. You can also use the Add Boot Option in the BIOS Setup, but that's a bit more effort, and the video you linked didn't show how to do that. It showed how to adjust the boot priority of systems that use Legacy BIOS mode, but that isn't helpful for a UEFI scenario.
jphughan
9 Legend
•
14K Posts
0
May 30th, 2018 11:00
See my earlier post where I did exactly that.
BonesB
1 Rookie
•
83 Posts
0
May 30th, 2018 11:00
So why dont you jphughan tell the guy what his problem is and how to solve it. By the way i am writing this on a fully functioning machine with no problems. AW17 R5 with Samsung Evo. Took me 15mins to install and configure.
todski
5 Posts
0
May 30th, 2018 12:00
Command Prompt tells me "Failure to copy boot files" .. What could this be?
EaseUS Todo was the cloner..
How do I set up a new boot option in BIOS setup? I've tried, but it asks me to name a file, and I don't know where to direct it.
Thanks for the help so far!
BonesB
1 Rookie
•
83 Posts
0
May 30th, 2018 12:00
If its any help i used the Samsung data migration tool to do mine. Could not have been easier.
http://www.samsung.com/semiconductor/minisite/ssd/download/tools/
jphughan
9 Legend
•
14K Posts
0
May 30th, 2018 14:00
Looking at my UEFI system, after you click Add Boot Option, enter "Windows Boot Manager" as the Name. In the File System list, you'll need to select your SSD; if that option can't be changed because you only have one drive, then no worries. For the File Name, click the "..." button, change the File System dropdown if needed until you see an "EFI" listing below, then select that, navigate to Microsoft, then Boot, and select Bootmgfw.efi.
You may also want to look at Macrium Reflect Free for future cloning/imaging needs. I'm active on the Macrium forums and I see several users who say they came from EaseUS or Acronis and find Reflect to be a superior product. Their bootable "Rescue Media" even has a Fix Boot Problems function that will fix things like this.
todski
5 Posts
0
May 30th, 2018 15:00
Hi, I tried as Bootmgfw.efi but that didn't do it. However, I tried everything in there and bootx64.efi worked. It's location was: EFI; Windows; Boot; Bootx64.efi. It didn't work until I disabled something called "Windows Boot Manager" that I found in the F12 menu that also appeared in the F2 menu.
Now it boots from power button on. Does that mean I am booting x64, and is that somehow undesirable?
Works now so thanks!
jphughan
9 Legend
•
14K Posts
1
May 30th, 2018 16:00
In the UEFI spec, the path \EFI\Boot\Bootx64.efi is defined as the standard bootloader path. UEFI-compliant systems are supposed to search the readable partitions (usually just FAT and FAT32) of any detected devices at boot time for that file and list it in the one-time boot menu if they find it. That's why your SSD showed up in the F12 boot menu. As for the existing Windows Boot Manager entry that you disabled, that was probably left over in your firmware from your previous hard drive, and if you had checked the file path for that entry, you would probably have seen it pointing to the same file I mentioned earlier. I'm not sure why that didn't work when you manually created the new one since that's how all Windows environments configure themselves during a clean install, and I have no idea why the Windows bootloader doesn't just use the standard Bootx64.efi file that also exists on that partition, but if your system is booting normally now then I wouldn't worry about it. Glad you're sorted! :)
todski
5 Posts
0
May 31st, 2018 12:00
Yeah, happy, boots in seconds to FO4 :D