Boot issues after windows install attempt

I have a Samsung 850 Evo 1TB which is being used as my boot drive. I also have a Samsung SM951 m.2 NVME 128GB drive which is much faster. I used to have windows installed on my m.2 drive, but due to unfortunate circumstances, everything on my pc was wiped and the 850 Evo was used as the boot drive. Since the 850 Evo boots in under 20 seconds, I haven't been hard pressed to switch back to the m.2 drive as a boot drive. I was bored today and decided to try installing windows onto the m.2 drive. As far as I know, I did NOTHING to the 850 Evo... Well, now I am getting the blue screen at startup saying:
"Recovery
You're PC/Device needs to be repaired.......
File: \Windows\system32\winload.efi
Error Code: 0xc000000e

I've tried everything I can find readily available to me on the internet such as all of the repair features you can get to by pressing F1 on the above mentioned screen. I've performed the bootrec command functions, no help.
The only thing that has helped is pressing f1, going to the advanced options, more options, restart, pressing 8 to disable antimalware detection during startup. Only by doing that can I get to my desktop. I've found a way to permanently disable the antimalware detection during startup, but I don't want to do this. I want my computer to boot how it did before, normally. Any help is greatly appreciated.

Before I figured out I had to disable the anti-malware to get to the desktop, I tried this. In the windows usb boot drive I created, there's an option to format a drive. I used that tool to format. I can try formatting again from inside of windows, but I remember during one of those bootrec commands, it output that there was only 1 windows install found. Maybe there are some residual files let over from the format of the m. 2 drive? I'll check into it once I get home tonight. Ty!

The startup repair I used from the F1 menu didn't work, but I like this idea. I'm going to try using the utility you suggested once I am able to later tonight. I will report then with the results.

I think I found the post you're mentioning: Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
When I try to download, it tells me 1.3 or so GB and an hour to download. Then it proceeds to stall and finish downloading in under a minute as a corrupt file. What am I doing wrong?

Edit: I found another rescue/repair toolkit, it took me to the same host to download the file from. That isn't downloading either...
Edit2: Tried downloading something else just to see if I could download anything. Firefox installer downloaded fine.

Free Download Manager suggested on post #1509 of your above referenced link worked perfectly. I put the ISO on my flash drive, changed boot order and was able to boot into the recovery ISO now on the flash drive. From there, I used the recovery tool in Macrum Reflect PE which ran without any errors. I rebooted, changed boot order to normal SSD and this booted me to an option to Start with the Windows 10 install on Volume 6 or on Volume 2. A quick Google search yielded me with a Reddit post. The Reddit post advised using the msconfig tool in Windows; Windows key+R, type msconfig, boot tab, delete the Windows that DOES NOT say Current OS. I deleted it and rebooted and it brought me straight into my Desktop just the way I left it. Thank you very much for your guidance. I'm going to be sure to keep this recovery ISO on a flash drive at all times!

I faced a similar kind of problem recently.

I have 4 Windows OS on my PC.

1. Windows 8.1 32 bit
2. Windows 7 64 bit
3. Windows 7 64 bit on SSD
4. Windows 10 64 bit.

As my Windows 10 corrupted, I formatted it and reinstalled it.
Then I got a different BCD error. But I think your problem seems the same.

I loaded the Windows 10 ISO into a USB flash drive and made it a boot drive using Rufus.
Using BIOS options I booted using USB drive, but my bootloader was corrupt..

So I went to command prompt using Repair functionality of Windows 10 installation disk.
There I entered the bootrec commands like rebuild bcd, fix bootmgr, etc.

But still I got the BCD error. Then I realized my mistake.

I had 3 disks on my PC.
1. 80 GB HDD - Disk 0
2. 1 TB HDD - Disk 1
3. 120 GB SSD. - Disk 2

But after applying the bootrec commands I was booting from Disk 1, so I was getting the error.
Finally I realized the mistake and found that Disk 0 was my boot disk.
So when I changed the boot order to Disk 0, it logged in successfully.

I did not delete any OS or format any drive.
But the boot entries were deleted.

For this you can use EasyBCD to recreate the entries once you login to any Windows OS for multi-Windows OS.

Hope this helps !!!. :)