Altered `bcdedit` and now Windows 10 won't boot





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I have dual boot on my Surface Pro 3, Windows 10 primary (was installed first) and Ubuntu Budgie (secondary). During the installation, GRUB2 was installed as well. Following the guide here, I entered



bcdedit /set "{bootmgr}" path EFIubuntugrubx64.efi


When I power up the Surface, I see the GRUB menu, from which I can choose Ubuntu and it boots fine. But, before the command above, I used to be able to press Esc and type exit to exit GRUB and boot Windows 10. Since after that command, I can no longer access Windows 10. Now, when I exit GRUB, it just restarts the computer back to the GRUB menu, and if I do it again it turns off the computer!



PLEASE do not direct me to here or here, as I have already read those posts and tried their solutions. Additionally, I have tried the following commands with no help:



bcdedit /default {ntldr}
bcdedit /set "{bootmgr}" path EFIubuntushimx64.efi


Please tell me there is a way to get Windows back other than re-install



Here is an image of bcdedit command from Command Prompt










share|improve this question































    1















    I have dual boot on my Surface Pro 3, Windows 10 primary (was installed first) and Ubuntu Budgie (secondary). During the installation, GRUB2 was installed as well. Following the guide here, I entered



    bcdedit /set "{bootmgr}" path EFIubuntugrubx64.efi


    When I power up the Surface, I see the GRUB menu, from which I can choose Ubuntu and it boots fine. But, before the command above, I used to be able to press Esc and type exit to exit GRUB and boot Windows 10. Since after that command, I can no longer access Windows 10. Now, when I exit GRUB, it just restarts the computer back to the GRUB menu, and if I do it again it turns off the computer!



    PLEASE do not direct me to here or here, as I have already read those posts and tried their solutions. Additionally, I have tried the following commands with no help:



    bcdedit /default {ntldr}
    bcdedit /set "{bootmgr}" path EFIubuntushimx64.efi


    Please tell me there is a way to get Windows back other than re-install



    Here is an image of bcdedit command from Command Prompt










    share|improve this question



























      1












      1








      1








      I have dual boot on my Surface Pro 3, Windows 10 primary (was installed first) and Ubuntu Budgie (secondary). During the installation, GRUB2 was installed as well. Following the guide here, I entered



      bcdedit /set "{bootmgr}" path EFIubuntugrubx64.efi


      When I power up the Surface, I see the GRUB menu, from which I can choose Ubuntu and it boots fine. But, before the command above, I used to be able to press Esc and type exit to exit GRUB and boot Windows 10. Since after that command, I can no longer access Windows 10. Now, when I exit GRUB, it just restarts the computer back to the GRUB menu, and if I do it again it turns off the computer!



      PLEASE do not direct me to here or here, as I have already read those posts and tried their solutions. Additionally, I have tried the following commands with no help:



      bcdedit /default {ntldr}
      bcdedit /set "{bootmgr}" path EFIubuntushimx64.efi


      Please tell me there is a way to get Windows back other than re-install



      Here is an image of bcdedit command from Command Prompt










      share|improve this question
















      I have dual boot on my Surface Pro 3, Windows 10 primary (was installed first) and Ubuntu Budgie (secondary). During the installation, GRUB2 was installed as well. Following the guide here, I entered



      bcdedit /set "{bootmgr}" path EFIubuntugrubx64.efi


      When I power up the Surface, I see the GRUB menu, from which I can choose Ubuntu and it boots fine. But, before the command above, I used to be able to press Esc and type exit to exit GRUB and boot Windows 10. Since after that command, I can no longer access Windows 10. Now, when I exit GRUB, it just restarts the computer back to the GRUB menu, and if I do it again it turns off the computer!



      PLEASE do not direct me to here or here, as I have already read those posts and tried their solutions. Additionally, I have tried the following commands with no help:



      bcdedit /default {ntldr}
      bcdedit /set "{bootmgr}" path EFIubuntushimx64.efi


      Please tell me there is a way to get Windows back other than re-install



      Here is an image of bcdedit command from Command Prompt







      windows-10 ubuntu boot grub






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 28 at 22:24







      Ptheguy

















      asked Jan 28 at 22:14









      PtheguyPtheguy

      188




      188






















          1 Answer
          1






          active

          oldest

          votes


















          1














          So it turns out editing boot configurations wasn't the issue--the issues was the BitLocker preventing me from booting to Windows. I used the Command Prompt to manually disabled BitLocker so it wouldn't yell at me when I boot Windows through GRUB. Commands used



          manage-bde -status   #returns list of volumes and whether they are encrypted or not
          manage-bde -unlock (volume name, example C:) -rp (48 digit recovery code)
          manage-bde -protectors -disable (volume name, example C:)





          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399435%2faltered-bcdedit-and-now-windows-10-wont-boot%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            So it turns out editing boot configurations wasn't the issue--the issues was the BitLocker preventing me from booting to Windows. I used the Command Prompt to manually disabled BitLocker so it wouldn't yell at me when I boot Windows through GRUB. Commands used



            manage-bde -status   #returns list of volumes and whether they are encrypted or not
            manage-bde -unlock (volume name, example C:) -rp (48 digit recovery code)
            manage-bde -protectors -disable (volume name, example C:)





            share|improve this answer




























              1














              So it turns out editing boot configurations wasn't the issue--the issues was the BitLocker preventing me from booting to Windows. I used the Command Prompt to manually disabled BitLocker so it wouldn't yell at me when I boot Windows through GRUB. Commands used



              manage-bde -status   #returns list of volumes and whether they are encrypted or not
              manage-bde -unlock (volume name, example C:) -rp (48 digit recovery code)
              manage-bde -protectors -disable (volume name, example C:)





              share|improve this answer


























                1












                1








                1







                So it turns out editing boot configurations wasn't the issue--the issues was the BitLocker preventing me from booting to Windows. I used the Command Prompt to manually disabled BitLocker so it wouldn't yell at me when I boot Windows through GRUB. Commands used



                manage-bde -status   #returns list of volumes and whether they are encrypted or not
                manage-bde -unlock (volume name, example C:) -rp (48 digit recovery code)
                manage-bde -protectors -disable (volume name, example C:)





                share|improve this answer













                So it turns out editing boot configurations wasn't the issue--the issues was the BitLocker preventing me from booting to Windows. I used the Command Prompt to manually disabled BitLocker so it wouldn't yell at me when I boot Windows through GRUB. Commands used



                manage-bde -status   #returns list of volumes and whether they are encrypted or not
                manage-bde -unlock (volume name, example C:) -rp (48 digit recovery code)
                manage-bde -protectors -disable (volume name, example C:)






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 29 at 0:29









                PtheguyPtheguy

                188




                188






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399435%2faltered-bcdedit-and-now-windows-10-wont-boot%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                    Alcedinidae

                    Origin of the phrase “under your belt”?