Hello!

Is it possible to disable auto update functionality for All Users? Now it seems it works on a peruser level.
I found this suggestion in another topic, but it does not work.

[HKEY_LOCAL_MACHINE\SOFTWARE\Martin Prikryl\WinSCP 2]
"DefaultUpdatesPeriod"=dword:00000000

When I configure this setting autoupdate is still available for users.

thanks!

The DefaultUpdatesPeriod is the default.
If the user already has own settings, it overrides the default.

What's your use case?

hi, and thanks for your feedback.

Our use case would look like this:

1. We would need that the "Updates" feature/functionality in your software could be completely disabled CENTRALLY (by Administrators), so that the users will not have the ability to modify Update setting.
2. The users shall not even access the "Updates" menu entry in the Configuration.

Simply put we do not want the program to look for updates, and we do not want the users to perform manual update checks or modify specific central update settings.

thank you!

The WinSCP application have the updates disabled by default actually.

It's the WinSCP installer that enables the updates by setting the DefaultUpdatesPeriod, if you keep the default "Enable automatic updates ..." installation task. So just turn the task off and the updates will be disabled too. This obviously won't affect the existing users anymore.

You cannot have WinSCP hide the Check for Updates command.
This request has been added to the tracker:
https://winscp.net/tracker/show_bug.cgi?id=1413

You can block the update check URL on your firewall though.

hi, and thanks for your quick feedback!

we are looking forward to the feature be added to your software!

greetz

hi again!

I just realized you started this Feature request as Medium priority. Can I ask that usually how much time does it take to implement a function in the software with Mid prio?

thank you so much!

Depends on how many people asks for this.

My case: On a desktop/server computer I've setup an automated script using Powershell and .NET dll. Script run well until a user/admin login for the first time and sees a prompt to ask to check for new update. Executable updates but .NET dll doesn't. Either I have to keep a copy of matching executable and overwrite at the beginning of script or manually download .NET dll from site.

That's the right approach. You should not rely on the installed version of WinSCP.