Windows 10: The command prompt cannot run the bootrec command to enter the bcd configuration

Hi,When I set the easybcd boot entries for multi-hard drives in EasyBcd, I can then in the command prompt in the windows 10 installation media type bootrec /rebuildbcd for both a lagecy installed hard drive and a uefi installed hard drive. Because for the hard drive that has the uefi installation, the command interpreter does not find the path and a text line should appear that says the operation completed successfully. But for legacy, the text line the operation completed sucessfully appears. But this depends on whether they are two different kinds of hard drives with two different brands. No

:)

 

bootrec not recognized by command prompt

Like I said bootrec commands has error of saying "'Bootrec' is not recognized as an internal or external command,

operable program or batch file." which is why I posted a question here on the first place.

Both step 6 and 7 work but step 8 keeps telling me that The process cannot access the file because it is being used by another process.

first alternative link you posted shows about exporting bcd which was on step 6 which I already done so that doesnt help because my problem now is step 8 which is renaming before doing the bootrec /rebuildbcd and the
other alternative you posted involves clean install like I said I'm not going to do.

 

bootrec not recognized by command prompt

I just tried all the steps you have given me from this link Redirecting while on safe mode all successfully
finished like the sfc scan and restorehealth with no issues. The only thing I havent tried is the reset and reformat which I said I wouldn't do. Bootrec commands still gives the same error "bootrec is not recognized as an internal or external command, operable
program or batch file" in command prompt. And when I use the command ren f:\boot\bcd bcd.old an error pops out saying "the process cant access the file because it is being used by another process" even though I'm in safe mode. I just did everything you said
still same result

 

command prompt will not open in safe mode with command prompt

Would I just follow the same steps within safe mode after hooking up to the other system?