Cannot boot windows 10, “bootrec /fixboot” gives “access denied” Announcing the...

How to call a function with default parameter through a pointer to function that is the return of another function?

How discoverable are IPv6 addresses and AAAA names by potential attackers?

Generate an RGB colour grid

What does "fit" mean in this sentence?

Overriding an object in memory with placement new

Why do we bend a book to keep it straight?

Seeking colloquialism for “just because”

Book where humans were engineered with genes from animal species to survive hostile planets

What does this icon in iOS Stardew Valley mean?

Single word antonym of "flightless"

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?

How to tell that you are a giant?

What is the meaning of the new sigil in Game of Thrones Season 8 intro?

Sci-Fi book where patients in a coma ward all live in a subconscious world linked together

Why is "Consequences inflicted." not a sentence?

Why are there no cargo aircraft with "flying wing" design?

Why didn't this character "real die" when they blew their stack out in Altered Carbon?

How come Sam didn't become Lord of Horn Hill?

How to run gsettings for another user Ubuntu 18.04.2 LTS

What does the "x" in "x86" represent?

Is there a (better) way to access $wpdb results?

Resolving to minmaj7

Can I cast Passwall to drop an enemy into a 20-foot pit?

How does the particle を relate to the verb 行く in the structure「A を + B に行く」?



Cannot boot windows 10, “bootrec /fixboot” gives “access denied”



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)How can I rebuild the Windows boot files?Move users and program files to another PCVista/Server 2008: BOOTMGR is missingBoot error after upgrading to W10, tried to fix it with a W7 disc, think I screwed upWindows 7 fails to boot after copying 500GB HDD to 1 TB SSDBOOTREC /FIXBOOT => Element not foundI can't boot Windows 10 after removing ssd with elementary osCan't Boot into Windows 10, Grub Rescue and Bootrec /FixMBR doesn't workWindows 10 MBR boot - bootrec /rebuildbcd says “requested system device cannot be found”Broken boot manager bootmgr Windows 10 SSD bootrecRecover UEFI boot of Windows 10 after failed Linux installWindows 10 (1803) won't boot - bootrec errors





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







9















My “always on” home desktop today appeared to be totally unresponsive. It was clear that I had only one choice to power reset it. At first it seemed that it booted into my login screen, but again my I did power reset by mistake. From this point on I wasn’t able to boot. It shows “inaccessible boot device” blue screen.



Recovery or restore doesn’t work. From cmd prompt I see my C: drive and all files seem to be ok, entire chkdsk shows that everything is ok with the drive.



bootrec /FixMbr works, however bootrec /fixboot gives me “access is denied.”



bootrec /scanos and bootrec /rebuildbcd both show “Total identified windows installations: 0”



I tried to run it all from the UEFI partition by enabling it from diskpart but I still get “access denied” for fixboot, no matter what I tried. There is one suggestion for the “access denied” error: to format the UEFI partition and then manually create EFIMicrosoftBoot in there and retry bootrec /fixboot but I find it outlandish to even consider it.



Any suggestions? What could be wrong?










