New
#11
Since you have still the original EFI partition
You would just have to assign the drive letter S to that partition and then format that efi partition
then run bcdboot
Reading your post - you created another EFI partition
Since you have still the original EFI partition
You would just have to assign the drive letter S to that partition and then format that efi partition
then run bcdboot
Reading your post - you created another EFI partition
I know this thread is a little old, but I created an account and just wanted to say Thank You, Kyhi!
Fixed me right up. For anyone wondering, I did this with Windows booted to the desktop, and it worked just fine. In my case, I had the EFI System Partition on the HDD instead of my SSD, which is apparently an issue when you install Windows 10 with both drives connected.
You need to set the new EFI System Partition's ID in diskpart or you won't be able to update windows (even though it will boot)!
set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Why not just copy the EFI from old drive to new drive using minitool partition wizard free - done it zillions of times.
Last edited by cereberus; 26 Aug 2018 at 16:31.
Thank you for this guide!
I tried a bunch of different methods online however none worked for me until i found this.
I installed windows to an SSD while a data HDD was plugged in. The EFI partition for some reason got put on the data hdd.
bcdboot X:\windows /s S:
Note: Replace "X" with the volume letter of the Windows OS partition.
For me C was my ssd while G was my HDD. I used "bcdboot C:\windows /s S:"
Thanks kyhi!
Need to see a screenshot of disk management...
Disk Management - How to Post a Screenshot of | Tutorials
It's fine, I got it working in the end.
I was trying to do it from inside windows, as a previous comment had suggested was possible.
Apparently there was some weird drive remapping happening in windows that was preventing it.
Ran from the creation media and found that the drive letters I saw in windows weren't even actually assigned and the letters for all other volumes were different than they had been reported previously.
It's all working now. Huge thanks to this thread for helping me actual start booting of my nvme
I just want to point out that for me, this was the only thing that worked. My original drive was a samsung SSD - the new one was a Samsung m2. The original samsung SSD contained the only functioning EFI. I Tried all the different permutations outlined in this thread and just ended up with a bunch of pointless 100mb partitions that really cluttered up my potential boot sources. Once I applied the copy tactic to one of the handful of efi partitions that'd been created in my stumbling around diskpart, a functioning one was created.
That wasn't the end, of course...Had to manually go into bios and disable all these boot drives until I found out which one(s) worked since there were so many non-working ones with practically the same name. Lets just say I won't be screwing around with boot stuff for a long while again. Every time I do it's hours down the toilet. Dual booting linux, shudder at the memories....The whole point of this was to try and do the intel optane business but I think I'm just going to stick with what I have for now....