Diagnostic utility finds a problem..

[Guest]

[Vettetech]

Comodo showing up in the Security Center is normal. Alot of security programs have this problem with Windows. You need to rebuilt the repository folder. Go to run and type "services.msc". Then find the WMI (Windows Management Instrumentation) and stop it. Then migrate to C\Windows\System32\Wbem and delete the repository folder and reboot.

[Tarq57]

Thanks, Vettetech, I remember that trick now. Still, don't think it's associated with the original problem.
What do you think about those legacy driver entries in the registry? Worth a crack at deleting?

[Soyabeaner]

The comprehensive guide to remove CFP3 states legacy keys are harmless and are created well after a software is installed.  Instead of following those step-by-step instructions, why not just scroll to the bottom of the first post and execute the .bat file?  It does the work for you.  Yes, they will return after installing and they all legacy keys never give full control.  Dunno why, but I would delete them if the script doesn't cover them and then clean reinstall CFP with disabled security programs.

[Tarq57]

Well, here's where I'm at. Uninstalled it, used the Revo uninstaller, changed the permissions/deleted all Legacy keys, (having already uninstalled Boclean and CMF), using regedit removed everything Comodo, looked in Device Manager (hidden entries)- nothing present, removed the wbem repository from System 32 having disabled WMI, rebooted, downloaded and ran the .bat file.
In other words, pretty much everything in the detailed instructions in that awesome forum post.
Just ran with the Windows firewall for a time, but it's a bit like a "space saver" spare tyre, not really good for serious security. Tried Onliine Armour firewall, again, (but briefly; it has almost frozen my computer in the past, and this time was no exception. Have no idea why. But I used the Revo uininstaller to remove it.)
Reinstalled the latest CFP. Seems to work ok.
Ran the Diagnostic Test. Same result. Totally flummoxed. It once showed the installation as working perfectly, and now does not, no matter what. Can't work out what's changed.

[Vettetech]

Why run the diag test if Comodo is working. Or are you getting a message stating that Comodo isnt working properly?

[Tarq57]

Vettetech, purely to see if the diagnostic utility does indeed work (as it used to.)
No errors appear to have been reported. The firewall itself appears to work correctly. But any aspect of a software, especially security software, that mysteriously stops working correctly nags at me.
I originally ran it not long after the first install, just to make sure everything was OK - and it reported everything was. Now it doesn't. So either something actually is wrong, or the utility has a glitch. I suspect the latter.
I would like to know why, but suspect it may be too hard to find out.
(But, hey! Reading through 13 pages of uninstall information has been somewhat educational...)

[Soyabeaner]

So to clarify: CFP still reports/finds errors that it can't fix.  I know what you mean.  Even if it's just a reporting error, peace of mind is at stake .

[Tarq57]

Soyabeaner, that's exactly it.

[Soyabeaner]

Hmm... does remind me of a similar situation in the past when I installed an update patch (rather than a full setup executuable) on top of an existing CFP version (I had no other security programs and I'm a system clean freak, so I barely had anything running other than M$ processes).  I did everything as I should, and when I rebooted, out of curiosity, I ran the diagnostics wizard with the same result as you.  I later on uninstalled and installed CFP 3 (probably a different version, but it was a while ago so my memory is fuzzy) without this error ever since.

Edit: Not exactly the same results as you as my diagnostics wizard did manage to repair it.  Fuzzy memory!

[Tarq57]

I like to have unnecessary things not load at startup, too. Quicktime, Keyboard utilities, all those softwares that want to run at startup, even though they might only be used once a day...
It's one of the reasons I had a look at Blackvipers site. Probably went a bit overboard. Most of my services are set to automatic, now.
I'd definitely be interested in finding out what's causing that error. Maybe I'll have to wait for a new version of CFP...
I wish they were still developing 2.4. That's a pretty problem free application, apart from occasionally forgetting some of the rules.

[Soyabeaner]

I wish they were still developing 2.4. That's a pretty problem free application, apart from occasionally forgetting some of the rules.

That really depends on the system running it.  I was one of the those who experienced high CPU usage due to the monitor dll injections option.  But that's another story .

I re-checked your first txt attachment.  Even though you do have guard32.dll in C:\Windows\System32 folder, the report shows that it's not loading or currently in use...In C:\Program Files\COMODO\Firewall\Repair there should also be a copye of this file.  Can you check?

[Tarq57]

Yes, guard32.dll exists in that folder.

[Soyabeaner]

It's one of the reasons I had a look at Blackvipers site. Probably went a bit overboard. Most of my services are set to automatic, now.

That shouldn't be necessary.  CFP doesn't rely on any particular Windows services AFAIK. I myself usually have only 15 services in total running.

If guard32.dll is supposedly the Defense+ driver, just to make sure, you have been receiving the Defense+ alerts?

Have you tried Start > Run > sfc /scannow?

[Tarq57]

If guard32.dll is supposedly the Defense+ driver, just to make sure, you have been receiving the Defense+ alerts?

Yes. (Even though the recent reinstall selected "firewall only", defence is running, and occasionally alerts to unknown processes.

[Soyabeaner]

I see you opted for the Firewall only during installation.  Now that I don't know since I've never selected that one.  I wonder if someone else with the same setup can reproduce the issue   Shouldn't matter since you said the first time you installed CFP 3, assuming it was also Firewall only, this error didn't exist.

I'm wondering the exact timing when you first noticed the error in relation to when XP SP3 was installed.  There have been some reports of SP3 causing issues with CFP3.

[Tags:]