Registry cleaner too Aggressive
Posted: Sat Apr 21, 2007 3:01 am
I strongly suspect the Ace Registry Cleaner has been too aggressive. I have used it for a long time without incident under W2K. I think this new version is the problem.
I discovered the following programs that were working fine stopped working after it ran. I am in the process of flipping from Win2K to Vista on my new machine. I have been experimenting with XP as well.
1. Vista. Would not reboot. It said the registry was corrupt, though I could read it fine in maintenance mode. That took weeks to recover from -- probably just one critical entry turfed by mistake. I could not run Ace to attempt a recover. Perhaps something you can run from maintenance mode is needed.
2. NTI CD maker
3. NTI Backup
4. CSE HTML Validator
All were fine after a reinstall.
It is unwise to yank entries in uninstall sections where the file does not exist. It may well exist by uninstall time, and without the entry, you leave an orphan. Ditto log files, which are not yet created, but the program needs the name of the file when it does get around to creating it.
I discovered the following programs that were working fine stopped working after it ran. I am in the process of flipping from Win2K to Vista on my new machine. I have been experimenting with XP as well.
1. Vista. Would not reboot. It said the registry was corrupt, though I could read it fine in maintenance mode. That took weeks to recover from -- probably just one critical entry turfed by mistake. I could not run Ace to attempt a recover. Perhaps something you can run from maintenance mode is needed.
2. NTI CD maker
3. NTI Backup
4. CSE HTML Validator
All were fine after a reinstall.
It is unwise to yank entries in uninstall sections where the file does not exist. It may well exist by uninstall time, and without the entry, you leave an orphan. Ditto log files, which are not yet created, but the program needs the name of the file when it does get around to creating it.