My problem: Thunderbird can’t receive or send messages anymore. I think it has been 2 days.
My Comodo situation: the ‘About’ says I have Comodo Firewall version 7.0.317799.4142 (on Windows 7 64 bits). I think Comodo was updated, probably yesterday, as the alerts seem to be more detailed than they used to be (the red part is new):
It also says several of my apps are “not recognized”, when it used to know them…
I have ‘Check for program updates every 7 days’ checked, but ‘Automatically download program updates’ unchecked. I’m not sure what version I was running prior to this, although from my personal log, I can tell you I had updated Comodo on June 24th, and before that, on April 7th.
- did Comodo really self-update without asking me anything? Did I do something wrong? How can I make sure this doesn’t happen again?
- where can I find more details about the update (exact time it happened, previous version) to try and determine if there is a link to my Thunderbird issue?
- how else can I determine if there is a link between my Thunderbird issue and Comodo?
- and of course: how do I fix my Thunderbird issue?
Any help will be greatly appreciatly!
First things first, the Thunderbird issue is solved, it had indeed to do with Comodo: going to Advanced settings / Firewall / Application rules, I saw that there was no entry for Thunderbird (or Firefox or Chrome, actually, but those two seem to be working perfectly well).
So I added a new entry and ticked Use ruleset / Email client (and added a TCP/Out rule to have images displayed in messages).
Also. I had completely missed the Tasks button at the top of the window since the upgrade! I was wondering where a whole lot of features had gone… well, found them now! Oops. So I was able to view the log.
General tasks / View Logs says “Last update: 24/06/2014”; that’s what I thought! So it’s still weird that the program has started behaving differently over the past week. Could it have been corrupted somehow??
I found the following entries in the log, which are due to Windows Update Agent 7.6.7600.320
2014-08-01 14:58:17 C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe Modify File C:\Windows\WindowsUpdate.log
2014-08-01 14:59:26 C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe Modify Key HKLM\Software\Microsoft\SystemCertificates\root
2014-08-01 14:59:29 C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe Modify File C:\Windows\WindowsUpdate.log
2014-08-01 15:00:14 C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe Modify Key HKLM\Software\Microsoft\SystemCertificates\root
2014-08-01 14:57:41 String Added User Defense+ Trusted File C:\Windows\SoftwareDistribution\SelfUpdate\Packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320\amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.6.7600.320_tk-tm_b7a812b5be47ad80\wuaueng.dll.mui
+ 151 other lines that closely resemble it
I have my Windows Update service set to ‘check for updates but let me choose whether to download and install them’, not automatic updates, but out of the blue the other day, Comodo warned me that a WuSetupV.exe file was trying to install something. I didn’t allow it to proceed, and now, Windows Update reports a failure on patch 7.6.7600.320. Sounds like I’m not the only one who saw this installed - well, just an attempt in my case - behind their backs.
Anyway, even if it didn’t install, it looks like it reset part of my Comodo config.
Is there any simple way I can restore my previous parameters? And/or check if I am currently vulnerable? :-\