This post is more than 5 years old
3 Posts
2
30546
Inspiron 13-7359: Windows 10, Operating System Loader has no signature. Incompatible with Secureboot. All bootable devices failed Secure Boot verification.
I get this error when booting up my 2-in-1. It was working fine just last night! Please help me.
System Bios: 01.10.00
Service Tag: <ADMIN NOTE: Service tag removed per privacy policy>
EPSA: Build 4304.09 UEFI ROM
mistymi
1 Message
9
July 13th, 2017 04:00
Operating System Loader Has No Signature . . .
these steps resolved my issue:
1. On Startup, press F12
2. Reset Bios to default settings
3. Restart laptop
4. In Bios, select Boot Sequence menu
5. Manually ADD additional line with the name "Windows Boot Manager"
6. Select /EFI/BOOT/BOOTX64.EFI
7. Exit
answer found at:
www.reddit.com/.../
Laustin46
1 Message
0
October 16th, 2016 14:00
I just encountered the same issue. Have you found a solution yet?
Slayaboy87
3 Posts
0
October 16th, 2016 21:00
Someone in another forum suggested getting a Windows 10 recovery drive and reinstalling
sportsjuice
1 Message
0
October 29th, 2016 14:00
Anybody have any luck with this yet? Same issue, just on a 7368. Laptop last night seemed to be doing some updates on its own. went to restart today and got that error message.
paulholly
1 Message
0
November 5th, 2016 05:00
I have exactly the same message on am Inspiron 5559. As above everything else was fine. Critical battery notification, an automated hardware check ran and then the above message is displayed.
Slayaboy87
3 Posts
0
November 5th, 2016 19:00
I tried everything including a recovery disk and nothing worked. Spent 2 hours on the phone with dell and finally had to send it in for repair. They replaced the hard drive and reinstalled windows 10. Lost all of my files. I read that the automatic windows updates for 10 bricks the system.
rfwimberly69
1 Message
0
July 22nd, 2017 07:00
THIS WORKED!!!! You are AWESOME!!! thanks so much!
jdng
2 Posts
0
July 22nd, 2017 18:00
This works, however everything I reboot my laptop. I will have to repeat the steps again.
Any one has a solution to fix that?
Raczo
105 Posts
0
July 29th, 2017 14:00
As a workaround, try to disable Secure Boot.
JerryIrons
7 Posts
0
December 13th, 2018 18:00
OMG this was a huge help for me, thank you for posting this!
I played around with turning off secureboot, setting legacy options etc and all that got me was unbootable hard drive messages.
Went back to secureboot settings, deleted any boot types, and then manually added a new windows boot manager like you said, building it to point to the bootx64.efi. Worked like a youknowwhat champ!
Thanks again!
Raj2909
1 Message
0
September 11th, 2019 23:00