bill-stewart / syncthingwindowssetup Goto Github PK

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.

C:Users...\Syncthing\StartSyncthing.js

I tried a bunch of things like sfc/ scannow or editing the regedit with https://www.winhelponline.com/blog/error-there-is-no-script-engine-for-file-extension-when-running-js-files/ but both didn't work

FYI I uninstalled the application and deleted the config folder so idk why it is still trying to run this file

By default, this executable gets flagged as a virus, making it hard to use on Windows without shutting down Windows Security:

Any clue what might be causing that?

Could not install v1.27.6 on Windows Server 2019 Standard.
The installer - appears to be down.
I was able to install v1.27.5 with no problems.

Setup shows the Eula but cannot click Next or Cancel, X works to cancel setup, works fine on v1.26 setup

Is this fork using the same config file than the original? I am having trouble resetting the password by removing the user and password entry from the config file. Any suggestions? I have also posted on the Syncthing forum itself.

https://forum.syncthing.net/t/login-password-popup-after-updating-config-file/19791/3

Thank you for any feedback!

I have a few installs of SyncthingWindowsSetup but they are all on Windows 10 and only 1 on Windows 11.

The Windows 11 instance is giving me issues. I see the service (All Users install) starting up upon boot but then it crashes. I have already reinstalled it just to clear things out. But the same issue occurred.

I found the below in the event log. When I manually start up the service again, it stays running.

I just want you to know that VirusTotal is issuing some red flags:

https://www.virustotal.com/gui/file/fac31c2c48b5211ca839fded7965b61dec9c9de424ea20440c12ff643d131fca

I hope there is no serious problem.

And also thank's for that awesome piece of software ^~^

Hi,
I'm trying to use latest syncthing-1.21.0-setup.exe with parameters for silent installation /silent /allusers /log="dir" /norestart on Windows Server 2019 in default directory C:\Program Files\Syncthing. Unfortunatelly I get this error:

Installation on Windows 10 and Windows Server 2016 was successful.

I've noticed this happening sometimes when my files aren't syncing after I first boot my laptop. Changing battery mode to High Performance doesn't do anything but if I plug in the charger, it starts. If I manually start Syncthing, then upon plugging in, another instance is started but it closes with a dialog box since another is already open. Haven't checked if Syncthing always starts only when plugged in.

The issue here: Install as current user, access is granted, esp. if the current user is a domain user.
Install as a local admin user - no access is granted to network shares.

I attempted to change the user that starts the service, but SyncThing does not start. Possibly I need to modify the config or the level of access granted.

The fix: In the installer, create an option to use a specific service account (ie. fabricom\SyncThingService) to run as a service. This would allow for granular NTFS permissions on connected UNC shares that require synchronization to non-domain joined resources.

Additional add to the installer: Offer the ability to change the default directory at installation, simplifying the post-install process.

I installed v1.19.2 with no issues.

VirusTotal link:

https://www.virustotal.com/gui/file/f3b7de57a9eb522c00e0e8e632a408b84209d20ea9f367e618442c05e55b6654

I have submitted to the following vendors as a false positive. "Fixed" means the vendor has acknowledged the false positive and marked it as not malware.

• BitDefender: Fixed
• Broadcom/Symantec: Fixed
• AVG: Fixed
• Avast: Fixed
• ALYac (estsecurity.com): Awaiting response
• Cylance: Awaiting response
• ESET-NOD32: Awaiting response
• Fortinet: Awaiting response
• McAfee: Awaiting response
• Microsoft: Awaiting response
• Sophos: Awaiting response
• VIPRE: Awaiting response

That's all I have time for right now.

After uninstalling Syncthing on Windows 10 it is impossible to delete the folder /Users/SyncthingServiceAcct and all files within it. Even with admin rights it is not possible - windows says I don't have enough access rights. For example:

PS C:\Users> rm .\SyncthingServiceAcct\ntuser.dat.LOG2
rm : Das Element C:\Users\SyncthingServiceAcct\ntuser.dat.LOG2 kann nicht entfernt werden: Sie besitzen keine ausreichenden Zugriffsberechtigungen zum Ausführen dieses Vorgangs.
In Zeile:1 Zeichen:1
+ rm .\SyncthingServiceAcct\ntuser.dat.LOG2
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (C:\Users\Syncth...ntuser.dat.LOG2:FileInfo) [Remove-Item], IOException
    + FullyQualifiedErrorId : RemoveFileSystemItemUnAuthorizedAccess,Microsoft.PowerShell.Commands.RemoveItemCommand

I have already deleted the service account with:

net user "SyncthingServiceAcct" /delete

Any idea what I should do?

I did not migrate anything. This is a fresh install that was completely inoperative and threw repeated error messages at me in the administrative page (localhost:8384).

