I’m not sure what happened, for some reason my Comodo firewall didn’t auto start at startup. Up until today, it had been starting, it’s even in startup area within msconfig. Is there a reason this could of happened anyone may know of or is it just one of those things? I couldn’t find anything with Comodo to make sure it’s set to auto start, that being said should I reinstall it?
both cmdagent & cpf.exe are not started after reboot, until of course I start them manually. I read the post between you & beck, I made sure it was enabled (checked) restarted went into msconfig and it was disabled again. Does something need to be added or edited in the registry?
If it comes to that then yes. However, the root problem still exists: something is removing it in the first place and you must find out. It’s either malware or anti-malware that’s doing it. Usually anti-spyware has options that check for registry changes in ways that you don’t want.
The weird thing is and I probably should of mentioned this before, my NOD32 started doing the same thing at the same time. Should I find a registry checker, malware or anti-malware scanner? I was sure NOD32 checked for all that, I thought.
Other than Comodo & NOD32 having these issues, everything else runs well on the PC. I did notice when I went into msconfig under services cmdagent was set to start, was unchecked in startup and did not show as running after a reboot.
every time I enable it (check the box) within mscofig and then reboots, it starts up disabled. When I go to services.msc it shows Comodo Application Agent as set to run at startup and running without firewall. Were you saying cpf.exe & cmdagent.exe are also suppose to be there.
I’m not sure at all what to be looking for in event viewer , what should I look for.
I don’t like system restore, and I just as I’m writing re-installed Comodo, but not in safe mode. I wasn’t aware you could even do that, I assume you’d have to be in safe mode to do it (:CLP)? Anyway, the re-installation changed nothing, it’s still doing the exact same thing, I even installed NOD32 and same thing. At this point, my paranoia, is getting the better of me.
Safe Mode because it’s safe :D. This is to avoid potential “critters” from infesting CFP installation stage. But if your CFP was working fine before until recently, it’s obvious to me (now :-[) that you did not have a corrupt CFP installation and something in the midst of the whole process got to it, affecting your startup items on Nod32 as well as CFP. Why not upload a HijackThis log (as a text file) here so that we can see if there are other things loading at the same time?
The good news is your HJT log is short and looks ok to me. However, I’m not expert enough to fully know some of the files you have and how it might affect your startup items, namely APC PowerChute: I just wonder what exactly you see if you right-click on the APC UPS Status icon properties in your Windows Startup menu.
If anyone knows anything feel free to jump in anytime because I’m nearly out of ideas :-\