Welcome, Guest. Please login or register.
December 29, 2009, 03:34:02 AM

Login with username, password and session length

345911 Posts
38199 Topics
86774 Members

Latest Member: Mathieu76

Search:     Advanced search | Tag Cloud
+  Welcome to the Comodo Forum
|-+  Archive Boards
| |-+  Comodo Firewall
| | |-+  Help for v3
| | | |-+  Full Removal of Comodo Firewall Pro 3 with SafeSurf Toolbar (If Regular Uninstall Method Fails)
« previous next »
Pages: 1 ... 6 7 [8] 9 10 ... 20 Go Down Print
Author Topic: Full Removal of Comodo Firewall Pro 3 with SafeSurf Toolbar (If Regular Uninstall Method Fails)  (Read 168043 times)
USSS
Comodo's Hero
*****
Offline Offline

Posts: 298


« Reply #105 on: March 14, 2008, 07:19:11 PM »

Yes, run the batch file first. 

If you have a good registry cleaner available, it won't hurt to run it after executing the batch file.  Run Windows' Disk Cleanup utility as well.  Then reboot and proceed as below.

If you are running Windows XP, create a System Restore point.  Then disable your Internet connection.  Shut down or disable your anti-virus.  Disable all unnecessary processes in Task Manager.

Then attempt to install the latest version of CFP. 
« Last Edit: March 14, 2008, 07:20:56 PM by USSS » Logged

Tip of the Day: "Old telephone directories make ideal personal address books. Simply cross out the names of all the people that you do not know."

ThinkPad T43 and Micron Millennia Desktop: Kaspersky Anti-Virus 7.0.1.325 and CFP 3.0.25.378 running on Windows XP Pro SP2 x32
beatnik
Newbie
*
Offline Offline

Posts: 11


« Reply #106 on: March 14, 2008, 08:47:07 PM »

The batch file seems to have done the job, plus a little clean up with RegSupreme and I've now updated to the latest firewall with no problems.  Thanks USSS.
Logged
x111
Newbie
*
Offline Offline

Posts: 22


« Reply #107 on: March 17, 2008, 05:23:02 AM »

Can i use revo uninstaller http://www.revouninstaller.com for uninstalling & updating comodo instead of the batch file?
Logged
USSS
Comodo's Hero
*****
Offline Offline

Posts: 298


« Reply #108 on: March 17, 2008, 07:25:10 AM »

Yes.  The batch file is specifically designed to remove CFP, however.  Revo is a good addition to any user's suite of utilities.
Logged

Tip of the Day: "Old telephone directories make ideal personal address books. Simply cross out the names of all the people that you do not know."

ThinkPad T43 and Micron Millennia Desktop: Kaspersky Anti-Virus 7.0.1.325 and CFP 3.0.25.378 running on Windows XP Pro SP2 x32
doodler
Guest
« Reply #109 on: March 17, 2008, 09:38:07 AM »

"This batch file is only guaranteed to work on Windows XP Home/Professiona (all languages) using the final version of CFP 3 (until the current release, 3.0.17.304)."

I recently downloaded 3.0.19.318 but may need to uninstall it.  When I read the above (copied from the beginning of this thread), I can't tell if it means the batch file will only work for releases that are earlier than 3.0.17.304 or if it means the bach file will only work for releases that come after 3.0.17.304 (which would include mine).  Please clarify.
Logged
Ragwing
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 3451



« Reply #110 on: March 17, 2008, 12:34:26 PM »

"This batch file is only guaranteed to work on Windows XP Home/Professiona (all languages) using the final version of CFP 3 (until the current release, 3.0.17.304)."

I recently downloaded 3.0.19.318 but may need to uninstall it.  When I read the above (copied from the beginning of this thread), I can't tell if it means the batch file will only work for releases that are earlier than 3.0.17.304 or if it means the bach file will only work for releases that come after 3.0.17.304 (which would include mine).  Please clarify.

Ah, it's because the topic hasn't been updated for around 1 month, and back then, 3.0.17.304 was the latest version.
It should work fine with the latest version of CFP 3. I've updated the topic to avoid further confusion. And "until the current release, 3.0.17.304" includes all versions before 3.0.17.304 and 3.0.17.304 (now updated to 3.0.19.318).

