Full Removal of Comodo Firewall Pro 3 with SafeSurf Toolbar (If Regular Uninstall Method Fails)

[Guest]

[eKatherine]

I am just amazed. Yesterday Comodo locked up on me, and I uninstalled, downloaded the new version, and reinstalled. This morning the new version was not allowing any internet connection at all, although what few settings I was allowed to see appeared to be correct. I ended up uninstalling in order to get back online, but windows thinks it's still running. I've got no firewall now (time to shop for another, I guess). There is absolutely no way I follow the instructions in the original post. None at all. I would never have installed in the first place if I'd known that using it required such a high level of technical expertise.

[USSS]

Welcome to the forum, eKatherine.

We're sorry to hear about the issue you had with removing and reinstalling CFP.

Please try the batch file created by Ragwing.  There's a very good chance that this file will remove the remnants of the previous installation and allow you to install the latest version of CFP.

As you pointed out, the list of instructions for a comprehensive removal is daunting, and we hope the uninstaller in future editions of CFP will incorporate these steps so that users will not have to set aside a couple of hours just to remove a firewall.

Let us know if you try the script files and whether you succeeded in reinstalling CFP.  Your feedback on this would be very useful to the programmers and developers.

[Yuriy]

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CMDAGENT *
    v.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CMDGUARD *
   w.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CMDHLP *
    x.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_INSPECT *
    y.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_CMDAGENT *
    z.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_CMDGUARD *
  aa.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_CMDHLP *
  bb.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_INSPECT *
  cc.   HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_CMDAGENT *
  dd.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_CMDGUARD *
  ee.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_CMDHLP *
   ff.   HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_INSPECT *
  gg.  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_CMDAGENT *
  hh.  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_CMDGUARD *
    ii.  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_CMDHLP *
   jj.   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_INSPECT *

Hi Stephen,
I noticed that on different systems legacy keys may be located under different ControlSets, e. g.:
- CurrentControlSet + ControlSet004 + ControlSet005; under ControlSet001-003 no entries related to Comodo;
- CurrentControlSet + ControlSet001 + ControlSet002;

[USSS]

You are correct. 

The appearance of those LEGACY keys that are specific to Comodo will vary from system to system, as the enumeration of ControlSets will generally range between 001 and 003.  However, if a user plans to reinstall CFP, those LEGACY keys will be recreated and will overwrite any existing entries.  Therefore, removing them prior to reinstallation isn't necessary.

Still, your script is useful to users that may be experiencing other issues related to those keys.

[Yuriy]

... if a user plans to reinstall CFP, those LEGACY keys will be recreated and will overwrite any existing entries.  Therefore, removing them prior to reinstallation isn't necessary.

Thanks, didn't know that.

[Ragwing]

Hi Stephen,
I noticed that on different systems legacy keys may be located under different ControlSets, e. g.:
- CurrentControlSet + ControlSet004 + ControlSet005; under ControlSet001-003 no entries related to Comodo;
- CurrentControlSet + ControlSet001 + ControlSet002;

It's used for Last known good configuration, so therefore people might have more or less. I myself have CurrentControlSet, Controlset001 and ControlSet002.

Cheers,
Ragwing

[Yuriy]

It's used for Last known good configuration, so therefore people might have more or less. I myself have CurrentControlSet, Controlset001 and ControlSet002.

Thanks for that... And i have CurrentControlSet, Controlset001-005.

[Searinox]

I am having serious issues. I uninstalled CFP and ran your cleaner utility but I am left with two "Comodo Firewall Miniport" devices that I CANNOT uninstall. Help please!

[USSS]

This is the first I've heard of "Comodo Firewall Miniport" appearing in Device Manager.  I looked through mine and found no such instances of this.

Regardless, have you tried right-clicking on these "miniports" and selecting "Uninstall"?

Failing that, you might have to do some registry edits to get rid of them, and even then, you may need to elevate the permissions on those registry keys (if they do, in fact, exist) to delete them.

Post back...this is a weird one.

[Dennis2]

This is the first I've heard of "Comodo Firewall Miniport" appearing in Device Manager.  I looked through mine and found no such instances of this.

Regardless, have you tried right-clicking on these "miniports" and selecting "Uninstall"?

Failing that, you might have to do some registry edits to get rid of them, and even then, you may need to elevate the permissions on those registry keys (if they do, in fact, exist) to delete them.

Post back...this is a weird one.

You have to tick Show hidden devices in Device Manager before you can see comodo miniports.
Dennis

[bonas]

Many thanks!!!!

[Yuriy]

This is the first I've heard of "Comodo Firewall Miniport" appearing in Device Manager.  I looked through mine and found no such instances of this.

I have been told these are present on Vista. I guess you are using XP and that's why nothing is listed in Device Manager.

[USSS]

You have to tick Show hidden devices in Device Manager before you can see comodo miniports.
Dennis

I know...I did that the first time, and there were no entries (I use Windows XP Pro).

It's a moot point, though, as Yuriy points out above that these entries likely appear only in Vista's Device Manager.

[Searinox]

I didn't have to show any hidden devices of any sort. CFP miniport was UNDER NETWORK ADAPTERS. Also... it didn't install WHEN I installed CFP. It happened after the restart. As the OS booted a device install balloon popped up saying it's installing CFP Miniport #4. The device was successfully installed but the firewall remained on "not functioning properly" message until I did another reboot. CFP kept freezing up my desktop moments after boot so I uninstalled it ASAP. Following that I was left with a Miniport under network adapters in device manager. Rightclicking and selecting uninstall, no matter how many times, refreshes the device list but leaves the miniport right where it is. When I go to its properties it says that some software related to the device is missing.

[Dennis2]

I know...I did that the first time, and there were no entries (I use Windows XP Pro).

It's a moot point, though, as Yuriy points out above that these entries likely appear only in Vista's Device Manager.

Oops sorry 
That will teach me to look properly just WAN miniports in XP none for comodo.
Dennis

[Tags:]