share|improve this question































    9















    My “always on” home desktop today appeared to be totally unresponsive. It was clear that I had only one choice to power reset it. At first it seemed that it booted into my login screen, but again my I did power reset by mistake. From this point on I wasn’t able to boot. It shows “inaccessible boot device” blue screen.



    Recovery or restore doesn’t work. From cmd prompt I see my C: drive and all files seem to be ok, entire chkdsk shows that everything is ok with the drive.



    bootrec /FixMbr works, however bootrec /fixboot gives me “access is denied.”



    bootrec /scanos and bootrec /rebuildbcd both show “Total identified windows installations: 0”



    I tried to run it all from the UEFI partition by enabling it from diskpart but I still get “access denied” for fixboot, no matter what I tried. There is one suggestion for the “access denied” error: to format the UEFI partition and then manually create EFIMicrosoftBoot in there and retry bootrec /fixboot but I find it outlandish to even consider it.



    Any suggestions? What could be wrong?










    share|improve this question



























      9












      9








      9


      6






      My “always on” home desktop today appeared to be totally unresponsive. It was clear that I had only one choice to power reset it. At first it seemed that it booted into my login screen, but again my I did power reset by mistake. From this point on I wasn’t able to boot. It shows “inaccessible boot device” blue screen.



      Recovery or restore doesn’t work. From cmd prompt I see my C: drive and all files seem to be ok, entire chkdsk shows that everything is ok with the drive.



      bootrec /FixMbr works, however bootrec /fixboot gives me “access is denied.”



      bootrec /scanos and bootrec /rebuildbcd both show “Total identified windows installations: 0”



      I tried to run it all from the UEFI partition by enabling it from diskpart but I still get “access denied” for fixboot, no matter what I tried. There is one suggestion for the “access denied” error: to format the UEFI partition and then manually create EFIMicrosoftBoot in there and retry bootrec /fixboot but I find it outlandish to even consider it.



      Any suggestions? What could be wrong?










      share|improve this question
















      My “always on” home desktop today appeared to be totally unresponsive. It was clear that I had only one choice to power reset it. At first it seemed that it booted into my login screen, but again my I did power reset by mistake. From this point on I wasn’t able to boot. It shows “inaccessible boot device” blue screen.



      Recovery or restore doesn’t work. From cmd prompt I see my C: drive and all files seem to be ok, entire chkdsk shows that everything is ok with the drive.



      bootrec /FixMbr works, however bootrec /fixboot gives me “access is denied.”



      bootrec /scanos and bootrec /rebuildbcd both show “Total identified windows installations: 0”



      I tried to run it all from the UEFI partition by enabling it from diskpart but I still get “access denied” for fixboot, no matter what I tried. There is one suggestion for the “access denied” error: to format the UEFI partition and then manually create EFIMicrosoftBoot in there and retry bootrec /fixboot but I find it outlandish to even consider it.



      Any suggestions? What could be wrong?







      windows-10 boot






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jul 1 '18 at 9:48









      phuclv

      10.7k64297




      10.7k64297










      asked Jan 13 '18 at 21:00









      PavelPavel

      81321116




      81321116






















          3 Answers
          3






          active

          oldest

          votes


















          14














          I ran into the same issue, the suggestion from Darko_65 in Microsoft Answers forum is what worked for me:



          "bootrec" command sometimes has problems finding proper boot device and windows installation to fix.

          Use "bcdboot" command to fix boot (bcdboot requires that partitions are specified explicitly!)

          bcdboot C:windows /s S:

          specifies C: as Windows partition, S: as system partition.

          Use "diskpart" or "mountvol" commands to map system partition.





          share|improve this answer



















          • 4





            Thank you. You saved m̶y̶ ̶l̶i̶f̶e̶ my cloned win10 installation on a new SSD drive.

            – Toc
            May 18 '18 at 23:35








          • 1





            Saved my bacon too. Had cloned my SSD to a new bigger one then wiped. Just 'bcdboot C:windows' fixed it for me.

            – AceJordin
            Dec 14 '18 at 18:32











          • Bacons are still being saved for those of us who clone to larger SSDs.

            – Fls'Zen
            Mar 6 at 16:00



















          0














          In the answer given by @aoetalks, copying the BCD files to new mount point didnt worked for me. It always ended up saying source files not found. It could be because my /EFI directory got corrupted.



          Anyways, trying to boot with a Windows 8.1 USB media worked.
          All the commands, bootrec /fixmbr, /fixboot, /scanos, and /rebuildbcd worked fine and I'm back to my desktop in a few minutes.



          It looks like the Windows 10 bootrec has some issues.






          share|improve this answer































            0














            It's been much easier for me: after 2 weeks (!!) of Windows 10 not booting with UEFI not recognizing my GPT disk anymore, I simply used diskpart from an installation DVD/USB:



            diskpart
            list disk
            sel disk 0
            sel vol 1
            attributes volume clear readonly
            sel vol 2
            attributes partition clear readonly
            sel vol 3
            attributes...


            ...worked for me so I could boot into Windows 10 after 2 weeks, WITHOUT reinstalling.






            share|improve this answer


























            • I've edited this answer to make the commands valid, as attributes partition... is not valid syntax and attributes volume... is the command that's likely being referred to instead, but I haven't confirmed that the answer works.

              – Hashim
              18 hours ago










            protected by Community Jan 18 at 13:40



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?














            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            14














            I ran into the same issue, the suggestion from Darko_65 in Microsoft Answers forum is what worked for me:



            "bootrec" command sometimes has problems finding proper boot device and windows installation to fix.

            Use "bcdboot" command to fix boot (bcdboot requires that partitions are specified explicitly!)

            bcdboot C:windows /s S:

            specifies C: as Windows partition, S: as system partition.

            Use "diskpart" or "mountvol" commands to map system partition.





            share|improve this answer



















            • 4





              Thank you. You saved m̶y̶ ̶l̶i̶f̶e̶ my cloned win10 installation on a new SSD drive.

              – Toc
              May 18 '18 at 23:35








            • 1





              Saved my bacon too. Had cloned my SSD to a new bigger one then wiped. Just 'bcdboot C:windows' fixed it for me.

              – AceJordin
              Dec 14 '18 at 18:32











            • Bacons are still being saved for those of us who clone to larger SSDs.

              – Fls'Zen
              Mar 6 at 16:00
















            14














            I ran into the same issue, the suggestion from Darko_65 in Microsoft Answers forum is what worked for me:



            "bootrec" command sometimes has problems finding proper boot device and windows installation to fix.

            Use "bcdboot" command to fix boot (bcdboot requires that partitions are specified explicitly!)

            bcdboot C:windows /s S:

            specifies C: as Windows partition, S: as system partition.

            Use "diskpart" or "mountvol" commands to map system partition.





            share|improve this answer



















            • 4





              Thank you. You saved m̶y̶ ̶l̶i̶f̶e̶ my cloned win10 installation on a new SSD drive.

              – Toc
              May 18 '18 at 23:35








            • 1





              Saved my bacon too. Had cloned my SSD to a new bigger one then wiped. Just 'bcdboot C:windows' fixed it for me.

              – AceJordin
              Dec 14 '18 at 18:32











            • Bacons are still being saved for those of us who clone to larger SSDs.

              – Fls'Zen
              Mar 6 at 16:00














            14












            14








            14







            I ran into the same issue, the suggestion from Darko_65 in Microsoft Answers forum is what worked for me:



            "bootrec" command sometimes has problems finding proper boot device and windows installation to fix.

            Use "bcdboot" command to fix boot (bcdboot requires that partitions are specified explicitly!)

            bcdboot C:windows /s S:

            specifies C: as Windows partition, S: as system partition.

            Use "diskpart" or "mountvol" commands to map system partition.





            share|improve this answer













            I ran into the same issue, the suggestion from Darko_65 in Microsoft Answers forum is what worked for me:



            "bootrec" command sometimes has problems finding proper boot device and windows installation to fix.

            Use "bcdboot" command to fix boot (bcdboot requires that partitions are specified explicitly!)

            bcdboot C:windows /s S:

            specifies C: as Windows partition, S: as system partition.

            Use "diskpart" or "mountvol" commands to map system partition.






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 14 '18 at 3:14









            aoetalksaoetalks

            29328




            29328








            • 4





              Thank you. You saved m̶y̶ ̶l̶i̶f̶e̶ my cloned win10 installation on a new SSD drive.

              – Toc
              May 18 '18 at 23:35








            • 1





              Saved my bacon too. Had cloned my SSD to a new bigger one then wiped. Just 'bcdboot C:windows' fixed it for me.

              – AceJordin
              Dec 14 '18 at 18:32











            • Bacons are still being saved for those of us who clone to larger SSDs.

              – Fls'Zen
              Mar 6 at 16:00














            • 4





              Thank you. You saved m̶y̶ ̶l̶i̶f̶e̶ my cloned win10 installation on a new SSD drive.

              – Toc
              May 18 '18 at 23:35








            • 1





              Saved my bacon too. Had cloned my SSD to a new bigger one then wiped. Just 'bcdboot C:windows' fixed it for me.

              – AceJordin
              Dec 14 '18 at 18:32











            • Bacons are still being saved for those of us who clone to larger SSDs.

              – Fls'Zen
              Mar 6 at 16:00








            4




            4





            Thank you. You saved m̶y̶ ̶l̶i̶f̶e̶ my cloned win10 installation on a new SSD drive.

            – Toc
            May 18 '18 at 23:35







            Thank you. You saved m̶y̶ ̶l̶i̶f̶e̶ my cloned win10 installation on a new SSD drive.

            – Toc
            May 18 '18 at 23:35






            1




            1





            Saved my bacon too. Had cloned my SSD to a new bigger one then wiped. Just 'bcdboot C:windows' fixed it for me.

            – AceJordin
            Dec 14 '18 at 18:32





            Saved my bacon too. Had cloned my SSD to a new bigger one then wiped. Just 'bcdboot C:windows' fixed it for me.

            – AceJordin
            Dec 14 '18 at 18:32













            Bacons are still being saved for those of us who clone to larger SSDs.

            – Fls'Zen
            Mar 6 at 16:00





            Bacons are still being saved for those of us who clone to larger SSDs.

            – Fls'Zen
            Mar 6 at 16:00













            0














            In the answer given by @aoetalks, copying the BCD files to new mount point didnt worked for me. It always ended up saying source files not found. It could be because my /EFI directory got corrupted.



            Anyways, trying to boot with a Windows 8.1 USB media worked.
            All the commands, bootrec /fixmbr, /fixboot, /scanos, and /rebuildbcd worked fine and I'm back to my desktop in a few minutes.



            It looks like the Windows 10 bootrec has some issues.






            share|improve this answer




























              0














              In the answer given by @aoetalks, copying the BCD files to new mount point didnt worked for me. It always ended up saying source files not found. It could be because my /EFI directory got corrupted.



              Anyways, trying to boot with a Windows 8.1 USB media worked.
              All the commands, bootrec /fixmbr, /fixboot, /scanos, and /rebuildbcd worked fine and I'm back to my desktop in a few minutes.



              It looks like the Windows 10 bootrec has some issues.






              share|improve this answer


























                0












                0








                0







                In the answer given by @aoetalks, copying the BCD files to new mount point didnt worked for me. It always ended up saying source files not found. It could be because my /EFI directory got corrupted.



                Anyways, trying to boot with a Windows 8.1 USB media worked.
                All the commands, bootrec /fixmbr, /fixboot, /scanos, and /rebuildbcd worked fine and I'm back to my desktop in a few minutes.



                It looks like the Windows 10 bootrec has some issues.






                share|improve this answer













                In the answer given by @aoetalks, copying the BCD files to new mount point didnt worked for me. It always ended up saying source files not found. It could be because my /EFI directory got corrupted.



                Anyways, trying to boot with a Windows 8.1 USB media worked.
                All the commands, bootrec /fixmbr, /fixboot, /scanos, and /rebuildbcd worked fine and I'm back to my desktop in a few minutes.



                It looks like the Windows 10 bootrec has some issues.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Oct 7 '18 at 4:21









                Jimson Kannanthara JamesJimson Kannanthara James

                3131618




                3131618























                    0














                    It's been much easier for me: after 2 weeks (!!) of Windows 10 not booting with UEFI not recognizing my GPT disk anymore, I simply used diskpart from an installation DVD/USB:



                    diskpart
                    list disk
                    sel disk 0
                    sel vol 1
                    attributes volume clear readonly
                    sel vol 2
                    attributes partition clear readonly
                    sel vol 3
                    attributes...


                    ...worked for me so I could boot into Windows 10 after 2 weeks, WITHOUT reinstalling.






                    share|improve this answer


























                    • I've edited this answer to make the commands valid, as attributes partition... is not valid syntax and attributes volume... is the command that's likely being referred to instead, but I haven't confirmed that the answer works.

                      – Hashim
                      18 hours ago
















                    0














                    It's been much easier for me: after 2 weeks (!!) of Windows 10 not booting with UEFI not recognizing my GPT disk anymore, I simply used diskpart from an installation DVD/USB:



                    diskpart
                    list disk
                    sel disk 0
                    sel vol 1
                    attributes volume clear readonly
                    sel vol 2
                    attributes partition clear readonly
                    sel vol 3
                    attributes...


                    ...worked for me so I could boot into Windows 10 after 2 weeks, WITHOUT reinstalling.






                    share|improve this answer


























                    • I've edited this answer to make the commands valid, as attributes partition... is not valid syntax and attributes volume... is the command that's likely being referred to instead, but I haven't confirmed that the answer works.

                      – Hashim
                      18 hours ago














                    0












                    0








                    0







                    It's been much easier for me: after 2 weeks (!!) of Windows 10 not booting with UEFI not recognizing my GPT disk anymore, I simply used diskpart from an installation DVD/USB:



                    diskpart
                    list disk
                    sel disk 0
                    sel vol 1
                    attributes volume clear readonly
                    sel vol 2
                    attributes partition clear readonly
                    sel vol 3
                    attributes...


                    ...worked for me so I could boot into Windows 10 after 2 weeks, WITHOUT reinstalling.






                    share|improve this answer















                    It's been much easier for me: after 2 weeks (!!) of Windows 10 not booting with UEFI not recognizing my GPT disk anymore, I simply used diskpart from an installation DVD/USB:



                    diskpart
                    list disk
                    sel disk 0
                    sel vol 1
                    attributes volume clear readonly
                    sel vol 2
                    attributes partition clear readonly
                    sel vol 3
                    attributes...


                    ...worked for me so I could boot into Windows 10 after 2 weeks, WITHOUT reinstalling.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited 18 hours ago









                    Hashim

                    3,33173264




                    3,33173264










                    answered Aug 25 '18 at 11:33









                    Marcello BassaniMarcello Bassani

                    1




                    1













                    • I've edited this answer to make the commands valid, as attributes partition... is not valid syntax and attributes volume... is the command that's likely being referred to instead, but I haven't confirmed that the answer works.

                      – Hashim
                      18 hours ago



















                    • I've edited this answer to make the commands valid, as attributes partition... is not valid syntax and attributes volume... is the command that's likely being referred to instead, but I haven't confirmed that the answer works.

                      – Hashim
                      18 hours ago

















                    I've edited this answer to make the commands valid, as attributes partition... is not valid syntax and attributes volume... is the command that's likely being referred to instead, but I haven't confirmed that the answer works.

                    – Hashim
                    18 hours ago





                    I've edited this answer to make the commands valid, as attributes partition... is not valid syntax and attributes volume... is the command that's likely being referred to instead, but I haven't confirmed that the answer works.

                    – Hashim
                    18 hours ago





                    protected by Community Jan 18 at 13:40



                    Thank you for your interest in this question.
                    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                    Would you like to answer one of these unanswered questions instead?



                    Popular posts from this blog

                    Cannot install PyQt5 The Next CEO of Stack OverflowCannot install tcpreplay 3.4.4cannot...

                    Kapp-Putsch Acontecimentos | Outros artigos | Menu de navegação

                    Why did early computer designers eschew integers? The Next CEO of Stack OverflowWhat register...