I am aware of the authenticated restart when using FileVault 2 on OS X. Running the fdesetup authrestart command does however restart the system immediately.

Now, when running the OS X Update from the App Store (which often requires restarting the system) the update process reboots the system automatically at "its own convenience". It prompts about the restart requirement before starting the whole update process and there is no "you should reboot now"-point in time.

Is there any way to "combine" OS X Update from the App Store with authenticated restart so that a remote system with system drive would not require manual drive unlocking from the console?

  • Good question - I have exactly the same one. Please come back here if you find anything out, as will I.
    – GAM
    Commented Sep 28, 2016 at 7:19

2 Answers 2


It sounds like you want the next restart, whenever it might occur, to skip FileVault authorization. You can use the -delayminutes option with a value of -1 for this.

From the fdesetup man page:

authrestart [-inputplist] [-delayminutes number_of_minutes_to_delay] [-verbose]

If FileVault is enabled on the current volume, it restarts the system, bypassing the initial unlock. The optional -delayminutes option can be used to delay the restart command for a set number of minutes. A value of 0 represents 'immediately', and a value of -1 represents 'never'. The command may not work on all systems.

Try running the following command before the system update:

sudo fdesetup authrestart -delayminutes -1
  • 4
    Works like a charm!
    – Hank
    Commented Mar 9, 2021 at 13:31

I wanted a simple way to initial a Filevault Restart on Macs so I created FilevaultReboot

How FilevaultReboot Works

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .