Ubuntu 16.04 no longer booting on Lenovo Y70 Touch Error "Verification failed: (0x1A) Security Violation











up vote
0
down vote

favorite












I have Ubuntu installed as the sole operating system on a Lenovo Y70 touch laptop. It was version 16.04. After a recent update, the system would not start. Instead, I am presented with a blue screen saying verification failed: (0x1A) Security Violation. I can't fire up a terminal, boot from a live USB or use an alternate screen.



I went into the BIOS and attempted to disable UEFI. But the change won't stick. It always reverts to a UEFI boot.



I don't have a recovery disk, and Lenovo won't provide a way to revert to Windows. Has anyone come across this problem before?










share|improve this question




























    up vote
    0
    down vote

    favorite












    I have Ubuntu installed as the sole operating system on a Lenovo Y70 touch laptop. It was version 16.04. After a recent update, the system would not start. Instead, I am presented with a blue screen saying verification failed: (0x1A) Security Violation. I can't fire up a terminal, boot from a live USB or use an alternate screen.



    I went into the BIOS and attempted to disable UEFI. But the change won't stick. It always reverts to a UEFI boot.



    I don't have a recovery disk, and Lenovo won't provide a way to revert to Windows. Has anyone come across this problem before?










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have Ubuntu installed as the sole operating system on a Lenovo Y70 touch laptop. It was version 16.04. After a recent update, the system would not start. Instead, I am presented with a blue screen saying verification failed: (0x1A) Security Violation. I can't fire up a terminal, boot from a live USB or use an alternate screen.



      I went into the BIOS and attempted to disable UEFI. But the change won't stick. It always reverts to a UEFI boot.



      I don't have a recovery disk, and Lenovo won't provide a way to revert to Windows. Has anyone come across this problem before?










      share|improve this question















      I have Ubuntu installed as the sole operating system on a Lenovo Y70 touch laptop. It was version 16.04. After a recent update, the system would not start. Instead, I am presented with a blue screen saying verification failed: (0x1A) Security Violation. I can't fire up a terminal, boot from a live USB or use an alternate screen.



      I went into the BIOS and attempted to disable UEFI. But the change won't stick. It always reverts to a UEFI boot.



      I don't have a recovery disk, and Lenovo won't provide a way to revert to Windows. Has anyone come across this problem before?







      boot uefi ubuntu-touch lenovo






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 6 at 18:41









      Gabriel Ziegler

      3051314




      3051314










      asked Dec 6 at 15:36









      Cahir

      1




      1






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          Turn off secure boot in the BIOS/UEFI.
          Also try to save settings or press F10 and choose yes at the save dialog.






          share|improve this answer























          • I have tried to do this, as other threads suggest. It doesn't seem to stick - whether I save or press F10. But thank you for your reply anyway. I Wonder if there is a way to enter a more "advanced" BIOS. I use the NOVO button to get to BIOS, or press Fn and F2
            – Cahir
            Dec 6 at 16:54


















          up vote
          0
          down vote













          Well, if that's the case I suggest that you look for a service that can handle this. It looks like a bugous BIOS or similar.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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%2faskubuntu.com%2fquestions%2f1098957%2fubuntu-16-04-no-longer-booting-on-lenovo-y70-touch-error-verification-failed%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            Turn off secure boot in the BIOS/UEFI.
            Also try to save settings or press F10 and choose yes at the save dialog.






            share|improve this answer























            • I have tried to do this, as other threads suggest. It doesn't seem to stick - whether I save or press F10. But thank you for your reply anyway. I Wonder if there is a way to enter a more "advanced" BIOS. I use the NOVO button to get to BIOS, or press Fn and F2
              – Cahir
              Dec 6 at 16:54















            up vote
            0
            down vote













            Turn off secure boot in the BIOS/UEFI.
            Also try to save settings or press F10 and choose yes at the save dialog.






            share|improve this answer























            • I have tried to do this, as other threads suggest. It doesn't seem to stick - whether I save or press F10. But thank you for your reply anyway. I Wonder if there is a way to enter a more "advanced" BIOS. I use the NOVO button to get to BIOS, or press Fn and F2
              – Cahir
              Dec 6 at 16:54













            up vote
            0
            down vote










            up vote
            0
            down vote









            Turn off secure boot in the BIOS/UEFI.
            Also try to save settings or press F10 and choose yes at the save dialog.






            share|improve this answer














            Turn off secure boot in the BIOS/UEFI.
            Also try to save settings or press F10 and choose yes at the save dialog.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 6 at 16:20

























            answered Dec 6 at 16:05









            linux64kb

            550512




            550512












            • I have tried to do this, as other threads suggest. It doesn't seem to stick - whether I save or press F10. But thank you for your reply anyway. I Wonder if there is a way to enter a more "advanced" BIOS. I use the NOVO button to get to BIOS, or press Fn and F2
              – Cahir
              Dec 6 at 16:54


















            • I have tried to do this, as other threads suggest. It doesn't seem to stick - whether I save or press F10. But thank you for your reply anyway. I Wonder if there is a way to enter a more "advanced" BIOS. I use the NOVO button to get to BIOS, or press Fn and F2
              – Cahir
              Dec 6 at 16:54
















            I have tried to do this, as other threads suggest. It doesn't seem to stick - whether I save or press F10. But thank you for your reply anyway. I Wonder if there is a way to enter a more "advanced" BIOS. I use the NOVO button to get to BIOS, or press Fn and F2
            – Cahir
            Dec 6 at 16:54




            I have tried to do this, as other threads suggest. It doesn't seem to stick - whether I save or press F10. But thank you for your reply anyway. I Wonder if there is a way to enter a more "advanced" BIOS. I use the NOVO button to get to BIOS, or press Fn and F2
            – Cahir
            Dec 6 at 16:54












            up vote
            0
            down vote













            Well, if that's the case I suggest that you look for a service that can handle this. It looks like a bugous BIOS or similar.






            share|improve this answer

























              up vote
              0
              down vote













              Well, if that's the case I suggest that you look for a service that can handle this. It looks like a bugous BIOS or similar.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                Well, if that's the case I suggest that you look for a service that can handle this. It looks like a bugous BIOS or similar.






                share|improve this answer












                Well, if that's the case I suggest that you look for a service that can handle this. It looks like a bugous BIOS or similar.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 7 at 2:10









                linux64kb

                550512




                550512






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2faskubuntu.com%2fquestions%2f1098957%2fubuntu-16-04-no-longer-booting-on-lenovo-y70-touch-error-verification-failed%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

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