Upgraded to Thunderbird 52.2.1.6382. Now my ESET firewall is blocking it.
My Thunderbird just autoupdated to 52.2.1.6382. It appears to be working OK, except my ESET firewall started blocking it because the path seemingly changed. Strangely, the path shown in the warning is C:\Program Files (x86)\Mozilla Thunderbird\updated\thunderbird.exe.
I've tried launching TB as Administrator directly from C:\Program Files (x86)\Mozilla Thunderbird\thunderbird.exe and the same thing happens.
When I look, there is no "updated" folder. I don't want to change the firewall rule because I don't understand what's happening here. I'm running Windows 7 (x64), ESET smart security ver8
தீர்வு தேர்ந்தெடுக்கப்பட்டது
Problem solved. I was not able to find the exact cause or where the fault lay. The only thing I could find was the path entry in HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\LowRegistry\Audio\PolicyConfig\PropertyStore. Not much help. I rebooted and found that the problem solved itself. Maybe the ESET firewall needed a clearing out.
Read this answer in context 👍 0All Replies (4)
C:\Program Files (x86)\Mozilla Thunderbird\updated\thunderbird.exe is the TEMPORARY location of the updated program. It sounds like you haven't fully updated.
Yes, I assumed it's the temporary location, but that folder isn't there any more. Since the executable is in the C:\Program Files (x86)\Mozilla Thunderbird, I don't understand why the update path persists.
I suppose I'll also try rummaging through the registry or re-installing Thunderbird and see what happens.
Forget the registry
Start Windows in safe mode. Delete the directory "Mozilla Thunderbird" in %ProgramFiles(x86)% Restart Windows Redownload and reinstall Thunderbird from http://getthunderbird.com/
தீர்வு தேர்ந்தெடுக்கப்பட்டது
Problem solved. I was not able to find the exact cause or where the fault lay. The only thing I could find was the path entry in HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\LowRegistry\Audio\PolicyConfig\PropertyStore. Not much help. I rebooted and found that the problem solved itself. Maybe the ESET firewall needed a clearing out.