Cheers,
Ragwing
Logged

giraffe
Comodo's Hero
*****
Offline Offline

Posts: 569



« Reply #111 on: March 24, 2008, 04:20:59 AM »

Forgive me if this has been mentioned, but going through 8 pages...

Just removed v2.4 and installed v3.

Looking in Device Manager - Hidden Devices - Unknown Devices, found 4 related to CFP:

CmdAgent, cmdGuard, cmdHelp and cmdMon; these are shown by their Properties – Driver.

None was actually labelled 'Comodo', so it's worth looking deeper.

(Also found some belonging to OA and AVG!).

Many thanks for the instructions, made the job a lot simpler (I'd never have known about Inspect, for instance).
Some Reg. entries were left under Legacy as I couldn't delete them.
Logged

XP Pro SP3
CIS
Avast!
Opera
SAS
USSS
Comodo's Hero
*****
Offline Offline

Posts: 298


« Reply #112 on: March 25, 2008, 04:03:05 PM »

We're glad you found the instructions helpful.

Regarding the LEGACY registry keys, they can be removed by elevating the permissions on each one (right click > Permissions > Full Control > Allow).  However, they are harmless to your system if left intact.
Logged

Tip of the Day: "Old telephone directories make ideal personal address books. Simply cross out the names of all the people that you do not know."

ThinkPad T43 and Micron Millennia Desktop: Kaspersky Anti-Virus 7.0.1.325 and CFP 3.0.25.378 running on Windows XP Pro SP2 x32
mantra
Comodo Loves me
****
Offline Offline

Posts: 196


« Reply #113 on: March 26, 2008, 01:19:25 AM »

Novice users: see the bottom of this post for information on how to do this in an easy and fast way!

I encountered significant difficulty in removing a previous version of CFP so that I could upgrade to the most recent edition, v3.0.14.276.  In reviewing some recent posts about incomplete or aborted installation routines, I thought I would post a set of comprehensive instructions for completely removing CFP. 

In particular, these instructions should help upgrading users who receive the message, “COMODO Firewall Pro is already installed. Do you want to un-install it now?" and after checking either the “Yes” or “No” button, nothing happens.

These instructions are specific to Windows XP Pro SP2 x32.  However, they may be adapted to your particular Windows installation, including Vista.  I make no guarantees that these instructions will work in your specific situation.  On my partitioned system, F:\ is used for Program Files.  Most users will have C:\ as the default location for Program Files.

Caution:  These instructions involve modifying the Windows Registry, either manually or by using a specialized registry management tool. If you are unsure of your ability to do this, there's an attached batch file that'll automatically delete everything mentioned below.[/i][/u].

If you have experienced problems removing CFP in the past, uninstalling in Safe Mode may work.  However, these instructions are not intended for use in a Safe Mode environment, though they may work.  I have not tested them in Safe Mode.

Before starting, make sure that you understand how to use Windows Regedit and its search function.  A good tutorial for this is located at:   http://www.theeldergeek.com/windows_xp_registry.htm   

Alternatively, you may want to install a well-known registry tool that includes a configurable search function and other utilities to remove references to installed software as well as any associated registry keys.  I use RegSupreme Pro and jv16 PowerTools.  Use whichever registry tool(s) you feel comfortable with.  While Windows Regedit offers basic functionality, it may not locate all relevant keys and values, which could preclude a successful upgrade to the latest version of CFP.  A good registry management tool is a worthwhile investment.

Optionally, I also recommend having a dedicated uninstaller utility, such as Your Uninstaller! 2006.  Again, use whichever third-party uninstallation program you prefer.  Otherwise, use the Control Panel’s “Add/Remove Programs” applet.

If anyone has additional steps they feel should be added to this list of instructions, please let me know and I will amend this post accordingly.  If there is enough interest by other members, perhaps this could be made “sticky” until some of the kinks have been worked out of future versions of CFP.

1.  Mandatory: create a System Restore point and label it appropriately.  Optionally, perform a full backup of your system (you should be doing this, anyway).

2.  Temporarily disable your Internet connection and shut down ALL unnecessary processes using Task Manager (a utility called EndItAll can make this task easier).

3.  Open your third-party uninstallation tool (or Control Panel > Add/Remove Programs) and run it as you would normally uninstall any application.

4.  If given the option, do not reboot when the uninstallation routine completes.  Instead, first clean out all temporary files, using the Windows Disk Cleanup utility.  Optionally, you may manually inspect other folders in which temporary files are typically found and delete them.

5.  Run your registry cleaner.  Be sure to make up a backup of the keys that are removed, just in case.

6.  Reboot.

7.  After rebooting, once again shut down ALL unnecessary processes using Task Manager and EndItAll.

8.  Remove the following folders and files, if they still exist. *Caution: if you are using other Comodo products, some of the folder and files listed below should not be removed.  Check the forum for guidance, as I am using only CFP):

     a.  *C:\Documents and Settings\All Users\Application Data\comodo
          DO NOT delete the folder above if you are running other Comodo products, such as CMF.
     b.  C:\Documents and Settings\All Users\Desktop\COMODO Firewall Pro
     c.  C:\Documents and Settings\%user name%\Application Data\Comodo
     d.  C:\Program Files\[Comodo Firewall Pro folder]
          (If you have partitioned your drive, the Comodo program folder be may in another location.)
     e.  C:\boot.ini.comodofirewall (this file may not exist). 
          WARNING: Do not mistakenly remove the original “boot.ini”.
     f.  *C:\WINDOWS\system32\drivers\cmdGuard.sys
     g. *C:\WINDOWS\system32\drivers\cmdhlp.sys
     h. *C:\WINDOWS\system32\drivers\inspect.sys
      i. *C:\WINDOWS\system32\guard32.dll

         * [denotes a folder or files that may be necessary for other Comodo programs running on your system.]

