bootrec not recognized by command prompt

Anonymous
2019-11-16T02:48:02+00:00

Guys please help when I go to windows automatic repair an error pops out saying "Windows automatic repair could not fix your pc" so I tried going to command prompt running with admin of course and using the code bootrec /RebuildBcd and bootrec /FixBoot to fix it but a message pops out saying bootrec is not recognized so I don't know what to do. I tried searching bootrec.exe in drive c, windows, system 32 folder but I couldn't find it. How do i fix this and do I need a windows installation cd to activate bootrec and automatic repair or something? Please don't suggest using system restore points and system reset because I will not try those solutions for I already tried system restore and automatic repair still did not work and system reset for me will remove all my programs so I will not do it. I'm using windows 10 and with latest updates also tried sfc scan now with no issues and tried dism restorepoint already which completed successfully.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

54 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-11-17T00:31:01+00:00

    Hi bro, i tried also to update my W10 today but the same error appear to me.

    Searching in YouTube, i found a comment with another command for this error, the command is this:

    bootrec /nt60 sys

    And after this, type the bootrec /fixboot command. With this, i tried to update but after spending 6 hours, nothing, the blue screen appear to me every minute. My only way to get again the PC start, reinstalling the system without deleting my documents and games, for my luck, but this delete your configurations and some apps installed on the system disc partition, like Microsoft Office apps and all Redistributables and DirectX tools. Now i am reinstalling every app and playing my games again, i hope my reply can help you, greetings from Paraguay and sorry for my bad english :P

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-11-16T23:40:10+00:00

    I just copied what you posted same error 'Bootrec.exe' is not recognized as an internal or external command,

    operable program or batch file.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-11-16T23:06:53+00:00

    That's an error with the syntax for bootrec commands. Are you copying and pasting it or making sure there's a space:
    Bootrec.exe /fixboot
    Bootrec.exe /fixmbr

    More here:
    https://support.microsoft.com/en-us/help/927392...

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-11-16T22:30:03+00:00

    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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-11-16T18:16:44+00:00

    See explanation of the error, however I will tell you that this is much more technical that any consumer forums usually gets into. This is why I gave you two other much better alternatives to rescue your install :

    https://social.technet.microsoft.com/Forums/en-...

    https://answers.microsoft.com/en-us/windows/for...?

    I also asked if you ran the bootrec commands from Troubleshooting steps:

    http://answers.microsoft.com/en-us/windows/wiki...

    Was this answer helpful?

    0 comments