<p>[[Let us know|support/talk]] if you discover a new issue or workaround.</p>

<h3 id="dell-latitude-e6430">Dell Latitude E6430 and E6230</h3>

With BIOS versions A03 06/03/2012 (and A09, A11, and A12)

Workaround (at least with BIOS versions A09, A11, and A12): just hit enter and it will continue with the boot.

This machine does not start from a Tails USB stick: the Linux kernel included in at least Tails 3.11 to 3.13.1, inclusive, does not support the hardware USB controller.

<p>See our instructions on [[starting Tails on Mac|doc/first_steps/start/mac#not-entirely]]
for general troubleshooting tips.</p>

To start Tails successfully, [[add the following boot option when starting Tails|doc/advanced_topics/boot_options]]:

To start Tails successfully, try to [[add the following boot option when starting Tails|doc/advanced_topics/boot_options]]:

The keyboard and mouse do not work on this laptop. If you find a workaround, please let us know.

<h2 id="sbat">Shim SBAT verification error</h2>

This section applies if you get the following error message, either when starting Tails or when restarting your regular Linux operating system after starting Tails.

<p class="code">
Verifying shim SBAT data failed: Security Policy Violation<br>
Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation
</p>

If you get this error message when starting Tails, then do a [[manual upgrade|doc/upgrade#manual]] of your Tails USB to Tails 6.7 or later.

If you get this error message when starting your regular Linux operating system, then it means that your Linux operating system is outdated.

Edit your UEFI settings to disable Secure Boot.

With Secure Boot disabled, your regular Linux operating system should
start again.

To learn how to edit the BIOS or UEFI settings, search for the user manual
of the computer on the support website of the manufacturer.

Update your regular Linux operating system.

Try to enable Secure Boot again in your UEFI settings.

If your regular Linux operating system still doesn't start, then disable
Secure Boot again. You can try to enable Secure Boot again in the future.