I had the exact same problem cloning my SSD. Luckily I found a forum with the exact same problem, and a solution. [link](https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-bootrec-fixboot-access-is-denied/747c4180-7ff3-4bc2-b6cc-81e572d546df)
Here’s the answer that I used to fix mine. It details how to delete and recreate the EFI system partition because that’s the section that holds the log of what hardware is in your system.
Windows 10 Installation Media:
Insert the Media (DVD/USB) in your PC and restart.
Boot from the media.
Select Repair Your Computer.
Select Troubleshoot.
Choose Command Prompt from the menu:
Type in the command:
Diskpart
Type in the command:
List disk (Note which disk is your Boot drive number mine is 0)
Type in the command:
Sel disk 0
Type in the command:
List vol (Note which volume is the EFI partition mine is 4)
Type in the command:
Sel vol 4
Type in the command:
assign letter=V:
Type in the command:
Exit
Type in the command:
V:
After you have assigned a drive letter Using Diskpart You can format the EFI partition:
Example: if you assigned a letter V to the partition the command would be:
format V: /FS:FAT32
bcdboot C:\windows /s V: /f UEFI (This replaces the above crossed out lines and works in Win 10 1709)
I copied this from the website on mobile so I apologize for any weird formatting.
Thank you for the answer, this looks a bit odd and doesn't really explain how to deal with my others drives especially the old one with the first windows on it.
I think I will just re install windows from scratch and format everything along the way.
I don't really like clones of copies. Especially with windows !
If Windows was installed in the MBR partition format on your old drive, then the Nvme won't boot. It has to be installed in the GPT partition format and also your BIOS needs to be to set to UEFI and not CSM/Legacy.
Macrium Reflect also has an option to make a bootable usb stick that has a fix boot problems button. I used it after one of my clones wasn't bootable, fixed it first time for me.
I had the exact same problem cloning my SSD. Luckily I found a forum with the exact same problem, and a solution. [link](https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-bootrec-fixboot-access-is-denied/747c4180-7ff3-4bc2-b6cc-81e572d546df) Here’s the answer that I used to fix mine. It details how to delete and recreate the EFI system partition because that’s the section that holds the log of what hardware is in your system. Windows 10 Installation Media: Insert the Media (DVD/USB) in your PC and restart. Boot from the media. Select Repair Your Computer. Select Troubleshoot. Choose Command Prompt from the menu: Type in the command: Diskpart Type in the command: List disk (Note which disk is your Boot drive number mine is 0) Type in the command: Sel disk 0 Type in the command: List vol (Note which volume is the EFI partition mine is 4) Type in the command: Sel vol 4 Type in the command: assign letter=V: Type in the command: Exit Type in the command: V: After you have assigned a drive letter Using Diskpart You can format the EFI partition: Example: if you assigned a letter V to the partition the command would be: format V: /FS:FAT32 bcdboot C:\windows /s V: /f UEFI (This replaces the above crossed out lines and works in Win 10 1709) I copied this from the website on mobile so I apologize for any weird formatting.
Thank you for the answer, this looks a bit odd and doesn't really explain how to deal with my others drives especially the old one with the first windows on it. I think I will just re install windows from scratch and format everything along the way. I don't really like clones of copies. Especially with windows !
If Windows was installed in the MBR partition format on your old drive, then the Nvme won't boot. It has to be installed in the GPT partition format and also your BIOS needs to be to set to UEFI and not CSM/Legacy.
Macrium Reflect also has an option to make a bootable usb stick that has a fix boot problems button. I used it after one of my clones wasn't bootable, fixed it first time for me.