MacBook Pro 2016, TouchID and FileVault

Question

Has anyone managed to get TouchID and FileVault to work on a MacBook Pro 2016?I commissioned a new MacBook Pro 2016 to replace my MacBook Pro 2014.My old machine did not have FileVault enabled and it had automatic login enabled. When I used Migration Assistant to transfer my files to my new machine, I took the opportunity to enable FileVault on the new machine.I found that on my new machine, I wasn&#x27;t able to use TouchID because it claimed Automatic Login was enabled. However, when I went to System Settings / Users &amp; Groups / Login Options, Automatic Login was clearly shown as off, and indeed locked off (because FileVault was on).I eventually realised that I needed to switch FileVault off, to re-enable the Automatic Login switch, then toggle the switch to off. I did that and it worked. I enrolled three fingers into TouchID and all was well.Until I switched FileVault on again.Then, I discovered that TouchID had no fingerprints registered for me. Fair enough, I would enrol some new ones. Unfortunately, when I tried to enrol new fingerprints I got the message "Fingerprint limit reached.".I thought perhaps there were some ghost fingerprints hidden by FileVault that I could exorcise. So I disabled FileVault, re-enrolled my fingerprints and deleted them all, hoping to somehow clear the registry of fingerprints. I then switched FileVault on again.Still no luck. With FileVault enabled, TouchID reported "Fingerprint limit reached", although no fingerprints were shown registered. So, off with FileVault again.At present, I have my new Mac (which, in spite of the problem above, I&#x27;m enjoying immensely), but I have not found a way of using FileVault and TouchID at the same time.p.s. This has been a painful process. I have c. 1 TB of data so switching FileVault on or off takes a few hours each way. Moreover, I can&#x27;t quite believe that sweeping all those files several times won&#x27;t have left them untouched. I&#x27;m currently having to rebuild my mail database and re-index spotlight, having found the index was missing files and mail was missing messages. I hope these last symptoms aren&#x27;t related.p.p.s. I have no particular need to encrypt my files with FileVault, I&#x27;m only concerned that if I don&#x27;t enable FileVault, someone else might, and so lock me out of my data.

FoxFifth · Accepted Answer

I&#x27;m using FileVault and Touch ID on my 2016 MacBook Pro with no problems. I didn&#x27;t use Migration Assistant and I turned FileVault on before manually moving files from an external hard drive. I use FileVault in case the MacBook is ever stolen; it doesn&#x27;t have anything extremely sensitive but does have things like income tax returns with social security numbers, etc.Sorry that I don&#x27;t have any suggestions or help to offer other than the fact that it does work with Touch ID.

Tim Jervis · Answer

Many thanks for taking the time to reply.I think there might be a problem with my particular path of:Machine 1: setup with Automatic Login + no FileVaultMachine 2: new, uninitialisedMachine 2: startup, Migration Assistant from Machine 1, switching on FileVaultMachine 2: Touch ID not available (perhaps due to ghost setting for Automatic Login) Machine 2: switch off FileVaultMachine 2: TouchID available. Enrol fingerprintsMachine 2: switch on FileVaultMachine 2: Touch ID not available, no fingerprints enrolled, not able to enrol new fingerprintsMachine 2: switch off FileVault. Touch ID available. Enrol fingerprints.Perhaps if Automatic Login had been disabled on Machine 1 above, as a new step 1.5, then TouchID would have worked in step 4.

crazytyper · Answer

I have exactly the same problem (also used the migration assistant).I tried to fix it using https://support.apple.com/en-us/HT202842 without any luck.Maybe one has to delete keys autoLoginUser and autoLoginUserUID from plist com.apple.loginwindow too?

pupkinpie2 · Answer

I too have the same issue and just as you described.  I reached out for Apple chat support to ask why Touch ID didn&#x27;t work.  They told me to just turn of FileVault.  Since I had to restart to do this, I didn&#x27;t get to ask the follow up question as to why.  I have a late 2016 MacBook Pro with Touch Bar.

