-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autostart does nothing, never autostarts #39
Comments
By "toggle" I assume you mean "check box." Which specific check box are you referring to? I just tested the 1.27.11 installer on a Windows 11 machine, and all of the automatic startup stuff worked just fine for both current user and installing as a service.
You're going to have to be more specific about what you mean. (Remember, nobody can see your screen!)
What, specifically, "happens" (or doesn't "happen")? The behavior of the installer is very different between the non administrative (per user) and administrative (per computer) installation modes. Have you reviewed the documentation? (Again: Remember that nobody can see your screen.) |
Yes. You need to fix that error first. |
See this issue also: This is not a Syncthing Windows Setup issue but rather something broken on your machine. I can't reproduce it. |
Alright, I did some digging and found a fix. Thought it might help others to keep this here I went to |
Thanks for the update and the fix! |
Thanks for this! No idea how my one got borked, but this did the trick! |
The next version of Setup will check if this value is correct and abort the install if it's missing or incorrect. |
When installing syncthing on Windows, it gives you a toggle on whether you want it to start on user logon. Yet, it does nothing. It doesn't start on logon, nor does it register a service, put a shortcut in the startup folder or even just a task scheduler entry. Nothing. Why have this toggle if it does nothing? This happens regardless of running syncthing's installer with admin or not.
The text was updated successfully, but these errors were encountered: