Windows 10: Finding EFI system partiton of unbootable Windows OS while booted to another volume

My main Windows 10 system won't boot, so I'm booted to an older Win 10 volume on the same HD.From here, I want to look at the EFI System partition of the unbootable OS. Mountvol /S will mount the EFI partition for the current OS. What if the unbootable OS has a separate EFI partition - how would I mount it? And how can I tell if it has a separate EFI partition?Disk Management snap-in shows only one EFI system partiton - presumably that's for the currently booted OS right? If there were a separate EFI partition for the other OS,how would Disk Management display it? Would it be labeled as

:)

 

Cloned an SSD but it won't boot no more!!

Did all that but with no luck.
On the set id command, that should make the partition 1 as NTFS, after that if I make list volume, the volume 0, that represents partition 1, it still says that is FAT32. Shouldn't be the opposite ?!
Also, why partiton 3 is formated as NTFS?! I've search internet and also on other computers that I have, all of them EFI is a FAT32. I even repeated all the steps, but instead of format partiton 3 as NTFS, I formated as FAT32 but even then it didn't made any difference.
I guess I'm going to install a fresh windows 10 and after the instalation going to try to restore only the main partiton of the current drive to the new instalation to see if it works.

 

How to fix BCD for Dual Boot System

@AndreTen
I will definitely look into that.
@NavyLCDR

Sorry, I've read over your post, and will reread to better understand but wanted to give a clearer idea of what I'm attempting.

I have a functional multiboot device. Booting 3 windows 10 OS's.

I'm cloning the entire drive with AOMEI (willing to use anything, but find all suffer from same issue).
It clones well, and visibly looks perfect, except it boots into Recovery, your pc needs repair.

When I boot using WinPE i can see the volumes and partitions are all there including the EFI.

Something is happening to the EFI. I have on a few occasions reached out to AOMEI as well as Macrium support to see if they have a solution. Neither has been able to help.

I have, once been able to resurrect the EFI partition/boot loader on the cloned drive, but only once.
I think i'm just missing a step in the repair of the EFI/boot loader.

So the only way I can currently have some success is to recreate the boot loader with bcdboot, but this leaves me with only one os.

If this is the best way forward, then maybe your suggestion of "bcdboot E:\Windows /d /addlast" is my only solution, but I was hoping I could just find why the cloned efi partiton isn't working.

 

MBR of RAID volume overwritten, OS fails to boot. Help.

I've screwed up, big time.

My machine has a RAID 0 of two 500GB drives. The resulting volume stores my Windows XP installation. Its contents are vital. I installed an additional 80GB IDE HDD to install Kubuntu. During Kubuntu's setup, those 500GB drives were displayed as is, and not as the resulting volume. I was able to make sure the right drive (hdc, that 80 GB HDD) was partitioned and formatted, but the grand screwup came where in the "finalise" step, you have to specify where the boot-loader has to be installed. This option was hidden in a seperate dialog that comes up on clicking an "advanced" button somewhere. Well...the installer wrote the boot loader to (hda), the first member of the RAID 0 volume, when the installer doesn't recognise the volume itself and only its member disks.

Windows doesn't boot, neither does Kubuntu (shows Grub error 15). I need a way to recover data from the volume. I'm hoping the volume's contents are intact, though its MBR is gone. How do I boot Windows?

I can't use a WinXP boot floppy made from another system, since the boot floppy won't recognise a RAID volume. Should I boot the machine with the Windows XP install CD + AHCI driver floppy and install the OS without formatting the volume, so at least I could safely move my files to another drive even if the resulting OS is unstable? Ideas please.