where do you click v4 to see what version you have. usually there is an ‘about’ example in IE7 click help/about internet explorer and it ells you version. Do not have 8 on this pc
FOUND IT Ok thanks
I do not see any refrence to xp sp3, only xp sp2, on the download link. Unless the universal installer covers it?
I wrote a mini tutorial to help look for drivers of previously installed (security) programs. It may be helpful with getting to the bottom by looking for drivers left behind by Comodo or other companies.
We are gonna take a look to see if there are some old drivers of your previously uninstalled security programs are still around. Go to Device Manager --> View --> show hidden devices --> now look under Non Plug and Play drivers --> when you see a driver that belongs to your previous security programs click right --> uninstall ---> reboot your computer.When the problem persists make sure there are no auto starts from your previous security programs. Download Autoruns and run it.
This program finds about all auto starts in Windows. This tool can therefore seriously damage Windows when not handled properly. After starting pusdh Escape and go to Options and choose to hide Windows and Microsoft entries, to include empty locations and then push F5 to refresh.
Now check all entries to see if there are references to your previous security program. When you find them untick them. After unticking reboot your computer and see what happens.
Are there names other than comodo* to look for in the driver list?
For me there is nothing related to comodo firewall. I’m also regularly using Sysinternals tools (particularly procexp but it’s not the subject) and there is nothing in autoruns related to firewalls or even with HijackThis.
I’ve done searches in registry with Registrar Lite for “comodo” “cis” or “cfp” and deleted a few keys left from the rollback of the v4 installer but still the error 1603.
here is some more info I found about 1603 errors.
Error 1603 is a problem caused by Windows Installer when you either try and use or install it on your system. Windows installer is a program that allows you to install various programs onto your Windows computer, and is used primarily as a base to help Windows install all sorts of settings, files and software onto your PC. Unfortunately, the 1603 error will show because of several issues with this package. Here's how to fix these errors...This error is caused by 3 different problems:
* You're trying to install Windows Installer in an encrypted folder on your PC * The drive you're trying to install Windows installer to is a virtual / substitute drive * The Windows installer process is using the SYSTEM account & it does not have any privilegesThe first thing you need to do to fix the 1603 error is to make sure that you’re not trying to install the Windows Installer program into an encrypted folder on your PC. To do this, you should change the folder or create a new one, and then instruct the installer to install the program into that folder.
If this fails to work, you should then try and install the Windows Installer software onto a different drive. Many computers have substitute drives / virtual drives that are created because of system disc partitioning, meaning that if you try and install the software onto one of these drives, it will be unable to correctly install what it needs to. You should install the software onto a different drive if possible.
You should also make sure that the “System” user profile on your PC is able to install packages and programs on your PC. It’s often the case that this user account does not have any privileges to install the various files and settings on your computer - meaning that if you’re using this account, it’s essential that you make it able to install the files on your PC.
It’s also recommended that you use a ‘registry cleaner’ to fix any of the errors that Windows computers generally have as well. Registry cleaners are software programs which scan through the “registry database” of Windows and fix any of the errors that it has inside. The registry is a central database which keeps a large number of file for your computer, allowing it to save & recall a large number of different files on your PC. Unfortunately, the registry is also a big cause of problems for your system as it’s continually being saved in the wrong way, which leads to errors including the 1603 error. To fix this, you should use a ‘registry cleaner’ to fix the various problems that are inside your system.
SOLUTION Method 1: Unregister and re-register the Windows Installer 1. Click Start, click Run, type MSIEXEC /UNREGISTER, and then click OK. Even if you do this correctly, it may look like nothing occurs. 2. Click Start, click Run, type MSIEXEC /REGSERVER, and then click OK. Even if you do this correctly, it may look like nothing occurs, or you may briefly see an hourglass. After you run this command, the operation is complete. 3. Try your Windows Installer-based application again. Back to the top Back to the top Method 2: Verify the DCOM permissions This method involves changing the DCOM default impersonation level to Identify, removing the Msisip.dll file, and then reinstalling SP 3 for Windows 2000.To do this, follow these steps:
- Click Start, click Run, type dcomcnfg, and then click OK.
- On the Default Properties tab:
a. In the Default Authentication Level list, click Connect.
b. In the Default Impersonation Level list, click Identify, and then click OK.- Click Start, click Run, type explorer /select, %windir%\system32\msisip.dll, and then click OK.
- Rename the Msisip.dll file as Msisip.old.
- Reinstall Windows 2000 Service Pack 3.
Back to the top Back to the top
Method 3: Give Full Control permission to the SYSTEM account- Start Windows Explorer, right-click the computer’s root hard drive, and then click Properties.
- Click the Security tab, and then click Add.
- In the Select Users, Computers, or Groups dialog box, click the SYSTEM account, click Add, and then click OK.
- Under Allow, click to select the Full Control check box, and then click OK.
- Click the TEMP folder and then verify that the SYSTEM account has full control.
Back to the top Back to the top
Method 4: Verify the registry permissions- Click Start, click Run, then type Regedt32.
- For each of the registry hives, follow these steps:
a. Select the hive.
b. For Windows XP, on the Edit menu, click Permissions.For Windows 2000 and Windows NT 4, on the Security menu, click Permissions.
3. Verify that the SYSTEM account has been added and that it has Full control. If it does not, add the SYSTEM account with Full control.
Back to the top Back to the top
Method 5: Fix the broken security key for the MsiServer service
- Start the computer by using Windows 2000.
- Click Start, click Run, type regedit.exe, and then rename the following key to Old_Security:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer\Security- Restart the computer (you must do this).
- Run Instmsiw.exe for installer 2.0 again; this corrects the broken security key for the MSI service.
languy99, I’ve been there and I’ve done that a few hours ago 
I was surprised to see that the SYSTEM account did not have any privileges on my system drive…
So I followed the instructions, but nothing changed.
Of course I want to install comodo firewall on the system drive.
It is weird because I regularly install/uninstall applications and I never had this error before.
Thanks, everyone for all the helpful suggestions. I tried several of them with no luck and decided not to “experiment” with the registry for the time being.
Fortunately, I saved my old copy of v3 and managed to reinstall it. I think I’m just going to run with it for a while until Comodo makes a final identification of the problem and comes out with a maintenance release.
Meanwhile, does anyone know to turn off those annoying upgrade reminders?
Thx!
agreed, I shall wait as well
You can disable the automatic notification of updates under Miscellaneous → Settings → Update.
Thanks EricJH - Your advice to use the CIS Cleanup tool solved my problem!
I had also been battling to get the latest version of Comodo Firewall (4.1.15) installed after having for several years been using Comodo 3.14. Always got error 1603.
I had first tried, just trying to instal 4.1.15 over 3.15 no go error 1603. I then tried uninsatlling 3.15 and then trying 4.1.15, again error 1603
After your advice Comodo version 4.1.15 installed with no problems
My only comment is why Comodo makes it so difficult (one has to search and search for advice!) to upgrade!
This is my only complaint with Comodo as otherwise it is an excellent firewall and I have tried several over the years. Thanks again!
Hi,
I just wanted to tell you all, that I have finally been successful in installing Comodo Internet Security ( Comodo Anti Virus for my purpose ) on this Windows 2003 Server. ( 32-bit )
I was constantly being annoyed by 1603, then I did the following & I have a working CAV.
Just thought that I post it here, so I may be of help for someone.
-
Disabled Windows Installer Roll-back feature by adding a REG_DWORD value of value 1 here HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\Installer.
-
Tried to install by running cav_installer_x86.exe. ( Won’t install it successfully, however won’t also rollback (I think) )
After roll-back feature disabled, the files given in the next step are present in your drive. -
Manually ran these files in this order :
C:\Program Files\COMODO\COMODO Internet Security\cmdagent.exe
C:\Program Files\COMODO\COMODO Internet Security\cfp.exe
At this, I got a partially working CAV ( a system tray icon ), which says Defense+ is not functioning properly, and won’t update.
- Then I run this, and voila.
C:\Documents and Settings\All Users\Application Data\Comodo Downloader\CAV_Setup.msi
After pressing next, 3 options are given with 1 grayed out ( Change, Repair(grayed out/unavailable), Remove )
I clicked Change and then selected Comodo Anti Virus, and then Next, Next, Next . . . . .
It ran the install process, and much to my delight, didn’t give that ■■■■■■■■ 1603 error, successfully installed CAV, and asked me to restart, and after that, a fully functional Comodo Anti Virus.
Thankx Comodo, I have finally found a free Anti Virus product for Windows 2003 Server.
Hope that you could make this process automated somehow.
Very happy that it finally worked ( or installed should I say ).
Virus Database Update in progress now ( 84.6 MB )
Thanks a lot, this did it for me. I get some errors of the diagnostic, but at least CIS works again.
Finally I succeeded in installing V4, after having 1603 all the times… Here is how it worked on my machine:
First I tried on a Oracle VM Virtualbox:
XP Sp3
Antivir Version 9
Sygate Firewall:
- Uninstalled (!) antivir and sysgate.
- run antivir registrycleaner
- reboot
- install cfw_installer_x86.exe
- reboot
- install avira
no flaws at all.
Then I tried at normal system
Win XP SP3.
Antivirus: Antivir Personal 10.X
Comodo FW 3.x
- disable (!) antivir
- install cfw_installer_x86.exe
- after auto_reboot, wait for stable system, THEN disable antivir again, THEN proceed install
- reboot
Note: no obvoius need to run the comodo-cleaner.
Everything seems to work.
good luck.
I also tried installing CIS with Antivir on one and Avast! on the orher. No problems. You only need to make sure you don’t end up with two resident AV or Firewalls at the same time. That is when real truble can start. Anyway I read this and some other threads and it really takes too much time to read all of the topics and posts, just to be able to install one program… If anyone wants a summary whith a step by step explanation, that even a more layperson can follow (I hope), you can find it here:
I keep getting an error1603 when trying to install the new firewall.
I’m running Windows XP and had the previous version, any ideas what is causing this?
I’ve rebooted and tried again and got the same error, even disabled AV (Symantec) autoprotect, same problem.
I had the previous version of the Comodo firewall and loved it. I’ve searched the knowledge base for this error and the forums and it came back with 0 results for both searches.
Any help would be great!
Edit by EricJH: merged
Hello,
Use the remove tool form this post https://forums.comodo.com/install-setup-configuration-help-cis/cleanup-tool-for-comodo-internet-security-t36499.0.html to remove the remaints from the previous version and install the Comodo from here Firewall Download | Best Firewall Security software for Windows.
Ovidiu
This worked for me. There was a registry entry for CIS 3.X Deleting the key resolved my issue, which was pretty frustrating, especially since I had to turn to ZoneAlarm in the interim and ZA was incompatible with my Wireless Print Server (instant BSOD on trying to print - lovely).
On a side note, I’d tried two different registry cleaners, neither of which caught this. On top of that, one of them was Comodo System Cleaner 
OK, tried this for the first time today. Uninstalled v3, started Windows Firewall, and started the v4 setup. Wasn’t happy about having to lose over a years worth of settings just for updating, but that turned out to be the least of my problems.
It didn’t install, so I came to this forum. downloaded and ran the disk cleanup utility, reboot, run utility again. v4 went through the installation and said everything went fine. Rebooted, and received no clue that Comodo was running. Comodo Internet Security Helper Service was listed as “Started” in the local services window.
What went really bad is that my internet no longer works. I’m told there is little or no connectivity. I disabled the Comodo Service, rebooted, still no service.
Make me love you again, its starting to look like our relationship is starting to turn sour.
Re above - I did reboot before ever trying o install v4
Windows XP Pro SP2 32 bit
The folder I asked Comodo to install to was C:\Security\Firewall\Comodo
the folder it installed to was C:\Security\Firewall\Comodo\COMODO\COMODO Inernet Seciruty
What a headache. [Win XP SP3 32bit; AVG antivirus] Due to constant reminder pop-ups about an update I finally clicked to download and install the new version. There were no instructions what-so-ever: should I manually uninstall the previous firewall? Should I disable my AVG antivirus? Should I download and then run it, or click run from the website? After downloading should I disconnect from the internet during the instalation? Everything seemed to go well until the end when I got the Error 1603 message. Re-downloaded & tried it a few times again; same error. On these forums I found the cleanup batch file (Ragwing) downloaded it and ran it and after that the new Comodo still wouldn’t load. So I ran Comodo System Cleaner and let it clean out what ever it wanted to. My computer wouldn’t load windows upon reboot. There was a cryptic message that there was a problem with C:\Windows\System32\config\System. I had to boot windows from the Win XP CD and that worked well enough to go back to a restore point before I started the whole “update” fiasco. The old Comodo firewall was back upon restore but didn’t have the help file and the colors were bland/wrong. So I uninstalled it and went back to Windows XP firewall. I really don’t want to spend hours on end trying to fix my computer. The previous firewall worked fine except the pesky defense pop-ups that couldn’t even recognize the routine Microsoft updates (such as mrt.exe) as safe files. I may try it again in a month or two when the bugs are worked out(?) but until there is a robust uninstaller/installer I don’t trust my computer with the new firewall. After reading about all the people monkeying with their registry entries and the unofficial/not-officially-supported clean-up batch file I don’t know why Comodo doesn’t “officially” fix this problem in the official installer?