For some reason, whenever the SyncoveryVSService runs in the background, my internet connection is significantly affected (slower speeds, higher latency). Consequently, I have set the service's startup type to Manual and only start it when necessary.
However, every time I update Syncovery, the update process resets the SyncoveryVSService startup type to Automatic and automatically launches the service in the background.
If possible, please adjust the update process so that it does not reset the SyncoveryVSService startup type to Automatic or automatically start the service (if it was previously stopped).
Do not re-override the startup type of the SyncoveryVSService service during updates
Re: Do not re-override the startup type of the SyncoveryVSService service during updates
Hello,
that's interesting, because this service does not do anything. It just sits there and wait if Syncovery has a job for it.
The only purpose for this service is to create a volume shadow if there is a Syncovery job that needs to copy locked files, and Syncovery is not running "As Administrator". If it runs as admin, it can create the volume shadow itself and does not need the VSS service.
If creating volume shadows causes problems, you can turn it off in the profile under Files->File Access. I recommend using volume shadowing sparingly and not multiple times per day, and certainly not in any real-time jobs.
If you don't need the VSS service at all, I recommend running the Setup from our web site manually once and deselecting it from the features list. You can also delete the exe file from the program folder.
that's interesting, because this service does not do anything. It just sits there and wait if Syncovery has a job for it.
The only purpose for this service is to create a volume shadow if there is a Syncovery job that needs to copy locked files, and Syncovery is not running "As Administrator". If it runs as admin, it can create the volume shadow itself and does not need the VSS service.
If creating volume shadows causes problems, you can turn it off in the profile under Files->File Access. I recommend using volume shadowing sparingly and not multiple times per day, and certainly not in any real-time jobs.
If you don't need the VSS service at all, I recommend running the Setup from our web site manually once and deselecting it from the features list. You can also delete the exe file from the program folder.
Re: Do not re-override the startup type of the SyncoveryVSService service during updates
Yes, but it really affects my internet quality, yet there is no way to determine the cause.tobias wrote: Tue Aug 25, 2026 10:04 am Hello,
that's interesting, because this service does not do anything. It just sits there and wait if Syncovery has a job for it.
Oh, I use the built-in Administrator account, so Syncovery runs with Administrator privileges by default.The only purpose for this service is to create a volume shadow if there is a Syncovery job that needs to copy locked files, and Syncovery is not running "As Administrator". If it runs as admin, it can create the volume shadow itself and does not need the VSS service.
In that case, you could change the startup type of the SyncoveryVSService service to Manual. Then, you could simply start the service when needed and stop it once the task is complete.If creating volume shadows causes problems, you can turn it off in the profile under Files->File Access. I recommend using volume shadowing sparingly and not multiple times per day, and certainly not in any real-time jobs.
I think I'll reinstall Syncovery from the installation file.If you don't need the VSS service at all, I recommend running the Setup from our web site manually once and deselecting it from the features list. You can also delete the exe file from the program folder.
Re: Do not re-override the startup type of the SyncoveryVSService service during updates
Hello,
I will make sure that the next Syncovery setups will preserve the VSS service status.
I cannot use "Manual" for most users because the Syncovery runs under UAC most of the time, in attended mode, and therefore cannot start the service when needed.
I will make sure that the next Syncovery setups will preserve the VSS service status.
I cannot use "Manual" for most users because the Syncovery runs under UAC most of the time, in attended mode, and therefore cannot start the service when needed.