FileZilla Forums

Hi,

I downgraded to filezilla-3-35-2 due to a bug in 3.37.3 (unable to drag and drop in the local site panel), and in the settings I set checking for updates to never.

Despite that, every time I close the file manager, I have an annoying popup reminding me of the new version and about the pro version.

How can I disable it?

Please update to the most recent version, we cannot support outdated versions.

The most recent version has a bug that prevents me to use it.

Could you then just tell we what address Filezilla uses to check for a new version? If I set something like filezillachecker.com to 0.0.0.0 on my host file, that will solve my problem until you solve yours!

Let's talk about bug in the most recent version. Please describe what the problem is.

Most likely the "MS fudged Drag & Drop in 1803" problem.

Bug is described here:

https://trac.filezilla-project.org/ticket/11761#no3

But I still would like the "never update" to work. That is a bug is the last version too.

There is a difference between checking for updates and displaying known updates.

Ok, so we're back about my question about the name of the server that allows older versions to know that there is a new one.

If you give it to me, I'll disable it in my hosts file, and be happy.

Or I can use a process hacker and see all the connections that Filezilla does when it starts. But why make me waste my time?

You will find none, as FileZilla will not check for updates if the check has been set to "Never". But, as botg said, there is a difference between "checking" and "offering known updates". FileZilla just offers the update it checked for and stored in its configuration file before you disabled the check. To stop that, you would need to eradicate that information from the config file.

You need to do it yourself, without our help, since old versions are not supported.

It's hard to remain civil when you get this kind of "support", but I will and use reasonable arguments in this complaint rather than just yell like I strongly feel to do.

I'm sure that the configuration files have not changed on this minor upgrade, so it would have been very easy for you to give me instructions for the current release that would also have worked with the one I have to use because the new one is bugged.

Also, when you release a defective release, the LEAST (oops, sorry, yelling just a little) you can do until you solve the problem is support the last working one. I cannot think of a single vendor on the Internet that would say 'use the release that does not work, and then we will help you'. May be Microsoft can show that kind of disregard to their users needs, may be...

And in addition, how do such a cryptic comment such as "There is a difference between checking for updates and displaying known updates" can provide any help? It's like you think you customers need to download the sources and study them a few months to understand what you say.

Anyway, I did solve this problem by my own. I got rid of this annoying popup.

All I can say is that I got zero support for a free product. I guess you get what you pay for!

Until this issue can be fixed, simply use Explorer to move/copy local files.

Downgrading is not and will never be a supported use-case. We roll forward.

Again, missing the point. Explaining what to do would work for any release. Your refusal to give a very simple description of the way to solve my problem (erasing setup files in the download folder) is incomprehensible, it borders on fanaticism.
I did downgrade, and don't intend to waste time with an explorer window, like it or not.

You need to update to the most recent version, 3.37.4 as of writing this.

2020-08-05-Win 10 Pro / Filezilla 3.16.x

<removed insecure advise>

You need to update to the most recent version, old versions are not supported.