Secure Boot violation message.


zooburner

I really don't burn zoos !
Member
Local time
10:51 AM
Posts
85
OS
Windows 11 (Pro)
Hi there,

For many years i have used a program called 'Parted Magic' it's a boot USB with some great tools one that allows you safe erase a SSD drive (without writing all zero's etc) it's worked fine for years, till today i got this after i had selected it from the boot options (see image)

boot-error.gif

I've not made any changes to my BIOS settings and to be on the safe side re-imaged on a different USB parted magic boot USB, with the same results.
My Macrium boot USB boots fine without this, and if I press the OK it just boots into the Parted magic USB anyway.

I should also point out that it boots into windows fine just like it always has.
 

My Computer

System One

  • OS
    Windows 11 (Pro)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Scan Vengeance
    CPU
    i7 8700K
    Motherboard
    ROG Strix Z370F Gaming
    Memory
    16GB Corsair Vengeance
    Graphics Card(s)
    Nvidia 1070Ti
    Sound Card
    Onboard / Realtek
    Monitor(s) Displays
    BENQ GL2450
    Screen Resolution
    1920x1080
    Hard Drives
    1x Samsung 960 ProM=M.2 NVE 250GB
    1x Samsung SSD 860Pro SSD 250GB
    1x WD 2GB Spinner
    PSU
    Corsair 550w
    Case
    Fractual Mesh
    Cooling
    Corsair water cooling H100i v2
    Keyboard
    Microsoft keyboard and mouse combo
    Mouse
    Microsoft
    Browser
    Edge
    Antivirus
    Bitdefender
Open the Command Prompt with administrative privileges and execute the following commands one at a time.


Code:
Dism /online /cleanup-image /restorehealth



Sfc /scannow
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Pavilion
    CPU
    AMD Ryzen 7 5700G
    Motherboard
    Erica6
    Memory
    Micron Technology DDR4-3200 16GB
    Graphics Card(s)
    NVIDIA GeForce RTX 3060
    Sound Card
    Realtek ALC671
    Monitor(s) Displays
    Samsung SyncMaster U28E590
    Screen Resolution
    3840 x 2160
    Hard Drives
    SAMSUNG MZVLQ1T0HALB-000H1
Open the Command Prompt with administrative privileges and execute the following commands one at a time.


Code:
Dism /online /cleanup-image /restorehealth



Sfc /scannow

Hi there and thanks for the reply

Ran restorehealth which completed succesfully

scannow found no problems.

Though is this relevant as this is happening prior to windows boot up ?
 

My Computer

System One

  • OS
    Windows 11 (Pro)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Scan Vengeance
    CPU
    i7 8700K
    Motherboard
    ROG Strix Z370F Gaming
    Memory
    16GB Corsair Vengeance
    Graphics Card(s)
    Nvidia 1070Ti
    Sound Card
    Onboard / Realtek
    Monitor(s) Displays
    BENQ GL2450
    Screen Resolution
    1920x1080
    Hard Drives
    1x Samsung 960 ProM=M.2 NVE 250GB
    1x Samsung SSD 860Pro SSD 250GB
    1x WD 2GB Spinner
    PSU
    Corsair 550w
    Case
    Fractual Mesh
    Cooling
    Corsair water cooling H100i v2
    Keyboard
    Microsoft keyboard and mouse combo
    Mouse
    Microsoft
    Browser
    Edge
    Antivirus
    Bitdefender
The boot files if they get modified or corrupted can cause error message.

First developed by Intel, Secure Boot performs two tasks when a PC is switched on and before the OS loads. First, it verifies that the motherboard firmware is digitally signed, which helps reduce the risk of rootkits, which will modify the firmware and, thus, corrupt the signature.

Secure Boot then queries the digital signature of the OS in the bootloader to see if it matches a cryptographic signature that’s stored within the UEFI firmware. If both signatures match, the OS is permitted to load. If they don’t, Secure Boot concludes that the bootloader has been tampered with and will prevent the OS from starting.

Upgrade UEFI firmware from website of the manufacturer of your computer or motherboard.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Pavilion
    CPU
    AMD Ryzen 7 5700G
    Motherboard
    Erica6
    Memory
    Micron Technology DDR4-3200 16GB
    Graphics Card(s)
    NVIDIA GeForce RTX 3060
    Sound Card
    Realtek ALC671
    Monitor(s) Displays
    Samsung SyncMaster U28E590
    Screen Resolution
    3840 x 2160
    Hard Drives
    SAMSUNG MZVLQ1T0HALB-000H1
