Filevault Causing Login Problems on an M1 Mac with Monterey

After using Migration Assistant from a 6-year-old MBP 13" to a new 14” MBP M1 we now have very funky/clunky login behaviour.

 

Login Screen 01:

With a cold start or a restart, I have to 1st login to the S account. The machine will not accept the correct passwords for the two T accounts. The text “Your password is required to log in” is not present. Also, the keyboard is not lit during this process.

 

Login Screen 02 (pictured below):

But AFTER I login to the S account, then I can switch user accounts and the machine will now accept the correct passwords for either of the two T accounts. The text “Your password is required to log in” is now present. The keyboard is now lit. If I logout of all 3 accounts, the screen stays the same. But if I restart, we’re back to login screen #1.

 

 

The old 13” MBP had Filevault enabled and no weird issues like this at LogIn.

 

On the new machine Filevault is also enabled. T and T 02 accounts have a recovery key set (hopefully the same one that was used when I turned on Filevault on the 6 year old MBP 13" since it didn't give me a new one!!!), but S doesn't say it has a recovery key set (but Filevault is on).

 

Here are the Filevault settings for S, T, and T 02:





Another interesting piece to the puzzle is that when the migration happened, Migration Assistant popped up with a message that it was assigning a new password to S (but not T or T02). I had to enter the new PW to S then change it from the randomly generated one back to the one I had used for S on the old machine. I just (perhaps stupidly) assumed that it was because S was a standard account, while T and T 02 were both administrative privilege accounts.

 

I turned off Filevault on the MBP 14" M1 and it turned off almost instantaneously. I remember in the old days that Filevault seemed to take a long time and showed a progress bar; tonight it just went from on to off with no progress bar almost in real time.

 

The good news is that when Filevault was turned off on the new machine all of the login problems disappeared. Hurrah!

 

The bad news is that when I turned Filevault back on the identical logon problems reappeared :( :( :(


Again, the reencryption was almost instantaneous.

 

If anyone smarter than me (an easy thing) can suggest a way to fix this issue so that I can log straight into the T account on my gorgeous new 14” M1 without having to go through S first, I would be most grateful!

 

Thank you!!!

 

PS Black boxes in the screen logon pics are just Photoshopped privacy protectors.

 

PPS System Info

·      macOS Monterey Version 12.0.1

·      MacBook Pro (14-inch, 2021)

·      Chip Apple M1 Max


MacBook Pro (2020 and later)

Posted on Dec 17, 2021 10:42 PM

Reply
Question marked as Top-ranking reply

Posted on Jan 22, 2022 12:03 PM

While logged into the user account that is having trouble try going into the Security & Privacy System Preferences. On the General tab click the "Change Password" button. You can use your current password if you want.


With some of our organization's Filevaulted Macs with multiple user accounts I have discovered that the user account login password become disassociated from the Filevault password if the password of that account is changed (I'm assuming it was a bug from changing a user account password using the User & Groups System Preferences). I can log into that user account by first entering the old password which was used with Filevault, then once it boots to the actual user login screen I can use the correct new password for that user account. By changing the password as I have described here, macOS recombines the Filevault password and the user account password so only one password is needed for the user account. I've never had it affect the ability of any of the other user account from logging in, but you should definitely verify each user can log in after a system restart.


I highly recommend you have a good backup of this computer and each user account before doing anything just to be safe.


You should always have frequent & regular backups.


Similar questions

17 replies
Question marked as Top-ranking reply

Jan 22, 2022 12:03 PM in response to CharPatton1

While logged into the user account that is having trouble try going into the Security & Privacy System Preferences. On the General tab click the "Change Password" button. You can use your current password if you want.


With some of our organization's Filevaulted Macs with multiple user accounts I have discovered that the user account login password become disassociated from the Filevault password if the password of that account is changed (I'm assuming it was a bug from changing a user account password using the User & Groups System Preferences). I can log into that user account by first entering the old password which was used with Filevault, then once it boots to the actual user login screen I can use the correct new password for that user account. By changing the password as I have described here, macOS recombines the Filevault password and the user account password so only one password is needed for the user account. I've never had it affect the ability of any of the other user account from logging in, but you should definitely verify each user can log in after a system restart.


I highly recommend you have a good backup of this computer and each user account before doing anything just to be safe.


You should always have frequent & regular backups.


Feb 14, 2022 12:34 PM in response to CharPatton1

1. Power on the computer that has been previously FileVaulted.

2. Log into the Mac with an Administrator account to unlock the FileVaulted computer.

3. Have the Administrator log off the computer, so the computer is at the login window, asking for a user name and password. Have the additional user(s) log onto the computer they need access to.

4. Once the user is logged in, open System Preferences. 

5. Click the Security & Privacy panel.

6. Click on the FileVault tab to access the FileVault settings. 

7. Click on the padlock to allow changes to be made to the FileVault settings.

8. Click on the “Enable Users” button.

9. You will see which additional network user accounts that you can enable to log into the computer and unlock the hard drive during login.

10. Click on the Enable User button next to the user you want to allow access to. That user will be prompted to enter their login password. Click OK to accept the entered password.

11. Look for a green checkmark next to the user's name, which means they can unlock FV at login automatically.

Jan 30, 2022 4:37 PM in response to all will be well

Try entering your password multiple times and even try using an external keyboard. I have had to repeatedly enter the password to unlock some of our organization's Macs. It drives me crazy to find out the first password I attempted to use actually works five minutes later after trying dozens of other possible passwords. There is something with macOS in general that doesn't always recognize the correct password. I am sure I am typing the password correctly as I will re-enter it several times.


To further complicate matters the 2018+ Macs use a secure enclave and security chip to handle authentication. I've personally experienced a few bugs with the T2 implementation on some of our organization's Macs. It would not surprise me to find that a new Mac could become "confused" if you created a user account on first using your new Mac and later migrating a user account from your old Mac (or a backup). I think if you perform a clean install of macOS and migrate from your old Mac without first creating a new user account on the laptop you will be fine. Just be sure to transfer any files from the new user account to external media so you don't lose anything important. Personally I would go even further than a clean install and instead reset the firmware on the M1 Mac which will reset the security enclave as well as performing a clean install.

Revive or restore a Mac with Apple silicon using Apple Configurator 2 - Apple Support


Dec 18, 2021 6:15 PM in response to CharPatton1

What can sometimes happen is that the user login password can become separated from the Filevault password which tends to happen if a user account password is changed. Usually at the first login screen you may need to enter the old password to unlock Filevault, then at the second login prompt enter the latest password. This is what you are seeing when logging into the other user account, then logging out and into the other user account.


After disabling Filevault and re-enabling Filevault it should have re-associated each user account & Filevault password. The Filevault pane of System Preferences should have an option to make sure any user not associated with Filevault to be associated so that they can unlock Filevault when logging in, but this is not always shown on the Filevault pane for some reason. You may need to delete the Filevault preference file while Filevault is disabled (I'm not sure where this file is stored) so when you re-enable Filevault it may associate all users properly. I'm not certain how the passwords for Filevault are now stored on the 2018+ Macs with the T2 security chip or the M1 Macs. Are all the user accounts "admin" accounts or is the account a standard user account?


Try booting into Recovery Mode to make sure you can authenticate with each admin user. I know that the T2 security chip can cause weird behavior with authentication, but I'm not certain of an easy way around these issues except to "Restore" the T2 or M1 firmware which wipes out the security enclave, destroys all data on the SSD and reinstalls macOS through Internet Recovery.

Revive or restore a Mac with Apple silicon using Apple Configurator 2 - Apple Support


Edit: Make sure to have a good backup before attempting any changes in case something goes wrong as you may become locked out of your Mac which may require you to perform a clean install or a "Restore" of the firmware (a more extreme version of a clean install as it also resets the security enclave).

Jan 23, 2022 7:50 PM in response to CharPatton1

CharPatton1 wrote:

Two even said, "just run your computer without FileVault since it works just fine that way" (my employer's IT department would have a cow about that). Two of them escalated to more senior engineers, but the knowledgeable folks haven't responded yet. COVID seems to be impacting us all :(

FYI, with a 2018+ Mac all your data is encrypted automatically using hardware encryption provided by the T2 security chip or the M1 Mac's secure enclave. Filevault on a 2018+ Mac just adds yet another layer of protection by requiring a password to unlock the Filevault.


I can tell you from personal experience that there are some bugs with the implementation of the T2 security chip where I have had problems authenticating while booted into Recovery Mode. I ended up "restoring" the T2 firmware just to be safe. It is possible the M1 Macs may have similar issues.


I'm wondering if there is some kind of migration bug if Filevault is active on the old Mac and you are migrating to an M1 Mac (or perhaps any 2018+ Mac). While Migration Assistant is nice, I have had times where I had to manually migrate my data, settings, and apps to a new Mac. Perhaps this is one of those times. Or maybe you could temporarily disable Filevault on the older Mac before trying to migrate to the new Mac. Keep in mind unless the engineers can reproduce the issue or figure out what is happening on your new Mac, this may take a while to get resolved (if ever depending on how common the error is).

Dec 20, 2021 6:01 PM in response to CharPatton1

1) Unless you used an incorrect username, then I don't know why it failed. Perhaps this is related to the problem you had with the migration of the user account.


2) I don't know where the Filevault preference file is located or where some of the authentication information is stored on 2017 and earlier Macs. With a 2018+ T2 Mac and probably with the M1 Macs, some of the security/authentication settings are stored in the secure enclave chip.


3) Unless you want to attempt to fix the issues on the old Mac and try another migration, then the best option is to create a new user account and manually transfer your data and settings to the new Mac. Transferring the general data from the Desktop, Documents, Downloads folders is easy enough, but the more difficult part of this process is transferring photos, music, videos, and app settings since these may not be easy straight up transfers. Another option is to use a Time Machine backup from your old Mac to migrate the user account(s) to the new Mac. Maybe migrating the user accounts from a Time Machine backup may not have the same issues as migrating directly from the old Mac. I don't know if there is any difference since I've never used Time Machine. It all depends on how much time you want to invest in experimentation.


Perhaps another contributor will be able to provide a better answer with more specific detailed instructions since I'm not a macOS software expert. My Macs have very simple configurations that I will manually recreate if I cannot figure out where all the settings files are stored for each app.

Jan 22, 2022 12:40 PM in response to HWTech

Phred42, sorry to hear the bug is impacting you as well.


HWTech, thanks, as always, for chiming in with your excellent suggestions for this vexing problem.


Unfortunately, I just did what you suggested and no luck. I spent 2 hours on the phone with AppleCare yesterday and they had me do I think the same thing from Terminal, using a command that if memory serves me correctly was a simple "setpassword" or something very similar. That didn't work either for the two problem accounts.


I'll post back with a solution if anyone comes up with one.


I bought my new still basically unusable M1 MBP in October (TG my 6 yo Intel MBP is still running fine!), spent ~two months trying to fix the bug on my own (with able help from wise posters on these forums to whom I am very grateful). I went to AppleCare about a month ago and have spoken to 6 people so far. The good news is that all 6 have been very nice and pleasant. The not-so-good news is that many of them seemed to have only very basic computer knowledge and I had to go through the same explanations and time-consuming basic trouble-shooting steps each time. Two even said, "just run your computer without FileVault since it works just fine that way" (my employer's IT department would have a cow about that). Two of them escalated to more senior engineers, but the knowledgeable folks haven't responded yet. COVID seems to be impacting us all :(

Jan 30, 2022 8:11 AM in response to CharPatton1

I am interested to see this as it is very similar to one I have. After migrating from a similar age MacBook Pro withMigration assistance, I have a weird problem of two user accounts popping up (one from old computer and one from new although I didn’t intend or want two. System starts by saying password is wrong (it is right). The two accounts problem appears during new password creation and restart/sign in. In any case the new passwords are always wrong.


The Senior Apple support engineer has never seen the problem and says I need to do migration all over again from factory settings. I have asked for escalation to developers to understand the basic cause.

Dec 20, 2021 7:29 AM in response to HWTech

Many, many thanks for your input; I really appreciate it!


Q1: There was no button to: "The Filevault pane of System Preferences should have an option to make sure any user not associated with Filevault to be associated so that they can unlock Filevault when logging in, but this is not always shown on the Filevault pane for some reason." but after digging around a bit I could the suggestion to use Terminal and "sudo fdesetup add -usertoadd [username]. Unfortunately, after doing this and entering the requested passwords, I get "Unable to add one or more users to FileVault. (-69594)"


Q2: Do you know where the the Filevault preference file is located? I tried looking but couldn't find anything.


Q3: Finally, any other options you would suggest to migrate data from my old MBP13" to the new MBP M1 14"? I'm not computer savvy and just would like to have a working MBP14" after having wasted untold hours trying lots of stuff to get my new machine up and running. Can I completely wipe my new MBP14" to the bone, removing all of these weird FileVault issues, and start from scratch to transfer just the data, but no FileVault weirdness, from my MBP13" to the MBP14" M1? How do I do a deep clean wipe of the new MBP 14" M1 to ensure that any messed up FileVault settings are gone? Once the new machine is clean, how do I migrate just user data but no FileVault weirdness since Migration Assistant seems to have transferred the screwed up FIleVault settings from the old machine?


Again, many, many thanks!

Dec 26, 2021 1:47 PM in response to HWTech

esoft

Again, THANK YOU for taking the time to login and suggest potential fixes!


Does anyone know how to escalate to an Apple Engineer? Basically, I bought a brand new M1 and am now stuck, after almost 40 hours of troubleshooting that didn't work, with a brand new MBP where one has to log into one account, then switch to the main account, to get any work done :( :( :(


Can I somehow get normal behaviour where FileVault is enabled but I can log directly into my main user account?


If it helps, here are the results of today's efforts. Apologies if some of this seems nonsensical, but I'm not a computer guy, just someone who uses a computer to get non-computer work done, so tried all sorts of stuff I found online.


Jan 24, 2022 9:33 AM in response to HWTech

As always, many thanks for sharing your thoughts and expertise!


I have no domain expertise at all re encryption etc and feel better given what you said about security protections other than FIleVault. However, the real world scenario is that our employer mandates FileVault on any computer that work business is done upon (even e-mail), and has let us know that we will be "hung out to dry" if our computers are hacked and they can show we didn't have FileVault enabled :(


Great minds think alike! I redid the Migration Assistant from the 6 yo Intel MBP with FIleVault turned off, but unfortunately the result was the same. This is so weird...


As you said, my BATNA is to not use Migration Assistant and simply create three brand new user accounts on the M1 and manually install everything. Besides the time and "pain" involved with that process, now that I have almost 4 months invested in trying to figure this out, I'm very curious what the issue is so will keep trying to suss it out.


Will post back if I hear anything from Apple engineers.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Filevault Causing Login Problems on an M1 Mac with Monterey

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.