Since the service runs under SyncthingServiceAcct, it has no access to the aforementioned config directory or config file.

I manually granted that user full permissions on that directory.

I did take a look at the readme, after encountering this issue and figuring that I should grant full permissions to that service user on the config directory.

I think the setup is missing a step or two. And some explanations, right in the setup.

If you think that reading the readme is mandatory, then make the installer open it.

I don't see a reason why the setup shouldn't at least take care of the permissions on the config directory. Setup should set this so a default install doesn't require user intervention to even work on a basic level.

I'd also appreciate if the setup caused a browser to open the local admin page (localhost:8384) after setup is done.

i look at services but the syncthing service was disabled and the was something wrong ( tried to edit service but password was not correct)
then i add password to user and reinstall it , it working, but another issuse its not have privileges to write to my folder
i manually add Syncthing user to the folder (read wright privileges) and now its working

Bitdefender Internet Security 26.0.34.145 is installed on the PC I intend to use Syncthing. During the installation process, BitDefender through up a notification. The full text:

Malicious command line detected
2 hours ago

Feature:
Antivirus

The app C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe was passed a malicious command line and has been blocked. Your device is now safe.

Command line: "C:\WINDOWS\system32\WindowsPowerShell\v1.0\PowerShell.exe" -NoProfile -NonInteractive -EncodedCommand ZgB1AG4AYwB0AGkAbwBuACAARABpAHMAYQBiAGwAZQAtAEUAeABlAGMAdQB0AGkAbwBuAFAAbwBsAGkAYwB5AHsAKAAkAGMAPQAkAEUAeABlAGMAdQB0AGkAbwBuAEMAbwBuAHQAZQB4AHQALgBHAGUAdABUAHkAcABlACgAKQAuAEcAZQB0AEYAaQBlAGwAZAAoACIAXwBjAG8AbgB0AGUAeAB0ACIALAAiAE4AbwBuAFAAdQBiAGwAaQBjACwASQBuAHMAdABhAG4AYwBlACIAKQAuAEcAZQB0AFYAYQBsAHUAZQAoACQARQB4AGUAYwB1AHQAaQBvAG4AQwBvAG4AdABlAHgAdAApACkALgBHAGUAdABUAHkAcABlACgAKQAuAEcAZQB0AEYAaQBlAGwAZAAoACIAXwBhAHUAdABoAG8AcgBpAHoAYQB0AGkAbwBuAE0AYQBuAGEAZwBlAHIAIgAsACIATgBvAG4AUAB1AGIAbABpAGMALABJAG4AcwB0AGEAbgBjAGUAIgApAC4AUwBlAHQAVgBhAGwAdQBlACgAJABjACwAKABOAGUAdwAtAE8AYgBqAGUAYwB0ACAATQBhAG4AYQBnAGUAbQBlAG4AdAAuAEEAdQB0AG8AbQBhAHQAaQBvAG4ALgBBAHUAdABoAG8AcgBpAHoAYQB0AGkAbwBuAE0AYQBuAGEAZwBlAHIAIAAiAE0AaQBjAHIAbwBzAG8AZgB0AC4AUABvAHcAZQByAFMAaABlAGwAbAAiACkAKQB9ADsARABpAHMAYQBiAGwAZQAtAEUAeABlAGMAdQB0AGkAbwBuAFAAbwBsAGkAYwB5ADsAJgAgACcAQwA6AFwAUAByAG8AZwByAGEAbQAgAEYAaQBsAGUAcwBcAFMAeQBuAGMAdABoAGkAbgBnAFwASQBuAHMAdABhAGwAbAAtAFMAeQBuAGMAdABoAGkAbgBnAFMAZQByAHYAaQBjAGUALgBwAHMAMQAnACAALQBJAG4AcwB0AGEAbABsACAALQBTAGUAcgB2AGkAYwBlAEEAYwBjAG8AdQBuAHQAVQBzAGUAcgBOAGEAbQBlACAAIgBTAHkAbgBjAHQAaABpAG4AZwBTAGUAcgB2AGkAYwBlAEEAYwBjAHQAIgAgAC0AUwBlAHIAdgBpAGMAZQBBAGMAYwBvAHUAbgB0AEQAZQBzAGMAcgBpAHAAdABpAG8AbgAgACIAUwB5AG4AYwB0AGgAaQBuAGcAIABzAGUAcgB2AGkAYwBlACAAYQBjAGMAbwB1AG4AdAAiACAALQBTAGUAcgB2AGkAYwBlAE4AYQBtAGUAIAAiAHMAeQBuAGMAdABoAGkAbgBnACIAIAAtAFMAZQByAHYAaQBjAGUARABpAHMAcABsAGEAeQBOAGEAbQBlACAAIgBTAHkAbgBjAHQAaABpAG4AZwAgAFMAZQByAHYAaQBjAGUAIgAgAC0AUwBlAHIAdgBpAGMAZQBEAGUAcwBjAHIAaQBwAHQAaQBvAG4AIAAiAFMAeQBuAGMAdABoAGkAbgBnACAAcwBlAGMAdQByAGUAbAB5ACAAcwB5AG4AYwBoAHIAbwBuAGkAegBlAHMAIABmAGkAbABlAHMAIABiAGUAdAB3AGUAZQBuACAAdAB3AG8AIABvAHIAIABtAG8AcgBlACAAYwBvAG0AcAB1AHQAZQByAHMAIABpAG4AIAByAGUAYQBsACAAdABpAG0AZQAuACIAIAAtAFMAZQByAHYAaQBjAGUAUwB0AGEAcgB0AHUAcABUAHkAcABlACAAUwBFAFIAVgBJAEMARQBfAEQARQBMAEEAWQBFAEQAXwBBAFUAVABPAF8AUwBUAEEAUgBUACAALQBTAGUAcgB2AGkAYwBlAFMAaAB1AHQAZABvAHcAbgBUAGkAbQBlAG8AdQB0ACAAMQAwADAAMAAwADsAZQB4AGkAdAAgACQATABBAFMAVABFAFgASQBUAEMATwBEAEUA

