ES1-732 Laptop

TerrySmythe
TerrySmythe Member Posts: 5 New User
edited August 2023 in 2018 Archives
I have an ES1-732 laptop.   Trying to do a clean Install of Win10 Home on a new SSD drive, installed.    "Security Boot Fail" blocks boot to DVD drive or external DVD drive.     In Bios Setup, disable Security Boot Mode is greyed out.     Neither arrow keys nor mouse will let be disable this attribute.   I'm dead in the water.    Thoughts of others? 

Answers

  • Balatekie
    Balatekie ACE Posts: 1,353 Pioneer
    Hi, In order to change the secure boot setting, you need to set a supervisor password. Please follow the below instructions for disabling secure boot. 
    1. Completely shut down your computer.
    2. Power on the system. As soon as the first logo screen appears, immediately press F2 to enter the BIOS.
    3. Use the right arrow key to select Security.
    4. Use the down arrow key to highlight Set Supervisor Password and press Enter.
    5. Create a password and press Enter. Retype the password to confirm and press Enter again.
    6. Use the right arrow key to select Boot.
    7. Press the down arrow key to select Secure Boot and press Enter.
    8. With the arrow key, highlight Disabled and press Enter.
    9. Press the F10 key and select Yes to save the changes and exit the BIOS.
    NOTE:: We suggest removing the supervisor password immediately after enabling Secure Boot. If you choose not to remove your supervisor password, make sure you write it down for future use.
     :) If you think I've answered your question, please hit the Accept Answer:)

  • TerrySmythe
    TerrySmythe Member Posts: 5 New User
    A previous entry gave me the steps 1 to 5, which posed the problem I faced.    Your answer with the steps 6 to 8 worked out just fine.      I'm not a newbie, been working with personal computers since the early 80's.        My ES1-732 laptop came with Win 10 installed in a conventional hard drive.      As I'm having problems with my current Win 10 install, I wanted to do a clean install into a new SSD, rather than clone, which would have replicated the current problems.   Thank you.