Autostart fails after upgrade on windows

[jj-0ne-Two]

Hi, after upgrading following the recommendation to uninstall the old version as part of the upgrade, Rclone-Manager no longer autostarts after re-boot. I understand that the uninstall process would remove the windows autostart entry, but the Rclone-Manager Setting still shows as autostart is enabled (when it's not). It's easily manually fixed in Rclone-Manager by resetting this option and re-activating... but only if you remember, it's caught me out a few times.
Any chance of getting Rclone-Manager to verify at startup that the windows autostart entry is present if the option is set and re-add the entry in windows if it's missing?
Many thanks for the excellent software.

[Hakanbaban53]

Thanks for the open this discussion, and glad you're enjoying RClone Manager!

You're right: the uninstall removes the Windows autostart entry, but the "Start on startup" setting in the app stays on, so the two get out of sync. I've fixed this. On startup, if "Start on startup" is enabled, RClone Manager now checks that the system autostart entry exists and re-creates it if it's missing. After an uninstall/reinstall upgrade you no longer need to toggle the option off and on again.

The fix will be in the next release. One thing to know: if you disable the app's autostart entry from outside the app (for example by deleting the registry entry) while the setting is still on, it will be re-added at the next launch. To turn autostart off, use the setting in the app.

[jj-0ne-Two]

Wow that was quick, thanks very much Hakan