Login issue related to FileVault after installing Tahoe Beta

[schrup21]

Hi everyone, I hope you all doing great!

 

I have a small question: After installing Tahoe Beta (from Ventura with the Installer App) on a separate APFS volume, I was no longer able to log in to any of my volumes (Mojave, Big Sur, Ventura, Sequia). Neither the (correct) passwords nor the recovery keys worked. I had to disable FileVault via Recovery to resolve the issue. However, when I re-enable FileVault, I get the same.

 

Am I the only one? 😂

 

I suspect the installer changed something in /System/Volumes/Preboot but I have no idea what.

 

I would like to add, that I couldn't complete the installation of Tahoe Beta in the first try (I oversaw that Opencore 1.0.5 is needed), I had to do it later again (after fixing my log in issues). This tells me, that the Installer App itself created me that trouble (yea, I was a little shocked after the recovery keys did not work 😅).

 

many greetings from near Munich!

[schrup21]

@mhaeuser has provided a solution or let's say workaround:

 

https://github.com/acidanthera/bugtracker/issues/2499#issuecomment-2993805720

[Jay AReddick]

On 6/22/2025 at 5:45 PM, schrup21 said:

@mhaeuser has provided a solution or let's say workaround:

 

https://github.com/acidanthera/crazy flips 3d/bugtracker/issues/2499#issuecomment-2993805720

Could the Tahoe Beta installer have modified the Preboot volume or Secure Token settings in a way that breaks FileVault authentication across all APFS volumes?

Edited July 3, 2025 by Jay AReddick

[schrup21]

@Jay AReddick as mhaeuser suggested, Tahoe's APFS driver seems to have a bug - loading Sequoia's apfs_aligned.efi circumvents the issue.

[schrup21]

@cropsky Some people experienced this behavior, where FileVault was automatically activated in Tahoe and a recovery key was stored in the password safe – I didn't experience this either. However, after starting the Tahoe installation, I was unable to boot my remaining FileVault-encrypted APFS volumes because, as described above, neither the password nor the recovery key were accepted.
When an operating system containing a newer APFS driver version is installed in a shared volume group, this driver is used. Tahoe's APFS driver either contains a bug or the effect is intended. Real Macs, or let me say, those that Tahoe supports, do not seem to have the problem - so to me it looks like this might be intentional.

[schrup21]

On 6/28/2025 at 5:11 PM, cropsky said:

in no case I have FileVault at default turn on

it might be that FV is automatically turned on, if your Hack is connected to Internet at it's initial setup + you are setting up your Apple ID