PC won't boot to Windows 10 from SSD

Hi,

I don't have a clue as to why your EFI is in the Root, and not a separate partition... That is the default when windows installs...

Check through the UEFI Boot Drive BBS Priorities options and see what you get..

Is your machine encrypted in some fashion... I'm wondering if the selection of a Encryption Key at Boot is part of the problem...

I don't have a clue as to why the flash drive created with RUFUS would require a password for the SSD... I use RUFUS a lot, and have never seen that before.. Did RUFUS mention anything about a password when creating the flash drive ?

One thing I have noticed with RUFUS is that sometimes when you change one of the menu options, it will cause another to change... Sometimes the FAT32 or GPT will change when you select the Image you want to use...

Also look to see if your Bios has a "Secure Boot" setting... If it does, Disable it temporarily...

BTW... You want the Legacy USB Support Enabled..

I just flashed the ISO of Windows 10 to an USB with Rufus (https://www.windowscentral.com/how-create-windows-10-usb-bootable-media-uefi-support).

The first boot (UEFI) I needed to fill in my password of the SSD Windows User, but the repair failed.

The last two commands of BOOTREC even didn't succeed.

The second boot (USB KEY) I didn't need to fill in the password and FIXBOOT did work, but REBUILDBCD not. Same errors as above.

MediaCreationTool1803 was on the USB stick. 

A repairstation created on the newest version of Windows 10 has the same results as above.

Both don't have a EFI-partition, but do have a EFI folder on the root.

See some screenshots attached. 

When I disable Legacy USB Support (like below) the USB drives for repair aren't found.

Hi,

I'm surprised Gparted will make anything Active on a UEFI machine with a GPT drive... That is not supposed to be possible...

GPT drives no not use "Active" for the Boot Device... UEFI machines boot from the Windows Boot Manager that is located on a 150MB or so, Fat32 partition...

Only the older Legacy Bios uses "Active" partitions for the boot device...

Regardless... Your Boot Device would be the EFI partition... Not the entire SSD..

Do you have a EFI partition on both drives , or just possibly the HDD ?

I think you need to select "UEFI USB Key" if there is such a thing...

Not in your Bios, but the Boot Options menu I mentioned... This is separate from the actual Bios and usually displays more "One Time" Boot Options...

I can't find any pictures of what Gparted flags look like as far as "Active" or "Boot Device"...

I'm just about positive the errors you are getting with the BootRec stuff is because of how you are booting with the flash drive... I recently had a similar problem...

BTW... What Windows Build  is on the Flash Drive... Build 16299 has issues with some of it's repair functions

BIOS indeed names the mediatool usb UEFI and it is already FAT32 formatted.

I made the HDD partition active. 

BOOTREC /FIXMBR -> success

BOOTREC /FIXBOOT -> access denied

BOOTREC /REBUILDBCD -> 1 installation found on D: (SSD). When I accept the installation to boot list, I get an error: systemdevice not found.

My volumes (according to diskpart) are mixed up: C: = HDD, D: = SSD (which was the opposite).

EDIT: I can make the partition of the SSD active again. This seems not to be saved, closing diskpart and opening it results in the same statusupdate. I even can mark it as active or inactive twice and not get a message that it currently is one of them already.

EDIT2: In GParted the SSD has a boot flag, meaning it is active already.

EDIT3: I can boot the USB as "USB KEY", not as UEFI. After that the BUILDBCD works again, FIXBOOT still access denied. I do see Go to WIndows 10 Home, but immediately got a reboot then. Same operating system wasn't found when booting from SSD.