Retrospect for Windows fails to Autolaunch

Resources


If Retrospect is no longer autolaunching, first verify that you’ve got it set to automatically launch. Go to Configure > Preferences from the Retrospect Directory and click Startup under the Execution heading. Is "Automatically launch Retrospect" and "Enable Retrospect Launcher Service" checked?

Does Retrospect try to run a script right after you start it, but not at the specified time? If not, verify that your script is scheduled correctly. Go to Activity Monitor > Scheduled. Are there scripts scheduled to run? If there are, is the top one scheduled to run soon (as opposed to months or years in the future)? If it is scheduled to run some time in the future, you may have deferred execution of the script. Change this by editing your script.

If there are no scripts scheduled to run, you need to reschedule your scripts. Go to Automate>Manage Scripts to do this.

If Retrospect tries to run a script right after you launch the program, the service which autolaunches Retrospect, the Launcher, may not be working correctly. Reinstall it by doing the following:

Go to Configure > Preferences and click Startup. Uncheck "Enable Retrospect Launcher service." Now quit and restart your PC. Launch Retrospect and check "Enable Retrospect Launcher." Now quit and restart again.

Were you logged in as administrator during install? Failure to autolaunch can be a Launcher permissions issue, which would be affected by who you were logged in as when you installed the program. Try creating a new user account and add that user to the Administrator group. Then uninstalling and reinstalling Retrospect when logged in as the new administrator.


Last Update: February 13, 2012