This is so minor but still could lead to the same old complaints.
In Registry Cleaner settings the wording for the Unsafe to delete entries.
Reads - - - - - Scan for unsafe entries to delete
Should be - - Scan for unsafe to delete entries
Just swapping those two words changes the the meaning of the sentence.
And by now we all know someone will take it wrong.
No matter how much you try to warn them.
Your Operating System (and whether it’s 32bit/64bit); XP SP3 32 bit
Security Software Installed; CIS 3.5.57173.439
How you produced the problem; By installing CSC
How you tried to resolve the problem; -
Screen-shots with the error (if any); -
Post Memory Dumps on crash if you encounter any; -
Any other Additional Information; -
Minor installer bug: I chosed in the CSC installer not to install File Checksum, still a shortcut (non working of course) to this application was put in the Start Menu COMODO\System Cleaner\Tools folder.
Your Operating System (and whether it’s 32bit/64bit); XP SP3 32 bit
Security Software Installed; CIS 3.5.57173.439, Avira AV personal Free
How you produced the problem; By installing CSC using the auto update feature
How you tried to resolve the problem; - Uninstall CSC It will not let me uninstall even in safe mode I hope a restore point works. I could unistall the previous version of CSC after going to a restore point from earlier in the day.
Screen-shots with the error (if any); -
Here are the errors
Nope, I am a bit catious with CSC after that lil event. Sorry. I am just saying that it was nearly the same thing, but I had only did System Restore (Note: I am using Vista Ultimate 64bit). And I can read topic name…Lol (:HUG)
When I was trying to update to the new version over the old one. It was impossible to finish installation. So I tried to uninstall the old version first and an error appeared (screenshot 1). The strange thing is, that CSC itself launched and it was using HUGE ammount of memory (screenshot 2).
We know about this issue, it appears in all versions of Windows, and will be resolved in the next update.
Safe is to completely remove the old version of CSC before you update to current version.
Before you try to update CSC from 1.1.62802.22 version to 1.1.62802.23 version we recommend to delete all files from CSC installation directory(except executables),after that you can begin the installation.We know about this bug and it will be fixed in the next update.
I deleted some unsafe entries with registry protection activated, rebooted the computer (which was working fine on reboot) and selected “restore registry” in the Reg protect window. When I rebooted again and did a registry scan, and the entries that I deleted were NOT present (i.e. the registry protection did not restore the registry as promised). To restore the entries, I used the"Back up" function (which restored the entries).
Note: the registry entries were from an obsolete imaging program.
Windows XP sp3, CIS, superantispyware realtime, avira realtime, Boclean