new SSD wont boot without manual selection in BIOS

Welcome to the Dell Community  @tccack 

What does the drive look like under "Disk Management"

To better assist you, the members would need the exact model number of your laptop/desktop???

Identify your Dell:

https://www.dell.com/support/contents/us/en/04/category/product-support/self-support-knowledgebase/locate-service-tag?dgc=SM&cid=226210&lid=spr2429124398&linkId=69606563

Best regards,

U2

PLEASE DO NOT POST ANY SERVICE TAGS!!!

Its an Inspiron 5548. Win10.

I cant describe the disk as its shown in disk management. It was cloned from my HDD using the acronis cloning tool. It used to boot just fine. Its only started doing this in the last few months. I am sure I did not have any BIOS update in the period of changing the drive.

I have attached an screenshot of the drive in windows.

https://www.dropbox.com/s/b7s1nhpdgvrk87k/Disk%20Management%20Screenshot.jpg?dl=0

Why is secure boot off?

@tccack  your cloning application probably didn't register the bootloader file on your new disk into the UEFI firmware.  Whereas Legacy BIOS systems boot from devices, UEFI systems boot from specific bootloader files on specific partitions of specific devices -- and those files have to be registered.  The options in the one-time boot menu you posted are generated dynamically based on scans for bootloader files on detected devices at a folder path defined in the UEFI spec.  That dynamic listing behavior is designed to allow booting from things like USB devices that are only attached temporarily and therefore wouldn't be registered in the firmware, but "permanent" bootloaders that can be used without manual selection need to be registered.  Macrium Reflect Free is a popular cloning tool and its Rescue Media includes a "Fix Boot Problems" routine that can address this.  You don't have to run the clone again, but if you download Reflect Free and make bootable Rescue Media, go in there and run Fix Boot Problems.  You should be fine after that.  The alternative would be to manually add the path to the Windows Boot Manager bootloader file in your BIOS, but that's a bit trickier.

And as @Saltgrass  noted, don't turn off Secure Boot.  Windows 8 and up, and its corresponding Windows PE 4.0 kernel and up, all support Secure Boot, so unless you're trying to boot something built on an older Windows kernel or something built on a Linux kernel that doesn't support Secure Boot, you can and absolutely should leave it on.  Many cloning applications use Windows PE, and again unless they're using an old version, they'll support Secure Boot.  If you turned it off just because you had boot issues and were wondering if that was the culprit, if Secure Boot is the problem, you will see a boot error message that specifically says that the bootloader did not pass the Secure Boot integrity check.  If you don't see that message, Secure Boot isn't your problem.  And if you DO see that message, then make sure that the requirement to disable Secure Boot is known for whatever you're trying to boot, because if you see that message when trying to boot something that SHOULD support Secure Boot, then it could mean that the bootloader has been infected, in which case you definitely don't want to keep using it.  Disabling it might allow that system to boot, but that would be rather like having your home alarm system go off and then just disabling it without bothering to check if maybe a burglar is in your home.

The only other reason to disable Secure Boot would be if you were trying to boot something that didn't support UEFI booting at all, i.e. it only supported Legacy BIOS booting.  But that's very rare now, and actually when Secure Boot is off, which allows Legacy OPROMs to be enabled as is the case on your system, you've allowed the system to support both Legacy and UEFI booting.  That can be a problem because some things can be booted either way, but they will behave differently based on how they're booted, so having both modes enabled increases the chances of you accidentally booting the "wrong" way.  For example, if you boot Windows install media in Legacy mode, it will install itself on your hard drive in Legacy mode rather than UEFI mode.  And if you boot Macrium Reflect Rescue Media in Legacy mode, it won't perform the correct fixes for a UEFI system.  By comparison, when Secure Boot is enabled, the system only allows UEFI booting, which avoids the possibility of accidents like that.

Thanks for the information. I will try the Macrium software.

PS The secure boot is actually ON again. The screenshot was taken during one of the many attempts to see if that had something to do with the booting problems.

So i tied the Macrium software. I built what it suggested (a recovery image I think).

The laptop still doesnt boot up straight to windows. Now when select the SSD to boot from I now get an extra step to pick Windows 10 or Macrium. Its essentially added a step.

I tried to create a new boot option in the BIOS. Selected the disk and found the efi file etc.

This didnt fix it either. Now I have yet another option to select in the BIOS as it wont boot directly to WIN10 after a restart.

Going around in circles a bit.