Open Radar

 
Summary:
When trying to enable FileVault 2 for the first time, you were previously able (in 10.9 and 10.10) to add the -authrestart flag in the command in order to seamlessly enable FileVault and boot back into the OS. Since the release of 10.11 Build 15A284, this feature no longer works and returns the following error: "Error: A problem occurred while trying to enable FileVault. (22)"

Steps to Reproduce:
1. Erase disk on machine from NetBoot environment with terminal command "diskutil cs delete LVG UUID"
2. Reinstall Mac OS 10.11 using Recovery HD and Mac App Store download
3. Boot into OS, open terminal and run the following command "fdesetup enable -authrestart"
4. After running the command, you are prompted for the username and password of the user you want to enable on the disk
5. You are presented with the error noted in the description and brought back to the command prompt.
6. If you run the command "fdesetup enable" without the "-authrestart" flag, it will enable FileVault as expected.

Expected Results:
1. Erase disk on machine from NetBoot environment with terminal command "diskutil cs delete LVG UUID"
2. Reinstall Mac OS 10.11 using Recovery HD and Mac App Store download
3. Boot into OS, open terminal and run the following command "fdesetup enable -authrestart"
4. After running the command, fill in the information for the user you would like to enable on the disk (username and password)
5. The computer reboots and passes through the FileVault EFI Login screen and you are presented with the OS Login Window.

Actual Results:
After being prompted for the username and password of the user you would like to enable to unlock the disk, you are presented with the error "Error: A problem occurred while trying to enable FileVault. (22)" and FileVault is not enabled.

Version:
Tested on 2 separate OS versions:
1. 10.11 (15A284)
2. 10.11.1 (15B42)

Configuration:
This was tested on 2 separate machines:
1. Macbook (Retina, 12-inch, Early 2015)
2. Macbook Air (11-inch, Mid 2012)