pupkinpie2 · Answer

After spending 3 hours with online Apple Support here is what I found out to fix the issue.1)  Disable and delete all Touch ID fingerprints2)  Turn off File Vault3)  Turn on File Vault and wait for it to fully authenticate and finish4)  Then turn on Touch ID and input fingerprints5)  Both should be compatible at this timeGood luck!

Tim Jervis · Answer

Hi there - thanks for the news but unfortunately I tried this already and it failed at step 4.The only thing different from your procedure in my case was that there were no fingerprints registered when I tried to follow step 1, "Disable and delete all Touch ID fingerprints", with FileVault on. In effect, it was already deleted and disabled.I presume your procedure worked in your case, but can you please confirm? Was there anything else you think might have been relevant in your 3 hour session?

prl99 · Answer

I&#x27;m waiting to hear good results on this question before buying a 2016 MBP. I&#x27;ve also read about graphics issues when using FileVault.I&#x27;ve used FileVault for many years, first at work and now on my older MBP. @pupkinpie2 suggested waiting until FV had finished encrypting. On my 2011 MBP, it can take more than a few hours for this process to finish. The best way to make sure it&#x27;s finished is to use the Terminal and run the following command:&gt;diskutil cs list (or diskutil coreStorage list)You&#x27;ll get something similar to this:+-- Logical Volume Group 70B9016C-B8CD-4078-945F-334216F898C8    &#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;    Name:         MacHD    Status:       Online    Size:         499999997952 B (500.0 GB)    Free Space:   18907136 B (18.9 MB)    |    +-&lt; Physical Volume 8E98EFA7-A062-4137-A557-457B4FEE090C    |   ----------------------------------------------------    |   Index:    0    |   Disk:     disk0s2    |   Status:   Online    |   Size:     499999997952 B (500.0 GB)    |    +-&gt; Logical Volume Family 8BBFC4B9-77A5-4363-91F0-A5BA44E9C6B4        ----------------------------------------------------------        Encryption Type:         AES-XTS        Encryption Status:       Unlocked        Conversion Status:       Complete        High Level Queries:      Fully Secure        |                        Passphrase Required        |                        Accepts New Users        |                        Has Visible Users        |                        Has Volume Key        |        +-&gt; Logical Volume 136EAE1D-3CF0-44BD-A341-D50DDD5A3DB8            ---------------------------------------------------            Disk:                  disk2            Status:                Online            Size (Total):          499628769280 B (499.6 GB)            Revertible:            Yes (unlock and decryption required)            Revert Status:         Reboot required            LV Name:               MacHD            Volume Name:           MacHD            Content Hint:          Apple_HFS

pupkinpie2 · Answer

So far it seems to be working.  Touch ID is working and File Vault is still enabled.  I had to speak with a second tier tech though Apple Support (chat).  Im assuming that since it went to this level their is some issue with data migration.Personally it should be like your iPhone.  Before you sync anything you set up Touch ID and File Vault, then data migrate.  Apple makes data migration the first step.It could also be that my old Macbook pro was from 2009.

pupkinpie2 · Answer

I have not noticed any graphics issues.  But then again I am not an advanced Mac user.  I would recommend the computer.  But I upgraded from a 2009 model that was my only computer.  It was time to upgrade!

Surge74 · Answer

Mine works, but only sometimes. Specifically, TouchID only works occasionally, when waking the Mac from sleep. Firevault is on. I think this is a bug with TouchID.

prl99 · Answer

Have you tried using TouchID during the first disk un-lock sequence? Right after powering your MBP on. Once on, TouchID shouldn&#x27;t have an issue waking from sleep, I&#x27;m hoping it also works as the first logon. I would hope the Secure Enclave hardware is smart enough to be used at this point, otherwise FileVault might still not be secure even after Apple patched the latest issues.I&#x27;d document your process and submit a bug report. Apple does read these. bugreport.apple.com Of course you need an ADC account, which I no longer have.