To learn what you can do with Tails, refer to our [[documentation|doc]].

For more general questions about Tails, refer to our [[FAQ|support/faq]].

For issues with graphics cards, see our [[known issues with graphics cards|known_issues/graphics]].

This section lists known problems with specific hardware.

Tails does not start at all on Mac models that use the Apple chips (M1, M2, and so on) and on many other Mac models.

Apple does not prioritize collaborating with Free Software projects. Their newest hardware is usually very hard for Free Software developers to get working with Linux, and thus Tails. PC hardware tends to be more open and work better with Linux.

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

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

<p>See our instructions on [[starting Tails on PC|doc/first_steps/start/pc]]
for general troubleshooting tips.</p>

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>

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

<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.