Cant boot to EFI shell Asus Motherboard












0















I have an Asus Maximus VIII Impact MotherBoard



I just purchased an Intel RS3UC080 RAID card, and notice the firmware was very out of date. I figured I would update it before using the card. To do this you have to boot to an EFI shell. The README intel gives you in the download says to copy the files to a USB drive, then boot to the EFI shell on the drive. When I did that I got the following error



The Secure Boot is enabled to prevent untusted operating systems from
loading during the system start-up. To launch the EFI shell, please disable
the secure boot option.


So I disabled secure boot by removing the platform key (the internet told me to), I can get it back.



after a reboot it shows that secure boot is disabled.



However I get the same error when I try to boot to the EFI Shell.










share|improve this question



























    0















    I have an Asus Maximus VIII Impact MotherBoard



    I just purchased an Intel RS3UC080 RAID card, and notice the firmware was very out of date. I figured I would update it before using the card. To do this you have to boot to an EFI shell. The README intel gives you in the download says to copy the files to a USB drive, then boot to the EFI shell on the drive. When I did that I got the following error



    The Secure Boot is enabled to prevent untusted operating systems from
    loading during the system start-up. To launch the EFI shell, please disable
    the secure boot option.


    So I disabled secure boot by removing the platform key (the internet told me to), I can get it back.



    after a reboot it shows that secure boot is disabled.



    However I get the same error when I try to boot to the EFI Shell.










    share|improve this question

























      0












      0








      0








      I have an Asus Maximus VIII Impact MotherBoard



      I just purchased an Intel RS3UC080 RAID card, and notice the firmware was very out of date. I figured I would update it before using the card. To do this you have to boot to an EFI shell. The README intel gives you in the download says to copy the files to a USB drive, then boot to the EFI shell on the drive. When I did that I got the following error



      The Secure Boot is enabled to prevent untusted operating systems from
      loading during the system start-up. To launch the EFI shell, please disable
      the secure boot option.


      So I disabled secure boot by removing the platform key (the internet told me to), I can get it back.



      after a reboot it shows that secure boot is disabled.



      However I get the same error when I try to boot to the EFI Shell.










      share|improve this question














      I have an Asus Maximus VIII Impact MotherBoard



      I just purchased an Intel RS3UC080 RAID card, and notice the firmware was very out of date. I figured I would update it before using the card. To do this you have to boot to an EFI shell. The README intel gives you in the download says to copy the files to a USB drive, then boot to the EFI shell on the drive. When I did that I got the following error



      The Secure Boot is enabled to prevent untusted operating systems from
      loading during the system start-up. To launch the EFI shell, please disable
      the secure boot option.


      So I disabled secure boot by removing the platform key (the internet told me to), I can get it back.



      after a reboot it shows that secure boot is disabled.



      However I get the same error when I try to boot to the EFI Shell.







      motherboard shell secure-boot






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 21 '17 at 0:15









      Josh YoungJosh Young

      1113




      1113






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Removing the platform key (PK) actually entered what's known as setup mode, in which Secure Boot variables may be altered at will. That's not quite identical to simply turning off Secure Boot. I would expect that either approach would work for doing what you wanted, but different UEFIs are subtly different, so maybe yours is weird in this way.



          I recommend you re-enter your firmware and look for two options:





          • Re-load standard keys -- This option should load the standard key set, including the PK and all other Secure Boot keys. This should effectively undo what you've just done. Note that there's no standardization of user interfaces for how to perform tasks like this, so you may need to go poking around to find the correct option.


          • Disable Secure Boot -- This is a less destructive option than the one you used. See this page of mine for several examples of how to disable Secure Boot, including one on an ASUS board. (That said, my ASUS board is rather old as Secure Boot goes, and its user interface is not guaranteed to resemble yours'.)


          With any luck, this will get you going.






          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%2f1211251%2fcant-boot-to-efi-shell-asus-motherboard%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









            0














            Removing the platform key (PK) actually entered what's known as setup mode, in which Secure Boot variables may be altered at will. That's not quite identical to simply turning off Secure Boot. I would expect that either approach would work for doing what you wanted, but different UEFIs are subtly different, so maybe yours is weird in this way.



            I recommend you re-enter your firmware and look for two options:





            • Re-load standard keys -- This option should load the standard key set, including the PK and all other Secure Boot keys. This should effectively undo what you've just done. Note that there's no standardization of user interfaces for how to perform tasks like this, so you may need to go poking around to find the correct option.


            • Disable Secure Boot -- This is a less destructive option than the one you used. See this page of mine for several examples of how to disable Secure Boot, including one on an ASUS board. (That said, my ASUS board is rather old as Secure Boot goes, and its user interface is not guaranteed to resemble yours'.)


            With any luck, this will get you going.






            share|improve this answer




























              0














              Removing the platform key (PK) actually entered what's known as setup mode, in which Secure Boot variables may be altered at will. That's not quite identical to simply turning off Secure Boot. I would expect that either approach would work for doing what you wanted, but different UEFIs are subtly different, so maybe yours is weird in this way.



              I recommend you re-enter your firmware and look for two options:





              • Re-load standard keys -- This option should load the standard key set, including the PK and all other Secure Boot keys. This should effectively undo what you've just done. Note that there's no standardization of user interfaces for how to perform tasks like this, so you may need to go poking around to find the correct option.


              • Disable Secure Boot -- This is a less destructive option than the one you used. See this page of mine for several examples of how to disable Secure Boot, including one on an ASUS board. (That said, my ASUS board is rather old as Secure Boot goes, and its user interface is not guaranteed to resemble yours'.)


              With any luck, this will get you going.






              share|improve this answer


























                0












                0








                0







                Removing the platform key (PK) actually entered what's known as setup mode, in which Secure Boot variables may be altered at will. That's not quite identical to simply turning off Secure Boot. I would expect that either approach would work for doing what you wanted, but different UEFIs are subtly different, so maybe yours is weird in this way.



                I recommend you re-enter your firmware and look for two options:





                • Re-load standard keys -- This option should load the standard key set, including the PK and all other Secure Boot keys. This should effectively undo what you've just done. Note that there's no standardization of user interfaces for how to perform tasks like this, so you may need to go poking around to find the correct option.


                • Disable Secure Boot -- This is a less destructive option than the one you used. See this page of mine for several examples of how to disable Secure Boot, including one on an ASUS board. (That said, my ASUS board is rather old as Secure Boot goes, and its user interface is not guaranteed to resemble yours'.)


                With any luck, this will get you going.






                share|improve this answer













                Removing the platform key (PK) actually entered what's known as setup mode, in which Secure Boot variables may be altered at will. That's not quite identical to simply turning off Secure Boot. I would expect that either approach would work for doing what you wanted, but different UEFIs are subtly different, so maybe yours is weird in this way.



                I recommend you re-enter your firmware and look for two options:





                • Re-load standard keys -- This option should load the standard key set, including the PK and all other Secure Boot keys. This should effectively undo what you've just done. Note that there's no standardization of user interfaces for how to perform tasks like this, so you may need to go poking around to find the correct option.


                • Disable Secure Boot -- This is a less destructive option than the one you used. See this page of mine for several examples of how to disable Secure Boot, including one on an ASUS board. (That said, my ASUS board is rather old as Secure Boot goes, and its user interface is not guaranteed to resemble yours'.)


                With any luck, this will get you going.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 22 '17 at 2:51









                Rod SmithRod Smith

                17.1k22042




                17.1k22042






























                    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%2f1211251%2fcant-boot-to-efi-shell-asus-motherboard%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

                    How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                    is 'sed' thread safe

                    How to make a Squid Proxy server?