Deleted admin user account shows on startup

[Angle Loss]

late 2013 MBP 2.6GHz on 10.12.

I deleted an alternate admin user (not my main admin account) from my MBP but when I startup it only shows the deleted account to log in to. If I enter the password it loads (progress bar) which takes a little time, then it pops up my main account as it should.

Being that I have been using bootcamp a lot lately, it is frustrating to have log in take twice as long. The old account was deleted the normal way through Users&Groups and no longer shows there. It started in El Capitan and hasn't changed for Sierra.

How do I remove whatever traces of this old account still exists?

 

[KALLT]

I am guessing you are using FileVault? Is the old account only shown on that screen and you have to log in manually in the other, or does the login proceed automatically?

 

[Angle Loss]

I am guessing you are using FileVault?

FileVault is on.

Is the old account only shown on that screen and you have to log in manually in the other, or does the login proceed automatically?

The old account only shows (the name and picture associated with it) on the login screen. It won't login to that account, but merely pulls up my regular/current admin account after it tries to log in. That is to say it brings up the login screen again with my correct account name/pic.

Thanks for helping!

 

[KALLT]

For good measure, you can check whether there still is a record of the old account with the following Terminal command. It should only list your user accounts.

dscl . -list /Users UniqueID | egrep "5\d\d"

This should only list your user accounts. When you type the following command, it will list all users that can unlock FileVault. Is it mentioned there?

sudo fdesetup list

 

[Angle Loss]

When I input either of those codes, it only shows my current account and not the old one which shows at login.

 

[KALLT]

When I input either of those codes, it only shows my current account and not the old one which shows at login.

Hmm... that is weird. It is also not mentioned in this list?

dscl . -list /Users

 

[Angle Loss]

dscl . -list /Users

In this list I only see my current account mentioned.

 

[KALLT]

What you are saying seems to indicate a problem with FileVault. The account is clearly not there and your successful ‘login’ attempts at the FileVault stage mean that the FileVault unlock screen uses outdated information. Is the password the same or are you using the ‘old’ password at that stage?

What you can try is adding your account again to FileVault and see whether it overwrites or adds another entry (replace ‘your_username’ with your username).

sudo fdesetup add -usertoadd your_username

Then try this again:

sudo fdesetup list

Before you attempt this, make sure you have your FileVault recovery key ready. You don’t need it, just in case something goes wrong.

 

[Angle Loss]

Just before you responded, I was looking in FileVault in System Prefs and it allowed me to add my current account (which is what I think you were having me do with that first code?). I restarted the computer and now it shows me both accounts at the startup screen.

Though the old one is still there, I can now login straight to my correct account without the wasted time!

 

[KALLT]

Yes, that is what the command would have done. Try the last command I gave you again. I am guessing it will now show two results.

I believe FileVault somehow mixed up the account data.

 

[Angle Loss]

So I logged out and in...didn't show the old account. Restarted a second time and it is gone, just the current/regular admin account and guest options.

I just tried the last command...it only shows my current account.


Thanks so much for your help KALLT! I wouldn't have been able to fix it myself. You have saved me much time in future logins!

 

[grahamperrin]

… seems to indicate a problem with FileVault. …

It's commonplace but as far as I know, the problem is purely cosmetic.

When EfiLoginUI presents a user, or an array of users, before the Mac OS X Startup volume (a logical volume) is unlocked: what's presented is loaded from a different volume. Loaded from a non-encrypted slice of a physical disk; the slice that is used for things such as Recovery OS.

At some point, macOS will automatically, silently, invisibly mount then unmount the volume and when that automation occurs: you should expect the data to be brought up to date.

Apple Developer: Kernel Programming Guide: The Early Boot Process: Rooting

– read about Boot≠Root

 

[997440]

[...]Apple Developer: Kernel Programming Guide: The Early Boot Process: Rooting

– read about Boot≠Root

Thanks for the link. Tangential to topic -- I had an USB dongle plugged directly into a Mini port for a mouse which I also used briefly for a companion keyboard. I also had an Apple USB KB plugged into an USB hub.

With FV2 enabled the Apple KB would fail (even if I unplugged then plugged directly into the Mini) to work at login. The dongle controlled KB wasn't in use, the batteries were removed, so it didn't dawn on me right away what the problem was. The Early Boot Process was dependent on the dongle KB.