Operating System Loader failed signature verification. WARNING: The file may have been tampered with

102 views
Skip to first unread message

Humble

unread,
Nov 23, 2018, 5:07:32 PM11/23/18
to qubes-users
Good day,

I've got a brand new Dell Precision 7730 that I was planning to install QubesOS on.
As soon as I attempt to start the boot sequence, I get this error:

Operating System Loader failed signature verification. WARNING: The file may have been tampered with

I've tried several OS-es and Ubuntu and ESXi boot just fine, with Xen and a couple more failing to do so.
Upgraded the bios and all that, still no go.

Unfortunately from what I understand this generation of laptops no longer accepts installations of OS-es in legacy mode.

I am looking forward for your thougths.

unman

unread,
Nov 23, 2018, 7:54:03 PM11/23/18
to qubes-users
You have TPM enabled: I think you can disable it:
Go into the BIOS (F2 on boot?)
Under Security, you can turn off TPM, which should allow you to boot
other OS.
You can also turn off Secure Boot.

I dont think that you are prohibited from legacy boot.
Have a look under the Advanced Boot options, and you may be able to
enable legacy boot there.

unman

humble...@gmail.com

unread,
Nov 24, 2018, 1:21:37 AM11/24/18
to qubes-users

Legacy boot is not prohibited, but is allowed only for external devices (USB, SD Card, PXE).
This is the KB article from Dell's official site and this appears to be the norm from now on for any Enterprise-grade Dell laptop.
https://www.dell.com/support/article/us/en/04/sln309720/newer-dell-systems-unable-to-boot-to-internal-boot-device-in-legacy-boot-mode?lang=en

Looking forward for any guidance.

unman

unread,
Nov 24, 2018, 6:52:52 AM11/24/18
to qubes-users
I'm not sure what more you want. You have bought a laptop that cant boot
legacy mode from internal disk.
Try installing in UEFI mode.

humble...@gmail.com

unread,
Nov 24, 2018, 7:49:41 AM11/24/18
to qubes-users

.... Which doesn't work and it gives the error in the original post (Operating System Loader failed signature verification. WARNING: The file may have been tampered with) indicating that there are integrity checks that the current (and the 4.0.1-rc1) image are failing for the current generation of UEFI-enabled BIOS-es.
What is not clear in the above? UEFI doesn't work and Legacy isn't supported.

unman

unread,
Nov 24, 2018, 9:14:57 PM11/24/18
to qubes-users
No, it indicates that you still havent disabled SecureBoot, as I suggested.
Reply all
Reply to author
Forward
0 new messages