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












7















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





























    7















    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



























      7












      7








      7


      5






      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

      9,09463890




      9,09463890










      asked Jan 13 '18 at 21:00









      PavelPavel

      79821016




      79821016






















          3 Answers
          3






          active

          oldest

          votes


















          10














          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



















          • 3





            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













          • 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



















          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 bios not recognizing my gpt disk anymore - i simply used diskpart from installation dvd/usb



            diskpart>  list disk
            sel disk 0
            attributes disk clear readonly (didn't work for me, but..)
            sel partition 1
            attributes partition clear readonly
            sel partition 2
            attributes partition clear readonly
            sel partition 3
            attributes....


            etc



            worked for me so I could boot into windies 10 after grr 2 weeks WITHOUT reinstalling.
            thx a lot






            share|improve this answer
























              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









              10














              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



















              • 3





                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













              • 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
















              10














              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



















              • 3





                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













              • 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














              10












              10








              10







              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

              22328




              22328








              • 3





                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













              • 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














              • 3





                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













              • 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








              3




              3





              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















              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













              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 bios not recognizing my gpt disk anymore - i simply used diskpart from installation dvd/usb



                      diskpart>  list disk
                      sel disk 0
                      attributes disk clear readonly (didn't work for me, but..)
                      sel partition 1
                      attributes partition clear readonly
                      sel partition 2
                      attributes partition clear readonly
                      sel partition 3
                      attributes....


                      etc



                      worked for me so I could boot into windies 10 after grr 2 weeks WITHOUT reinstalling.
                      thx a lot






                      share|improve this answer






























                        0














                        .. it's been much easier for me : after 2 weeks (!!) of windows 10 not booting with uefi bios not recognizing my gpt disk anymore - i simply used diskpart from installation dvd/usb



                        diskpart>  list disk
                        sel disk 0
                        attributes disk clear readonly (didn't work for me, but..)
                        sel partition 1
                        attributes partition clear readonly
                        sel partition 2
                        attributes partition clear readonly
                        sel partition 3
                        attributes....


                        etc



                        worked for me so I could boot into windies 10 after grr 2 weeks WITHOUT reinstalling.
                        thx a lot






                        share|improve this answer




























                          0












                          0








                          0







                          .. it's been much easier for me : after 2 weeks (!!) of windows 10 not booting with uefi bios not recognizing my gpt disk anymore - i simply used diskpart from installation dvd/usb



                          diskpart>  list disk
                          sel disk 0
                          attributes disk clear readonly (didn't work for me, but..)
                          sel partition 1
                          attributes partition clear readonly
                          sel partition 2
                          attributes partition clear readonly
                          sel partition 3
                          attributes....


                          etc



                          worked for me so I could boot into windies 10 after grr 2 weeks WITHOUT reinstalling.
                          thx a lot






                          share|improve this answer















                          .. it's been much easier for me : after 2 weeks (!!) of windows 10 not booting with uefi bios not recognizing my gpt disk anymore - i simply used diskpart from installation dvd/usb



                          diskpart>  list disk
                          sel disk 0
                          attributes disk clear readonly (didn't work for me, but..)
                          sel partition 1
                          attributes partition clear readonly
                          sel partition 2
                          attributes partition clear readonly
                          sel partition 3
                          attributes....


                          etc



                          worked for me so I could boot into windies 10 after grr 2 weeks WITHOUT reinstalling.
                          thx a lot







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited Oct 28 '18 at 12:35









                          fret

                          1083




                          1083










                          answered Aug 25 '18 at 11:33









                          Marcello BassaniMarcello Bassani

                          1




                          1

















                              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

                              Aardman Animations

                              Are they similar matrix

                              “minimization” problem in Euclidean space related to orthonormal basis