Jump to content

The digital signature for this file couldn't be verified

Hello,

 

My computer gives me the following error when I try to load windows, or boot from any USB key

Image : https://imgur.com/zfLkIwt

Quote

Status: 0xc0000428

Info: The digital signature for this file couldn't be verified.

 

All I find on internet seems to lead to a Windows problem.

But when I try to boot from a USB key, with all other HDD/SSD unplugged, I get the same error.

 

 

What I tried :

  • Unplug all drives (HDD/SSD) and boot on a USB created with the official Windows tool (link) : I get the same error
  • Clear CMOS : same error
  • Disabling TPM (Trusted Computing) - link to image : same error
  • Resetting and disabling "Secure Boot" - link to image : same error
  • Trying UEFI and CSM mode - link to image : same error
  • With different memory : same error
  • With a different graphic card : same error
  • Reseat the CPU : same error
  • Reflash the BIOS : same error
  • Downgrade the BIOS : same error
  • Booting from an official Windows 10 DVD : loads the files from the DVD (DVD reader making noise with only the motherboard logo on screen), then tries loads (logo with windows circle turning - link to image), then the computer reboots before getting to the setup menu where you have to chose the language, link to image.

 

 

I didn't try to boot from a Linux based media.

My motherboard is a MSI B450 GAMING PRO CARBON AC

 

Would someone have an idea ?

Link to comment
Share on other sites

Link to post
Share on other sites

Your motherbord has USB flash capability. Use another computer to make a BIOS flashing usb, then flash the bios, and see if that fixes it. Maybe corrupt bios or something?

I only see your reply if you @ me.

This reply/comment was generated by AI.

Link to comment
Share on other sites

Link to post
Share on other sites

  • 7 months later...

Sorry for the bump. I just noticed that I didn't post the cause of the problem.

The CPU was faulty.

 

Putting the faulty CPU in a new motherboard caused the same problem.

Putting on new CPU on my motherboard resolved the problem.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×