Oh, man! I can’t believe you actually posted this! 8)
I was having issues with CIS, so after tolerating the prollems for quite a while, I woke up on 28 Fri 2013 and said “Self, we’re going to do a clean re-install.”
So I uninstalled it. I get a pop-up at the end:
1:1703 2:Comodo Internet Security Premium
The pop-up was a modal form containing the the above described lablel and contained a button control.
After pressing the buton control, the system entered shutdown mode. After saving settings, the wallpaper went away and the grey screen appeared (the one just before the screen winks out). The HDD made these funny two chirping noises that HDD make when the SCSI host-controller is polling the SCSI bus for SCSI ID during boot.
Presto! BSOD C thousand 5.
I rebooted and everything was cool. I ran CCleaner and fixed vestiginal errors. I re-installed. When it did its shutdown gyrations at the end of the installation it did the same thing aforementioned. Presto! BSOD 7E.
I rebooted and everything was cool. I launched CIS and went to update it. It gave me the error message that it couldn’t access the servers. After mucking around, I determined that CIS was preventing DNS access. Nothing was displayed in the logs as being blocked.
O.k, gee that didn’t go well. As they say, “Second time’s a charm.” SO I uninstalled CIS and rebooted (see above gyrations).
Except this time when I rebooted: things weren’t cool. I got a notice that at least one service didn’t start. When I looked into the event logs, I noticed that DHCP and a couple other services didn’t start because the TCP/IP device couldn’t be found. So the TCP/IP stack was hosed now.
But wait! I’m smart. We have the tools. We have the tinker-toys. Gentlemen, we can rebuild it!
So I rebuild the TCP/IP stack and go to do the required re-boot and see above for the gyrations. I reboot and everythings cool. I can’t update CIS. I can’t get on the interwebs. I can attach to 192.168.0.1 and ping it fine. Several image restores and CIS failed post-reinstall update attempts resu;ted in corrupt TCP/IP stqack.
Well. This aint goin’ nowhere FAST! Looks like this is a time to restore from backup. Looks in backup folder - heart sinks - last backup: 9 Apr 2013. Alas, and woe be unto me. I backs system up as is, and then reformat & re-install HDD image backup made 9 Apr 2013.
System boots up and everythings cool. Well, except for the wonky little prollems that ulitmately caused me to say: “Self, we’re going to do a clean re-install.” SO I did. See above for gyrations. Grrr.
I went through innumerable evolutions of this, trying to remove HDD drivers, SCSI drivers, GFX driver, etc all to no avail. Eventually I determined it had nothing to do with drivedrs, hardware or the O/S, it was the CIS uninstall itself that was the culprit.
I tried the Revo Uninstaller thingy per the uninstall sticky thread. How’d I get onto the interwebs to find that? OH, I have a dual-boot system and the other system works good lasts long time. Thingy is: Revo Uninstaller implements default CIS uninstaller. See above for gyrations. The thing is: rebooting from dual-boot installed WinXP was problem free.
As the sky was getting light again Saturday morning, I said “Self, this is going nowhere FAST!”
Cut to the chase: I reformatted, restored image and then ran Windows Installer Clean-up Util. After selecting CIS in MSICUU I then manually deleted CIS folders in
C:\Documents and Settings\All Users\Application Data
and C:\Program Files.
It deleted everything except: cavshell.dll (stating that despite being Administrator / creator I didn’t have permissions). Couldn’t delete the file in safe mode either. Grrrr. Booted into dual-boot system and poofed remaining vestige. Rebooted into primary desktop O/S which promptly warned me something was wrong with CIS. No kidding?
I then ran CCleaner and let it fix the stuff mucked in the registry. I then rebooted. After the system came up, I re-installed CIS and updated it. Everything was hunky dory, and no more pesky wonky little problems with CIS.
Moral of the story: drink your Ovaltine.