Open trupf opened 4 years ago
shdeb
commented
3 years ago Setting the "launch on system startup" sets the nextcloud-portable\app\nextcloud.exe as startup, instead of nextcloud-portable\nextcloud-portable.exe which is the actual launcher.
FIX: unset it and manually add nextcloud-portable\nextcloud-portable.exe at system logon from task scheduler.
shdeb
commented
3 years ago or you can also run/import the following reg file(copy it and save it as .reg)
replace the ---Path-to-root--- with install folder eg: A:\\programs\\nextcloud-portable
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"Nextcloud-portable"="---Path-to-root---\\nextcloud-portable.exe"
denmedius
commented
2 years ago Thanks @trupf : I had the exact same problem under Ruindows 10 with release 3.2.2, 7z package (after each computer reboot, ad to setup again NextCould client FROM SCRATCH about my cloud account and target local folder).
So I unchecked the "Launch on system startup", and added a shortcut to "
And since then it runs fine, even after computer reboot (no need to reconfigure cloud account).
I'm using current version 2.6.4 with Windows 10. Every time the client is started, the client does not automatically reconnect to my Nextcloud server (as the Ubuntu client does). I have to manually initiate the connect a web browser window will open where i have to log into my Nextcloud instance and confirm that the client is allowed to connect. I think this should be a one time confirmation only and afterwards the connection info should be saved for automatic reconnect at next application start. The sync itself is working after I have confirmed the connection till next application startup.