Invalid Signature Detected

Hello everyone
I have an ASUS Notebook, but I’m not sure if which version of Windows I have (7-10?). This morning my laptop automatically updated and after that a message saying “Invalid Signature Detected. Check boot policy in setup.” appeared. We looked it up online and tried to disable Secure Boot Control. It didn’t help & now all I see is Asus, In Search Of The Incredible. What can I do to fix this? There is an important file on my laptop I need as soon as possible.
Thank you for your help

I have the Flipbook TP501U and I don’t know which version of Windows I have. I don’t know how I can see that since my computer crashed...

I haven’t connected a laptop to mine. Do I have to?

I followed the instructions on this video: secure boot violation invalid signature detected check secure boot policy in setup - YouTube but like a couple of people said it sits on the loading screen forever afterwards.

My file is on the Flipbook.

Please Ignore my previous question about laptop - I was misunderstanding.

Just to be clear (following the video). You disabled secure boot on the ASUS, yes?

This should resolve the signature issue. You should definitely leave this disabled.

Did you change fast boot or csm settings (around 47s in the video)? I can imagine enabling csm could cause an issue. You could try to leave csm and fastboot disabled then hard shutdown (hold power until it turns off). Then restart. Some comments on the video say this works.

If it doesn't work you can take a picture of the BIOS settings (perhaps with your phone or a camera or something) and upload them.

I did.
And I’ve tried everything: CSM disabled, CSM enabled, Fast Boot disabled... nothing works

Do I have to take a picture of the “Main” screen?

What is giving the signature error the BIOS or windows as windows writes a signature to the hd

Samuria said:

What is giving the signature error the BIOS or windows as windows writes a signature to the hd

Microsoft's public keys are held in the firmware (this is a condition of being Windows certified device since Windows 8).

With secure boot enabled these are compared against the efi binaries (EFI/Microsoft/Boot/bootmgfw.efi or whatever) which are signed with Microsoft's private key.