Thanks.
In Windows, that says to me that I’m running 2 Scheduled Tasks.
First Scheduled Task: Run c:\Program Files\odrive.exe without any parameters at a triggered time. In my case, run odrive at 11 PM. Don’t “stop the task”, no matter how long it runs.
Second Scheduled Task: Shut down the exe started in the previous task:
Download the python, CLI interface of odrive. The .exe in the .zip file is, confusingly, called odrive.exe. This is not the same odrive.exe that you see running in Task Manager. Instead, this is a python-strapped command line interface (CLI) version also called odrive.exe. I saved it as “odriveCLI.exe” in “c:\program files\odrive” to avoid confusion.
Create a Windows Scheduled Task to shutdown odrive.
The “Action” tab should have c:\Program Files\odriveCLI.exe" as the “Program/Script/” The “Add Arguments” field should say “shutdown.”
The Trigger tab should set a time to shutdown odrive. In my case, 7 AM.
Suggestion: Make odriveCLI.exe part of the Windows download/install package. It’s 13 additional megabytes, sure. But it will help adoption and keep the CLI local and uniquely named.