Windows 10: Why BitLocker Recovery Key needed after booting into Windows without Secure Boot?

I disabled Secure Boot and after booting into Windows it is asking for a BitLocker Recovery Key. Is it a new update to Windows?

:)

 

Windows 10 Home asks for Bitlocker recovery key prompt on every boot after dual boot with ubuntu

Hi,



Thank you for writing to Microsoft Community Forums.



Please note that Windows 10 Home does not have a Bitlocker feature, however it can be embedded by manufacturer of the device. You can read more about it in the article:
BitLocker drive encryption in Windows 10 for OEMs. As you mentioned
that you are using dual boot, I would like to inform you that UEFI Secure Boot may have been toggled with a BIOS update. These generic instructions should allow you to locate the UEFI Secure Boot setting in most BIOS.

• Power the device off and then back on.
• Look for a message on the boot screen just before or after the manufacturer logo appears. You may need to press the “F1”,”F2”, or ”Delete” button, whatever key is indicated on the boot screen to enter BIOS Settings.
• Inside BIOS, look for a tab called BOOT and select that page.
  • Depending on the BIOS manufacturer this page could be BOOT, ADVANCED, STARTUP, etc.
• Look for a setting for UEFI Secure Boot.
  • Each BIOS could have a different name for this. These are the keywords to look for: UEFI, Secure Boot, Legacy Boot
• Please enable Secure boot

You can also follow the instructions provided by Dell in the article:
BitLocker
Asks for a Recovery Key Every Boot on USB-C / Thunderbolt Systems When Docked or Undocked. If you need any further information on this, please get in touch with the manufacturer of the device.



Hope it helps,

 

Windows 8 Secure Boot Feature: Not So Secure?

So Linux is switching to secure boot also? Or they have to because of UEFI?

 

Windows 8 Secure Boot Feature: Not So Secure?

• Linux
• Linux
• Linux
• Linux
• Oh and OSX

Here is a statement from a Kernal Developer at Red Hat:

I'm not sure this exploits the legacy BIOS but rather it exploits the legacy boot method on MBR drives, injecting a signed key before the OS boots, which you are correct in that it has nothing to do with Windows 8. And the simplest fix would just be to require boot drives use GPT when Secure Boot is enabled in UEFI.