When does Comodo tell you the installation is corrupt? If it is when try to start cfp.exe, you should be able to just start the service first (another shortcut, to cmdagent.exe). If it is at boot, the misconfiguration is probably being detected by the kernel level drivers that load early in the boot. But Comodo uses so few resources without the GUI that there is no reason not to let it run in the background. Look at cmdagent.exe with task manager on your system-for me, currently using 1MB of memory and 0 gdi handles.
Have you tried making a shortcut to cmdagent.exe and just double clicking it before you start cfp.exe? For size, are you looking at private memory or commit size? Without cfp.exe? Seems to use a bit more at idle under XP.
Taskmanager has selectable columns under “view”, and a process has dedicated private memory and then working and committed memory depending on what it is doing. When activity is low, the OS gives memory back to the pool. In any case, this is 1% or so of your memory. Did you try starting cmdagent first?
Don’t know how to shut it down again without a reboot once it is started, unless you go to D+/my protected files and unprotect it-and that compromises security. If it were easy to shut down, malware could do it easily also.