Spróbuj skontaktować się z dostawcą firewalla ;) (sądzę, że jesteś polakiem, po tytule)

Try to contact your firewall provider

Pozdrawiam, Best regards.

Thank you. But while the firewall, itself, might be the problem, I've been using it with every version of FF for 7+ years without any problems - until now, FF 35.0.1.

So let's say, for the moment, that the firewall is not the problem. What could cause FF 35.0.1 (versus all other prior versions of FF) to somehow be _perceived_ as changing itself over and over so that its binaries appear different? For example, does 35.0.1 incorporate plugins differently than does prior versions of FF?

Or does v 35.0.1 somehow change its binaries as certain processes take place, whereas before it kept any such changes external to its core binaries?

As far as I know, my firewall simply looks at its fingerprint of the binaries or any program on its list and if those binaries change it throws up an exception.

I have my firewall set to ask permission every time a new/changed program wants net access.

On the other hand, maybe most people have their firewalls set to allow any "known programs" to access the net without asking; if so, that might explain why others are not reporting this problem.

There are other things that need your attention.

Your System Details List shows multiple Flash plugins.

• Shockwave Flash 11.2 r202
• Shockwave Flash 16.0 r0

You can find the installation path of all plugins on the about:plugins page.

• http://kb.mozillazine.org/Issues_related_to_plugins#Identifying_installed_plugins

You can check the Flash player installation folder for multiple Flash player plugins and remove older version(s) of the plugin (NPSWF32) and possibly (re)install the latest Flash player.

• (32 bit Windows) C:\Windows\System32\Macromed\Flash\
• (64 bit Windows) C:\Windows\SysWOW64\Macromed\Flash\

You would have to contact your firewall's website for support if you have a problem with their software.

Thanks for the note about Flash. As it happens, they are both marked to require permission to activate. Still, thanks for that. I have now disabled the old one and will figure out how to uninstall it, if that's possible.

But again, as for my firewall, I am now using FF 35.0 without problems. It's only when I installed 35.0.1 that I did have problems -- with the firewall telling me that the binaries changed over and over and over with seconds, and then the same 30 seconds later, and then again...

So, yes, the problem may be a firewall problem. But it does seem odd (at best) that this has never been a problem with the countless iterations of updates of FF over many years -- until just now with 35.0.1.

IOW, I have a stable Win7 machine, it's working fine, and then I make one change - update from 35.0 to to 35.0.1 -- and bad things happen. In such cases, I usually suspect the one thing that changed, not the things that are constants.

I updated to 35.0.1., my firewall recognized its binaries had changed. So, I was asked if it was OK to let this "new" ap access the net. I clicked "Yes", and I made that permission permanent. But then a few seconds later the firewall said the binaries had changed from what they had been just seconds earlier. I cannot understand why a firewall that has never done this before -- that has never before failed to recognize an ap that had already been approved -- would mistakenly claim (over and over) that the binaries of this one app (35.0.1) were repeatedly changing. True, maybe it is the firewall, but I have years of reasons to believe that it's not the firewall -- it's 35.0.1

I might ask if you use a firewall and do you have it set so you have to give individual permission to each/every new (or changed) ap?

So, if you have it set to let "recognized applications" have access without your intervention, then maybe the same thing is happening to you (i.e., the binaries of FF 35.0.1 keep changing in background) but you just don't know it because your firewall is handling it automatically.

Again, thanks.