I cannot get Duplicati to automatically start, when I boot up Windows. The problem has quite some history. I am using Duplicati for many years now and had it set up as a Windows service. This used to work without problems until sometime this autumn, when the Windows service would not start and could also not be started manually.
Recently, there was a Duplicati-update which required manual installation. In the installer, I chose the option for “Launch Duplicati at startup”. To avoid conflicts, I disabled the Windows service.
I can see an entry on the autostart tab of the task manager. It has the exact same path and executable as the start menu entry, and both entries are configured to run Duplicati tray icon as administrator. However, Duplicati never comes up automatically. Starting it manually via the start menu works without problems.
Is there any log written during Duplicati startup that could give me clues of the problem?
I am running 2.1.0.2_beta_2024-11-29 on Windows 10.
My solution for autostart Duplicati is using Task Scheduler (i.e. run at log on, via command cmd /c start “Duplicati” “c:\Program Files\Duplicati 2\Duplicati.GUI.TrayIcon.exe”). This way you can also grant correct privileges for Duplicati (handy if you use VSS or usn-policy).
That one is different. It places a shortcut in the user start menu, so Windows will automatically start it during login.
Because Duplicati uses the current user to figure out where the settings database is stored, launching as a user vs as a system service causes it to look in different folders.
It is possible to enable/disable statup items in Windows settings. Is it possible that it is disabled?
For the service, there are log entries in the Windows EventViewer. If Duplicati crashes it will usually write a file named Duplicati-crashlog.txt either in the settings folder or in the temp folder, depending on where in the startup phase it crashes.