The boot files if they get modified or corrupted can cause error message.

First developed by Intel, Secure Boot performs two tasks when a PC is switched on and before the OS loads. First, it verifies that the motherboard firmware is digitally signed, which helps reduce the risk of rootkits, which will modify the firmware and, thus, corrupt the signature.

Secure Boot then queries the digital signature of the OS in the bootloader to see if it matches a cryptographic signature that’s stored within the UEFI firmware. If both signatures match, the OS is permitted to load. If they don’t, Secure Boot concludes that the bootloader has been tampered with and will prevent the OS from starting.

Upgrade UEFI firmware from website of the manufacturer of your computer or motherboard.

Thanks for that it's interesting, windows boots just fine without an error showing up, and has always done so.

I'm more troubleshooting why when I use the boot menu to boot from this USB (that never used to show it) now does.
 

My Computer

System One

  • OS
    Windows 11 (Pro)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Scan Vengeance
    CPU
    i7 8700K
    Motherboard
    ROG Strix Z370F Gaming
    Memory
    16GB Corsair Vengeance
    Graphics Card(s)
    Nvidia 1070Ti
    Sound Card
    Onboard / Realtek
    Monitor(s) Displays
    BENQ GL2450
    Screen Resolution
    1920x1080
    Hard Drives
    1x Samsung 960 ProM=M.2 NVE 250GB
    1x Samsung SSD 860Pro SSD 250GB
    1x WD 2GB Spinner
    PSU
    Corsair 550w
    Case
    Fractual Mesh
    Cooling
    Corsair water cooling H100i v2
    Keyboard
    Microsoft keyboard and mouse combo
    Mouse
    Microsoft
    Browser
    Edge
    Antivirus
    Bitdefender
...why when I use the boot menu to boot from this USB (that never used to show it) now does.
As FreeBooter explained....
Secure Boot then queries the digital signature of the OS in the bootloader to see if it matches a cryptographic signature that’s stored within the UEFI firmware.

For many years i have used a program called 'Parted Magic'....
If it's that old, then it is entirely possible that the key used for 'Parted Magic' has just passed its expiry date.

openssl does not permit creating a certificate without an expiration date....
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Lattitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
As FreeBooter explained....



If it's that old, then it is entirely possible that the key used for 'Parted Magic' has just passed its expiry date.



That's fine but this is at the boot manager stage, as i say windows boots and other USB's boot fine.
I got a new version of the software and it still did it, Turns out just a reflash of the (same) bios sorted it out :)
 

My Computer

System One

  • OS
    Windows 11 (Pro)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Scan Vengeance
    CPU
    i7 8700K
    Motherboard
    ROG Strix Z370F Gaming
    Memory
    16GB Corsair Vengeance
    Graphics Card(s)
    Nvidia 1070Ti
    Sound Card
    Onboard / Realtek
    Monitor(s) Displays
    BENQ GL2450
    Screen Resolution
    1920x1080
    Hard Drives
    1x Samsung 960 ProM=M.2 NVE 250GB
    1x Samsung SSD 860Pro SSD 250GB
    1x WD 2GB Spinner
    PSU
    Corsair 550w
    Case
    Fractual Mesh
    Cooling
    Corsair water cooling H100i v2
    Keyboard
    Microsoft keyboard and mouse combo
    Mouse
    Microsoft
    Browser
    Edge
    Antivirus
    Bitdefender
Turns out just a reflash of the (same) bios sorted it out :)
Then that would suggest that the particular key/certificate held in the bios that it was being compared with had somehow been lost/corrupted. Not sure how that may have happened, not really my area of expertise.....
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Lattitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
I had the same problem with all my computers running Windows 10.
I've tried all these solutions posted here, plus many others to no avail.
I believe the issue with Parted Magic was due to a recent Windows update, that corrupted the BIOS.
The solution to my fix was to go into the BIOS, and load the optimized defaults... that fixed the issue (obviously, if you have to apply some defaults overrides, you need to re-apply those).
Hope this solution will work for you.
 

My Computer

System One

  • OS
    WIndows 10

Latest Support Threads

Back
Top Bottom