Closed Adito5393 closed 1 year ago
It sounds like you performed a non administrative (per user) installation.
The purpose of executing the StartSyncthing.js
script using wscript.exe
(rather than cscript.exe
) is to prevent the superfluous console window from appearing. This is by design. I just tested the per-user installation and the logon task works as expected: Syncthing starts when the user logs on, and the configuration page link works as expected.
The task scheduler reported that the action was successfully executed. I tried to start it via the provided shortcut
Start Syncthing
without any luck. Running the following command manually also did not start it:C:\Windows\System32\wscript.exe "C:\Users\USERNAME\AppData\Local\Programs\Syncthing\StartSyncthing.js"
Fix
In the end, what actually makes it start was:
C:\Windows\System32\cscript.exe "C:\Users\USERNAME\AppData\Local\Programs\Syncthing\StartSyncthing.js"
Any ideas whywscript
didn't work for me? Butcscript
works fine? (I have little experience with Windows app development)FYI, I have crowdstrike falcon installed & Windows Defender disabled. Maybe they block JS execution via wscript? Some system info:
PS: Thanks for making this cool installer for Windows & I'm reporting this more for others to know how to fix this issue if they ever encounter it.