Share via

How do i fix my "secure boot corrupted" PC?

BrickThatBSODs 0 Reputation points
2025-10-30T18:20:43.58+00:00

How it all started; Firstly i was about to test a PE (to be exact Hiren's BootCD PE x64). There was a requirement to turn Secure Boot off, but before, i googled, will secure boot off be supported, Microsoft said yeah and i have had personal VM experience, so i said, eh give it a go and then, BSOD. (was system service except or 0x50 or 0x69 i dont remember). And then i turned Secure Boot back on in my UEFI settings. It booted fine. Next reboot though, was when it started to go down, more bsods, felt like the system was being corrupted, heck even safe mode didn't work. So then i ran sfc /scannow on my drive (/offbootdir=C:\ /offwindir=C:\Windows) and dism /Image:C:\ /Cleanup-Image /RestoreHealth /Source:<my install.swm files>. Then i ran bcdboot /set {current} bootmenupolicy Legacy (to boot into modes when spamming f8) and then i wasted like a day and then i found out about Disable Driver Signature Enforcement in the F8 menu, my pc booted, it was CLEAR that it was signatures errors considering normal boot had a system service exception (with no exception). and yes i have ran powershell commands confirming my signed drivers, (Only drivers not services or exes) which was VERY BAD OF ME TO DO HOLY and then i tried to boot to safe mode. Guess what. Mid-boot there was a 0x7e crash. This Was Bad. Now DSE off wouldn't work, nothing! Currently looking for a fix. (i have a command prompt with a good boot.wim in it like some install usbs or WinRE) (and no im not reinstalling AND WinRE crashes too due to a kfc list corrupt thingy)

Windows for home | Windows 11 | Performance and system failures
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Richard Trinidad 6,285 Reputation points Independent Advisor
    2025-10-30T19:23:58.4833333+00:00

    Hi BrickThatBSODs, thanks for posting here in Microsoft community, since Secure Boot reactivation led to persistent BSODs and recovery tools haven’t helped, it’s likely a bootloader or driver integrity issue. Given you still have access to Command Prompt via boot.wim,

     

    I suggest, Rebuilding the EFI partition using bcdboot C:\Windows /s Z: /f UEFI

    Auditing drivers with dism /image:C:\ /get-drivers to spot unsigned or conflicting ones

    Running bcdedit /enum all to check for misconfigured boot entries

     

    Also, did you install any low-level tools (e.g., encryption, boot managers, or anti-malware) before disabling Secure Boot?

    Let me know

    Chard

    Was this answer helpful?

    1 person found this answer helpful.
  2. Richard Trinidad 6,285 Reputation points Independent Advisor
    2025-10-30T20:58:50.5+00:00

    Hi Brick, you can check for unsigned drivers/services using built-in tools:

    Sigverif, Run sigverif.exe to scan for unsigned drivers. Results are saved in C:\Users\Public\Documents\SIGVERIF.TXT.

    DxDiag. Run dxdiag.exe and check the Drivers tab for signature info.

    PowerShell (Advanced), There are scripts like NinjaOne’s that scan for unsigned drivers great for deeper checks if you're comfortable with scripting.

    Chard

    Was this answer helpful?

    0 comments
  3. Richard Trinidad 6,285 Reputation points Independent Advisor
    2025-10-30T19:00:44.53+00:00

    Hi BrickThatBSODs, thanks for posting here in Microsoft community, since Secure Boot reactivation led to persistent BSODs and recovery tools haven’t helped, it’s likely a bootloader or driver integrity issue. Given you still have access to Command Prompt via boot.wim,

    I suggest, Rebuilding the EFI partition using bcdboot C:\Windows /s Z: /f UEFI

    Auditing drivers with dism /image:C:\ /get-drivers to spot unsigned or conflicting ones

    Running bcdedit /enum all to check for misconfigured boot entries

    Also, did you install any low-level tools (e.g., encryption, boot managers, or anti-malware) before disabling Secure Boot?

    Let me know

    Chard

    Was this answer helpful?

  4. AI answer

    2025-10-30T18:21:12.54+00:00

    To address the "Secure Boot corrupted" issue on your PC, you can follow these troubleshooting steps:

    1. Disable Secure Boot: Since you mentioned issues after enabling Secure Boot, try disabling it again in your UEFI settings. This can sometimes allow the system to boot without encountering the corruption issues.
      • Access the BIOS/UEFI settings by pressing a key (like F1, F2, F12, or Esc) during boot, or by holding the Shift key while selecting Restart from Windows and navigating to Troubleshoot > Advanced Options > UEFI Firmware Settings.
    2. Check for Hardware Compatibility: Ensure that all hardware components, including graphics cards and other peripherals, are compatible with Secure Boot. If you have recently added new hardware, consider removing it to see if that resolves the issue.
    3. Run System Repair Tools: Since you have access to a command prompt, you can run the following commands to attempt to repair your Windows installation:
      • sfc /scannow
      • dism /Image:C:\ /Cleanup-Image /RestoreHealth
      • Make sure to specify the correct paths for your installation files if needed.
    4. Boot into Safe Mode: If you can access the F8 menu, try booting into Safe Mode with Networking. This can help you troubleshoot driver issues that may be causing the BSODs.
    5. Check Driver Signatures: Since you mentioned driver signature errors, you can disable Driver Signature Enforcement temporarily to see if that allows you to boot successfully. This can be done from the F8 menu.
    6. Reset BIOS Settings: If the above steps do not work, consider resetting your BIOS settings to factory defaults. This can sometimes resolve configuration issues that lead to boot problems.
    7. Contact Manufacturer Support: If none of these steps resolve the issue, it may be necessary to contact your PC manufacturer for further assistance, especially if the problem persists after trying to restore or repair the system.

    These steps should help you troubleshoot and potentially fix the issues related to Secure Boot corruption on your PC.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.