Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ for more details.
One of my Macs was doing something strange recently. A new account that was created (using Windows Migration Assistant) would sometimes not show up on the login screen. I noticed this happened only after a restart. All other accounts would be there on the login screen except this new account. However, after logging in as one of the other users and logging out, the new account would show up.

It turned out that the problem was with FileVault settings and was easily remedied. To fix, open System Preferences. Click on Security & Privacy.

There should be a message that says "Some users are unable to unlock the disk." Click on the padlock button at the bottom so that the Enable Users button can be clicked.

macosfv2_1.png macosfv2_2.png

Click the Enable Users button, this brings up another dialogue box. Click Enable User next to all the users that you want to enable (probably all of them).

The password for the user being enabled then has to be entered.

Once the user is enabled, a green check mark is shown them.

Getting back to FileVault settings after enabling all the users will no longer show the message about some users not being able to unlock the disk.

After I followed all those steps my new account would always show up on the login screen. Success!

Remove a User from FileVault

In case this needs to be reverted, the fdesetup utility comes in handy. Run this command after opening the Terminal app...
sudo fdesetup remove -user testaccount

In this case testaccount is the account that will be removed from FileVault.


Skip down to comments...
A quick disclaimer...

Although I put in a great effort into researching all the topics I cover, mistakes can happen. If you spot something out of place, please do let me know.

All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
comments powered by Disqus
Other posts you may like...