Windows installer doesn't work?

You said the previous installs were to CSM or Legacy MBR. You've only just now begun trying to install UEFI to GPT.

The conversion is done when you wipe or delete all partitions down to Unallocated Space with an installer booted as a UEFI device. This both formats the drive GPT and invokes the Windows Boot Manager which is not showing up and is likely a firmware failure.

Can you borrow a UEFI PC to swap your SSD into it to install, then move it back to the target PC. Windows 10 is remarkably adaptive to new hardware without needing adaptive restore. If it will start it will swap out all drivers requiring several restarts. This will tell us important information and may complete the install.

By that I mean I format the disk in cmd using diskpart convert GPT. Now the ssd will come up as a GPT format disk and trying to continue installing gives an error that I cant install windows on it due to it being in GPT format. Deleting the partitions so the drive is all empty space, and then running clean in cmd doesnt work either.Trying to move on now gives me an error that the drive is not compatible with the hardware. Then I go into cmd, and format the disk as MBR, since it wont format the disk itself even blank, and it tells me that it cannot install now because of a MBR partition table. It seems to just not be compatible at all with legacy. At least using the uefi disk windows installer is able to finish, and just doesnt boot after. I did try booting the ssd on another rig with different hardware and I ended up at the same place. It seems to definitely be the program, the usb or the ssd. Everything else was swapped out. I will try those disk diagnostic programs you mentioned and get back to you though. I did only use disk check via the cmd in repair options, so it could still be a bad drive. I'll go test it and let you know the result.

Hi,

You are making things too complicated for yourself...

You are switching multiple things, but possibly not the correct combinations...

A UEFI HDD\SSD needs to be a GPT drive... A Legacy HDD\SSD needs to be MBR... Both NTFS...

This is not interchangeable...

Same thing with the Flash Drive... A UEFI Installation drive needs to be GPT\FAT32...

A Legacy Installation drive needs to be MBR\NTFS..

Both of the above conditions need to be met for a particular installation... There is no mix and match option... You may also need to select a "UEFI Flash" or "Flash" in boot options...

This type of confusion is one of the primary drawbacks of the introduction of UEFI Bios, and why I try to stick to Legacy... I do use UEFI at times for testing stuff like this, and on my HP Laptop and tablet that came that way, but avoid it on my primary desktop machines..

If you select your HDD as the boot device, it is Legacy.. Otherwise it would be WindowsBootManager...

It's hard to say what complications may have happened in one of your 1st attempts with both drives attached, but with the HDD removed you can make the SSD whatever you want...

Your attempts to put the SSD as a UEFI Boot Device may be failing due to the flash drive...

It may be that because of conflicting flash drive\bios issues that everything is there except for the boot files on the EFI partition... So no WindowsBootManager...

I'm thinking that without using RUFUS you might be out of luck fixing this issue...

One other option for Legacy Bios would be the Windows USB\DVD Tool to create the flash drive...

https://www.microsoft.com/en-us/download/details.aspx?id=56485

Your Legacy attempt failed as well... This may also be due to the installation media conflicting with your bios settings... 

Personally, I actually use two different flash drives for my installations... One specifically for UEFI, and one specifically for Legacy... Both burned with RUFUS... I already mentioned why...

You should not need CSM enabled to see your SSD if it not required for the HDD... UNLESS the SSD had already been set up as a GPT drive... Having it enabled is not a bad thing... it just not be a requirement to see the SSD...

You mentioned changing stuff to make "Active"... This suggests to me that you are using 3rd party Disk Management Tools...

You also mentioned updating your Bios... That could easily cause to work differently now, than they did during your original installation on the HDD...

What do you mean "in Legacy I've formatted it as both types?"  It's either Legacy/CSM which uses MBR file system or UEFI which uses GPT. 

What did you use to test the SSD?  Disk Check is not drive diagnostics, it only tests the file system.  Use one of the tools here:

https://merabheja.com/ssd-health-monitor/

https://mashtips.com/ssd-health-test-and-performance-monitor-tools/

I'm going back over your screenshots now.

I cannot run anything without CSM turned on. I'm unable to boot the usb or the ssd, nor my hdd. With CSM on I can boot the legacy media but it cannot install on the ssd. The uefi media appears to install on the ssd fine. It just won't boot. But I am able to use the ssd for other purposes, and checked the disk with no errors. In legacy I have formatted it as both types, and tried from a blank clean disk. Nothing works with the legacy media. Though my original hdd was installed using legacy if I remember right. It works fine. I still haven't been able to try with uefi on another drive because I cant find a spare so I'm not certain it's the installer. I have tried multiple usb sticks, have created media on 2 different PC's one of which is the rig I'm doing this on, redownloaded the creation tool multiple times and created install media multiple times. All SATA ports are enabled, I physically checked and the drive is plugged into port 1. Still does not work.