9.  Open Device Manager (Start > [right click] My Computer > Properties > System Properties > Hardware [tab] > Device Manager > View > Show Hidden Devices > Non-Plug and Play Drivers > [Remove all Comodo entries].  Entries may include some or all of the following:

    a.  Comodo Application Engine
    b.  Comodo Firewall Pro Driver Helper
    c.  Comodo Network Engine.

    Note:  if you have already removed the drivers listed in Step 8 above, some or all of the Comodo entries listed above may or may not be present.  If so, clicking “Properties” on Comodo Application Engine may show that “This hardware device is no longer connected to the computer.”  The other two will likely report that they are “working properly.”  To remove these entries, you may be prompted to reboot; however, do not waste time with multiple reboots trying to remove these entries as it is likely that a set of remnant registry keys is allowing the entries to remain.  Proceed to Steps 10 and 11 to resolve this.

10.  Open Regedit or your third-party registry tool and remove the following keys.
USE CAUTION if you have other Comodo products installed.  This is NOT an all-inclusive list; there may be other entries on your system not shown here (this list was modified on 12/21/07):

    a.  HKEY_CURRENT_USER\Software\ComodoGroup\CFP
    b.  HKEY_LOCAL_MACHINE\SOFTWARE\ComodoGroup\CDI\1 *
         *(If you have other Comodo products installed, delete only the values
           for CFP)
    c.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
         \cmdAgent
    d.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
         \cmdGuard
    e.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\cmdHlp
    f.   HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Inspect
    g.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services
         \cmdAgent
    h.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services
         \cmdGuard
    i.   HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\cmdHlp
    j.   HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Inspect
    k.  KEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services
         \cmdAgent
    l.   HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services
         \cmdGuard
   m.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\cmdHlp
    n.  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\Inspect
    o.  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cmdAgent
    p.  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cmdGuard
    q.  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cmdHlp
    r.   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
          \Inspect
    s.  HKEY_LOCAL_MACHINE\SYSTEM\Software\Comodo\Firewall Pro
    t.   HKEY_USERS\S-1-5-21-1202660629-746137067-2145843811-1003\Software\ComodoGroup\CFP
    u.  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 *
  kk.  HKEY_CURRENT_USER\Software\Local AppWizard-Generated Applications\CFP_Setup_3.0.14.276_XP_Vista_x32
    ll.  HKEY_CURRENT_USER\Software\Local AppWizard-Generated Applications\CFP_Setup_3.0.14.276_XP_Vista_x64
mm.  HKEY_CURRENT_USER\Software\Local AppWizard-Generated Applications\CFPLog
 nn.  HKEY_CURRENT_USER\Software\Local AppWizard-Generated Applications\CPFFileSubmission
 oo.  HKEY_LOCAL_MACHINE\SYSTEM\Software\Comodo\Firewall Pro


    *Note: It may not be possible to remove these "LEGACY" keys.  If you cannot delete them, leave them in the registry.  However, I have subsequently found that you MAY be able to remove these keys in Safe Mode by using a third-party registry tool.  To permanently remove them may also require modifying the Permissions for each key.  See: http://forums.comodo.com/help_for_v3/comprehensive_instructions_for_completely_removing_comodo_firewall_pro_info-t17220.0.html;msg119226#msg119226

If you are using a third-party registry tool, it may offer a feature that manages references to installed software.  Search for these entries that contain “comodo” and remove them, again exercising particular caution if you have other Comodo products installed.

11.  Open Regedit and highlight “My Computer”.  Then click Edit > Find and run searches  for the terms “comodo”, “cmd*” and “inspect” (without the quotes).  For the “cmd*” wild card search string, be careful not to delete any registry entries that reference “cmd” that is associated with commandEnsure the entry is associated only with Comodo.  If you are using a third-party registry tool, use its search function according to the instructions.  Again, make a backup of any keys that are removed, just in case.

12.  Reboot.

13.  Temporarily disable your Internet connection again, and open Windows Security Center.  Check to see that there is no reference to Comodo Firewall Pro.  If so, proceed to Step 14.  Otherwise. if the Windows Firewall has been re-enabled, disable it.  Proceed to Step 15.

14.  If there is still a reference to Comodo Firewall in Windows Security Center, run the “Wbem.exe” tool to reset the Security Center notification list.  This tool is available from the Comodo forum (search).  If you cannot find this tool for some reason, follow these steps (courtesy of forum member “pandlouk”):

    a.  At the command line of Windows XP  [Start > Run] enter the command "CMD" (without the quotes) and press Enter.
    b.  At the new Command Prompt window, type
         "NET STOP WINMGMT /Y" (without the quotes; there must be a space between WINMGMT and /Y) and press Enter. Then type "exit" end press Enter again.
    c.  Go to the folder C:\WINDOWS\system32\wbem and delete the folder "Repository".
    d.  Reboot. The Repository folder will be recreated automatically by the Security Center and will now display the correct information.

15.  Shut down ALL unnecessary processes using EndItAll and Task Manager.

16.  Install the latest version of CFP and configure as desired.  Reboot if prompted.

17.  Upon reboot, export your new default CFP configuration before making any changes to the firewall settings.

My contention is that no software should be this difficult to remove and/or install.  
In the meantime, I hope these instructions will help reduce the time and difficulty in migrating between different versions of CFP.  I am confident that, eventually, the Comodo programmers and developers will offer a more streamlined method of upgrading to future versions of this otherwise excellent firewall system.

------------------------------------------------------------------------------------------------------------
For novice users or people that want to save time

This batch file should work on Windows XP and Windows Vista (all languages) using the final version of CFP 3 (until the current release, 3.0.20.320).
Vista users will have to run the batch file as an administrator.
The legacy keys have to be removed manually, since they're protected by the system by default. Read step 10 in USSS' guide if you need help doing that.

The zip-file is attached to the post, so just click it and download will begin.
If you for some reason wouldn't see this link, you can download it thru RapidShare:
http://rapidshare.com/files/101562493/CFP_3_File_Registry_Cleaner.zip.html

Now unzip it using Windows built-in unzipper or a software like WinRAR or 7-zip, and then run it.

THIS IS NOT MEANT AS A STAND-ALONE UNINSTALLER, IT'S MADE TO DELETE LEFT-OVER FILES AND REGISTRY ENTRIES

Created by Ragwing. PM if you have any questions. Big thanks to USSS for providing the paths and registry entries!
Last update: March the 22nd 2008
Total downloads (not counting RapidShare downloads): 510


you forget

[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CMDAGENT\0000]
same group of keys


LEGACY_CMDGUARD
LEGACY_CMDHLP
LEGACY_INSPECT



 Comodo Wants You
Logged

Comodo Rocks  (R)
giraffe
Comodo's Hero
*****
Offline Offline

Posts: 569



« Reply #114 on: March 26, 2008, 03:43:54 AM »

We're glad you found the instructions helpful.

Regarding the LEGACY registry keys, they can be removed by elevating the permissions on each one (right click > Permissions > Full Control > Allow).  However, they are harmless to your system if left intact.

Yes, thanks for that - I just CBA! I used the 'Lite' version of Registrar for this - it removes most Legacy keys eventually, but some it wouldn't touch so I just left them.
Logged

XP Pro SP3
CIS
Avast!
Opera
SAS
mantra
Comodo Loves me
****
Offline Offline

Posts: 196


« Reply #115 on: March 26, 2008, 06:36:39 AM »

Yes, thanks for that - I just CBA! I used the 'Lite' version of Registrar for this - it removes most Legacy keys eventually, but some it wouldn't touch so I just left them.
i can't understand why jv16 power tool can't even find them
Logged

Comodo Rocks  (R)
USSS
Comodo's Hero
*****
Offline Offline

Posts: 298


« Reply #116 on: March 26, 2008, 09:07:49 AM »

i can't understand why jv16 power tool can't even find them
Yeah, I wondered about that, too.  I've used jv16 PT in "Aggressive" mode, and it made little difference.  Sometimes, I guess there's no substitute for a manual search of the registry.
Logged

Tip of the Day: "Old telephone directories make ideal personal address books. Simply cross out the names of all the people that you do not know."

ThinkPad T43 and Micron Millennia Desktop: Kaspersky Anti-Virus 7.0.1.325 and CFP 3.0.25.378 running on Windows XP Pro SP2 x32
x111
Newbie
*
Offline Offline

Posts: 22


« Reply #117 on: March 27, 2008, 07:56:25 AM »

Quote
2.  Temporarily disable your Internet connection and shut down ALL unnecessary processes using Task Manager (a utility called EndItAll can make this task easier).

Instead of shuting down processes wouldnt it be better to boot into safe mode for uninstalling.
Logged
USSS
Comodo's Hero
*****
Offline Offline

Posts: 298


« Reply #118 on: March 27, 2008, 07:06:50 PM »

Instead of shuting down processes wouldnt it be better to boot into safe mode for uninstalling.
It's really up to the user. 

I tend to reserve the use of "Safe Mode" when I encounter problems performing an otherwise "normal" uninstallation.  Since these instructions were first written back in mid-December, the trend has been toward increased use of "Safe Mode" when completely removing Comodo.  But now that the internal updater is working (for the most part, for most users), updating no longer requires full uninstallation of the previous version.
Logged

Tip of the Day: "Old telephone directories make ideal personal address books. Simply cross out the names of all the people that you do not know."

ThinkPad T43 and Micron Millennia Desktop: Kaspersky Anti-Virus 7.0.1.325 and CFP 3.0.25.378 running on Windows XP Pro SP2 x32
batrico
Comodo Member
**
Offline Offline

Posts: 26


« Reply #119 on: March 27, 2008, 10:06:27 PM »

After having problems updating from v3.20 to 3.21 i uninstalled cfp and tried to reinstall the new version.I got through all your steps eventually but when i installed the new version it still says its version 3.20.I am 99 percent sure i got rid off everything i was supposed (i even got rid of the legacy keys)to as the security panel said i had no firewalls on and could only find windows one.
im still getting prompted updates are available and i click on install but it doesnt ask me to reboot.

yay i solved my problem thanks to COLTRANE on another thread.

"Hi,

try this before reinstall: close CFP, then open it with "Run as Administrator" option. Disable Defense+ and Firewall as advised and try to update. I had your same problem but that way worked perfectly."

Now i am up to date.



or so i thought it reversing back to previous version on startup .
« Last Edit: April 04, 2008, 11:53:27 AM by batrico » Logged
Tags:
Pages: 1 ... 6 7 [8] 9 10 ... 20 Go Up Print 
« previous next »
Jump to:  

SSL Certificate Free Virus Removal Firewall
Page created in 0.067 seconds with 20 queries.
Powered by SMF 1.1.11 | SMF © 2006, Simple Machines LLC
Seo4Smf v0.2 © Webmaster's Talks
Design by 7dana.com