I don't know what specifically triggered this, but it prevented the Syncthing installer from installing the Windows service. But I suspect it's either the use of a path that intimates the use of a deprecated PowerShell (PSVersion 5.1.19041.2673 executed) or more likely the switches used or the presence of Base64 encoded data. I have submitted a false positive report to BitDefender, however, I'm mentioning it here to inform you of the issue. Perhaps you have a means to rectify this on your end.

v1.24.0 is detected as a Trojan:Win32/Wacatac.B!ml virus on Windows 10 by Microsoft Defender

Summary

Install v1.27.11 will get v1.27.12 shown in the configuration page. Is it expected? Where is v1.27.12 installer released?

Steps to reproduce

1. Download and install the latest stable release from tag v1.27.11.
2. Syncing will automatically start after the installation.
3. Enter the configuration page (https://127.0.0.1:8384/), I see version v1.27.12.
4. Version v1.27.12 is currently not available from GitHub Releases.

Additional information

• microsoft/winget-pkgs#172324 (comment)
• microsoft/winget-pkgs#172324 (comment)

Bill --

The changes made in 1.20.1 are making deployment impossible for business users:

v1.19.2...main

My guess is that the total risk score has gone over some threshold due to NSSM + the new PowerShell module ([Install-SyncthingService.ps1) which does direct API calls into Windows system DLL's.

Windows Defender, Defender 365, Sophos AV, Sophos XG Firewall are all hard blocking running this on all our new customer workstations.

Suggest ditching the powershell module and NSSM for service functions and use:

https://github.com/winsw/winsw

We have had good luck with this for customer packages.

Joe

I would just like to know what is the reason for this and if there is a way to circumvent this? (So far installing an older release works.)

Windows Defender detects Trojan:Win32/Wacatac.B!ml in syncthing-1.27.2-setup.exe?

Why isn't a PGP signature for the binary delivered?
Should it be verified with the signatures and keys from the original Syncthing repository?

Getting a malware warning from Windows Defender

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 why wscript didn't work for me? But cscript 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:

systeminfo /fo csv | ConvertFrom-Csv | select OS*, System*, Hotfix* | Format-List

OS Name             : Microsoft Windows 10 Pro
OS Version          : 10.0.19045 N/A Build 19045
OS Manufacturer     : Microsoft Corporation
OS Configuration    : Member Workstation
OS Build Type       : Multiprocessor Free
System Boot Time    : 13/08/2023, 20:26:56
System Manufacturer : LENOVO
System Model        : 81YT
System Type         : x64-based PC
System Directory    : C:\WINDOWS\system32
System Locale       : en-us;English (United States)
Hotfix(s)           : 18 Hotfix(s) Installed.,[01]: KB5028946,[02]: KB5027122,[03]: KB5007401,[04]: KB5011048,[05]:
                      KB5011064,[06]: KB5012170,[07]: KB5015684,[08]: KB5029244,[09]: KB5014032,[10]: KB5016705,[11]:
                      KB5018506,[12]: KB5020372,[13]: KB5022924,[14]: KB5023794,[15]: KB5025315,[16]: KB5026879,[17]:
                      KB5028318,[18]: KB5028380

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.

According to the documentation here, Syncthing does not have an official installer for Windows and will not start automatically unless users manually create a shortcut in the Startup folder.

Should the installer create this shortcut during installation so that users will not need to create it manually?

Solution: https://www.winhelponline.com/blog/error-there-is-no-script-engine-for-file-extension-when-running-js-files/
Please see if there is a need to integration this into the installer in some way.
What made it work for me was the registry fix.

I am on a upgraded Windows 10 -> Windows 11 system so the error could be specific to my system. Leaving a note of it here for others. If this issue is not reproducible on a Windows 11 system then please close the ticket.

Describe the bug:

An error dialog that appears after installation

To Reproduce:

1. Launch the installer syncthing-1.27.2-setup.exe
2. Follow the steps
3. Select Administrative (system-wide) install mode.
4. Tick the option to launch configuration page after completing installation.
5. Click finish

Expected behavior:

The installer should open the browser and redirect the user to the configuration page (which is on https://127.0.0.1:8384 by default)

Actual behavior:

The installer failed to open the browser and instead showed an error dialog.

Screenshots:

Additional context:

I am using Windows 10 LTSC.

Running syncthing 1.27.4, I cannot uninstall: after starting it up, uninstaller keeps hanging on 0%

Task Manager shows nothings happening either

The current EXE version is v1.20.1 in the meantime we have Syncthing v1.21.0 and I want to ask about a update.

https://www.virustotal.com/gui/file/f37cbbdd971b8ec6d26becb4a0fbfdd5c553d08f84ee6a849dd9bd6439972bdb

Flagged on Virus Total

syncthing-1.27.10-setup.exe : PUA:Win32/Packunwan

Windows Defender marked this exe.

Not sure if this has been asked before, but would it be possible to get MSI installers in the future for use in remote tools, such as Intune?

Bill --

First let me congratulate you on an EXTREMELY well done installer for Syncthing. I've been writing software installers for years for our product and was very impressed with your work. I hope the SyncThing team considers adding your installer to their Windows releases.

Now, getting to my suggestion:

I'm a security professional and noticed you are installing the service under the Windows Local Service account. Given that Local Service is also used by dozens of other services in Windows including several security sensitive services:

I would suggest allowing the user (during an ALL USERS install) to select a non-privileged service account of their choice and using it as the login for the service as well as permissions on C:\Program Files\SyncThing directory (For Auto Update). Knowing the service account name the user can manually add the service account to the permissions on the folders they sync. Perhaps as simple as a checkbox "Custom Service Account" during install (if not checked use Local Service) and they simply fill in the Service Account Name and Password. Optionally a checkbox on the Password field could be "Generate Random Password" which would grey out the Password field. You could use a random Password generator or simply execute net user /random:36 and capture the output) to use when you create the NSSM service.

You could optionally create the service account as well locking it down with no group memberships (users/guests), OR simply require the user to have already created the service account using compmgmt..msc first.

Make sure to mirror the new options on the silent install command line arguments so us Admins can deploy your installer with our own deployment tools with all options specified.

Thank You for a great IWindows nstaller for SyncThing!

Bill -- Is there a changelog for your new 19.1 release? Can't find one. Thanks.

Howdy!

First off, this installer is great! It makes using syncthing significantly easier! So thank you!

I used the admin installation option, but I have a folder in my documents folder that I would like to add to my sync chain. However, the Service account doesn't have access to my libraries for my User account. How do I let it access these folders? I apologize if this isn't the proper place to ask.

Hello,

I've installed this Syncthing app to windows. First I try to sync a Windows Folder with my Android Phone (Galaxy Z Flip 5) in lan. The sync is very very slow (3 Ko/s). Second i try to sync a folder with my Android Phone to Rsync Docker in Lan, the sync was quick. Folder sync Android phone to Windows is not working (no speed).
I disable relay and i try to enter manualy the IP adress device's to my W11 computer but it was also slow.
I think the problem is with my Syncthing W11 install.
The log don't show anormal logs.

Can you help me to resolve this ?
TY

Hi Bill,

Merely wish to say you've done an excellent job with this, especially after the demise of syncthingrazor. I've successfully installed on 2 instances (Windows 11 x2) with no issue. The only exception was a request for a windows firewall additional rule on one install, while the other didn't make the same request (both were clean Win11 installs, latest version as of Feb 2024).

The only thing lacking for semi-computer literate users would be some method of notifying the user in the event of a failure. Of course, the system is so simple (relatively speaking), there's little to go wrong!

All the best,

Chris

Is it normal for the client sending data to send at 15 Mbps (the maximum upload rate at that location) for a few seconds, then stop for a few seconds? Meanwhile, the receiving client always receives data at 3-4 Mbps without interruptions. Is there a way to speed this up?

https://www.hybrid-analysis.com/sample/ccdb410bbffe6c3f560366f7e0df131c24994394ae83ac4ce53a8ed76bcc8c83

https://www.virustotal.com/gui/file/ccdb410bbffe6c3f560366f7e0df131c24994394ae83ac4ce53a8ed76bcc8c83