Problem with Secure Boot Surface Pro 4

Anonymous
2017-08-10T12:40:17+00:00

Hello.

I got a big problem with Surface Pro 4 Secure Boot. 

I cant enable it and it keeps showing me red bar on top of the screen that makes me angry.

When i try to enable secure boot it shows me"

"Secure Boot error"

"The system failed to update the Secure Boot certificate keyset. The state of Secure Boot on this system has not been modified. Please reboot the system to try again, or open Surface UEFI settings and select a diffrent Secure Boot certificate keyset."

I tried recovery image.

Help!

The post was moved by the moderator to the correct forum category.

Surface | Surface Pro | Safety and security

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Anonymous
    2017-08-13T05:49:14+00:00

    Hi Jonatan,

    Your Surface Pro 4 may be running into conflicts when enabling Secure Boot. Here are several tips you can review to resolve the problem:

    • Uninstall any graphics cards or drivers that aren’t compatible with Secure Boot.
    • Find the Secure Boot setting, and if possible, set it to Enabled. This option is usually in either the Security tab, the Boot tab, or the Authentication tab.
    • If the device does not allow you to enable Secure Boot, try resetting the BIOS back to the factory settings.
    • If the Surface Pro 4 is not able to boot after enabling Secure Boot, go back into the BIOS menu, disable Secure Boot, and try to boot up again.
    • In some cases, you may need to refresh or reset your device to its original state before you can turn on Secure Boot. For more information about restoring or resetting Surface devices, go to this link.

    Let us know if you need more help.

    Regards.

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-08-30T09:12:00+00:00

    I am having the same problem.. I can't re-enable secure boot in any imaginable way.

    @Ruz San: I didn't know there is a BIOS menu that can be accessed with F1, F2, F12 or Esc. Are you talking about SP4? In the UEFI boot menu which you can access with Power+Vol Up buttons, the option to enable secure boot does not work. If it did, then this post would not exist.

    I have done a complete reset (with a recover usb key) and I still can't enable secure boot. The big red stripe at the top is annoying as hell.

    0 comments No comments
  3. Anonymous
    2017-08-30T16:46:01+00:00

    Hi,

    Since the issue remains the same after following the troubleshooting steps provided on this thread, we suggest that you perform additional troubleshooting steps. Please see Secure Boot isn't configured correctly: Determine if the PC is in a manufacturing mode (info for manufacturers).

    Should you need further assistance, feel free to get back to us.

    Regards.

    0 comments No comments
  4. Anonymous
    2017-08-30T19:51:35+00:00

    it doesn't work

    4 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2017-09-03T14:16:25+00:00

    I have no idea why procedures are proposed that give no solution to the problem.

    It is perfectly clear from this thread that we are talking about Secure Boot being disabled in UEFI mode on Surface Pro 4 with Windows 10 and it is not possible to enable it from the UEFI boot menu. Enabling secure boot in the UEFI menu spits out this equally non-sense message

    "The system failed to update the Secure Boot certificate keyset. The state of Secure Boot on this system has not been modified. Please reboot the system to try again, or open Surface UEFI settings and select a diffrent Secure Boot certificate keyset."

    It would be nice if only solutions are suggested instead of other links that want you to find out what the problem is. The problem is quite clear.

    8 people found this answer helpful.
    0 comments No comments