There is clearly a bug in the Comodo v3 (v3.0.13.268 in my case) install process.
As noted in this ticket, as well as several others (look up folks seeing MSIEXEC.EXE kicking off asking for the Dell Resource CD, or their HP drivers, etc.) including this one:
https://forums.comodo.com/empty-t15445.0.html
the problem that is occurring is that after installing Comodo v3, we are all getting some form of the msiexec.exe program kicking off when we login, and often at other times as well. In my case, the stupid thing kicks off 2x at login attempting to run the pcAnywhere 10.5 installer (which isn’t there). Then another 2x if I run Windows Update (translation: run IE and go someplace that triggers the msiexec process again somehow).
This is NOT a problem with my pcAnywhere install, which hasn’t changed in YEARS.
It is NOT a problem with people’s HP drivers.
It is NOT a problem with folks needing to reinstall their Dell Resource CD.
Even though certain parties who respond to many posts seem to indicate otherwise, they’re chasing their tails.
The problem is that the Comodo v3 installer is mucking with the Registry somewhere rather unique (and I’ll be darned if I can find it, as it’s not in the usual locations) that’s causing this to kick off. I believe Explorer, Internet Explorer, and possibly other apps may trigger this, but I can’t for the life of me find the ■■■■■■.
I went through the process of uninstalling Comodo v3, rebooting, and sure enough, the problem was gone. I had backed up my configuration before uninstalling, so I figured I could always get back to where I was. WARNING: This feature sucks and does NOT backup your entire config, so you have been warned. I’ll have to post that in another ticket, as I’m now stuck rebuilding my ruleset once again. sigh
After uninstalling/rebooting, I once again did a clean install of Comodo v3, rebooted when asked, and voila! The problem is back. So let’s just stop with the guessing game. The problem is Comodo v3, pure and simple. If you uninstall it and the problem goes away, and then reinstall and the problem’s back, that’s a glitch in the installation process. So please, those folks who are suggesting that users should go find their installation CD or re-run the installer of whatever app is being triggered, stop doing Comodo, yourselves, or the user community this disservice. That’s not a solution. That’s hearing a knocking sound in the car engine and throwing a monkey wrench at it in an attempt to “fix” the problem, insteading of going after the real root cause.
The real solution is to let the developers at Comodo know that there is a real bug in the installer, so they can kill the problem at its root. There seem to be several folks here in the forums technical enough to dig around a bit, but most users aren’t going to do that. They’re going to have this weird installer thing keep kicking off, get fed up, uninstall Comodo, see the problem has stopped, and head somewhere else. That’s a shame. And it’s avoidable.
Let’s find out what the hell this installer is doing exactly and fix that, shall we? Comodo Firewall is a pretty decent product with a lot of potential. It’s RAM footprint is nice considering what it does, and it has a ton of features. Unfortunately, as often happens in the development world, it seems they were more concerned with “kitchen sink” programming (throwing in every feature including the kitchen sink) than creating a stable, reliable program whose feature set might be smaller but worked well. Featuritis/bloat is something software companies need to be constantly on guard against.
And don’t get me started on the “noise” in the UI. Yes, Comodo does a great job as a firewall and now adding malware protection. But good lord, could you make it any more confusing? This program is fine for those of us who live on computers, but this sure doesn’t pass the “grandma” test.
So summing up, anyone finding this thread because they’re system is kicking up some kind of installer every time they login or run Windows Update (i.e., msiexec.exe), note you are not alone, and the problem is with Comodo.
Here’s hoping they find the problem and resolve it.