# Loader.conf reboot-for-bitlocker

**URL:** <https://forum.endeavouros.com/t/loader-conf-reboot-for-bitlocker/50522>\
**Category:** EndeavourOS installation\
**Created:** [January 28, 2024, 1:47pm UTC](https://forum.endeavouros.com/t/loader-conf-reboot-for-bitlocker/50522 "2024-01-28T13:47:59Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [January 28, 2024, 2:50pm UTC](https://forum.endeavouros.com/t/loader-conf-reboot-for-bitlocker/50522/6 "2024-01-28T14:50:08Z")

</div>

> [@joekamprad](#):
>
> [https://wiki.archlinux.org/title/Systemd-boot#Add\_support\_for\_Windows\_BitLocker\_TPM\_unlocking](https://wiki.archlinux.org/title/Systemd-boot#Add_support_for_Windows_BitLocker_TPM_unlocking)
> 
> it is a general support feature …

If `reboot-for-bitlocker’ is already set to be enabled in loder.conf, is there an explanation for why the line not being recognized?

> [@Unexpected entries in journalctl. system only boots randomly](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/1):
>
> ryzen systemd-logind[776]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.

Perhaps it has only bearing when a Windows system with BitLocker is present and then there will be no entry in the journal 🤔

---

_[View the full topic](https://forum.endeavouros.com/t/loader-conf-reboot-for-bitlocker/50522)._