Windows 10: Windows 10 non-secure boot to Windows 11 update has not worked

I have a system which dual boots to Ubuntu Linux 24.04 and current Windows 10 with secure boot disabled.I want to update to Windows 11 as an in-place update, not a clean reinstall but I cannot get this to work.My system has several SSD and NVME which I have Grub2 boot records on that have successfully dual booted.I finally got a Grub2 bootstrap to boot in Secure Boot and can get to Linux with Secure Boot enabled, but that gives me more grief with NVidia drivers not being signed, needing to get a driver, sign it, register the keys in Bios, etc, more trouble than I want. So Linux will remain non

:)

 

Windows 10 Update

Well just noticed a pretty large one pop up coming in at 914MB, seems it makes some pretty serous updates.

KB3172985
Cumulative update for Windows 10 Version 1511 and Windows Server 2016 Technical Preview 4: July 12, 2016 - Microsoft Support

This security update includes improvements and fixes in the functionality of Windows 10 Version 1511 and Windows Server 2016 Technical Preview 4. It also resolves the following vulnerabilities in Windows:

• 3175677 MS16-094: Security update for secure boot: July 12, 2016
• 3174060 MS16-093: Security update for Adobe Flash Player: July 12, 2016
• 3171910 MS16-092: Security update for Windows Kernel: July 12, 2016
• 3170048 MS16-091: Security update for .Net Framework: July 12, 2016
• 3171481 MS16-090: Security update for Kernel Mode Drivers: July 12, 2016
• 3170050 MS16-089: Security update for Windows secure kernel mode: July 12, 2016
• 3170005 MS16-087: Security update for the Microsoft Print Spooler: July 12, 2016
• 3169999 MS16-085: Cumulative security update for Microsoft Edge: July 12, 2016
• 3169991 MS16-084: Cumulative security update for Internet Explorer: July 12, 2016

 

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.

 

Windows 8 Secure Boot Feature: Not So Secure?

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