История изменений

Исправление Vsevolod-linuxoid, 28.06.17 13:29 (текущая версия) :

Винда пишет свой загрузчик в removable media path, что и приводит к этой хрени. Делают разрабы мелкомягкие это из-за кривых UEFI, чем ещё и усугубляют ситуацию, вот цитата из статьи про UEFI wiki Debian:

Many UEFI firmware implementations are unfortunately buggy, as mentioned earlier. Despite the specification for boot entries and boot order being quite clear about how things should work, there are lots of systems in the wild which get it wrong. Some systems simply ignore valid requests to add new boot entries. Others will accept those requests, but will refuse to use them unless they describe themselves as «Windows» or similar. There are lots of other similar bugs out there, suggesting that many system vendors have done very little testing beyond «does it work with Windows?»
As described above, on a UEFI system bootloaders should be installed only in the correct vendor-specific directory in the EFI System Partition (ESP). But, because of the buggy firmware implementations out there, operating system distributors cannot necessarily expect that this will work correctly for all systems. Microsoft have worked around this (and arguably also made the problem worse) - the Windows installer also installs to the removable media path in the ESP (e.g. \EFI\boot\bootx64.efi for amd64/X64 systems). All firmware implentations have to use this path to be able to run an OS installer. This means that Windows will always work on all these broken implementations, but it also means that system vendors can get away with shipping broken implementations. It removes the idea of having a fallback boot path and sensible control of boot order.
All OS installers installing things to this removable media path will conflict with any other such installers, which is bad and wrong. That's why in Debian we don't do this by default.

В общем, тебе мешает винда + кривой UEFI. Проще всего — снести все системы с компа, отключить UEFI совсем, оставив Legacy(BIOS), потом переставь винду и уже тогда ставь Tails в дуалбуте.

Исходная версия Vsevolod-linuxoid, 28.06.17 13:28:

As described above, on a UEFI system bootloaders should be installed only in the correct vendor-specific directory in the EFI System Partition (ESP). But, because of the buggy firmware implementations out there, operating system distributors cannot necessarily expect that this will work correctly for all systems. Microsoft have worked around this (and arguably also made the problem worse) - the Windows installer also installs to the removable media path in the ESP (e.g. \EFI\boot\bootx64.efi for amd64/X64 systems). All firmware implentations have to use this path to be able to run an OS installer. This means that Windows will always work on all these broken implementations, but it also means that system vendors can get away with shipping broken implementations. It removes the idea of having a fallback boot path and sensible control of boot order.