http://www.winhelponline.com/blog/yet-another-serious-disk-cleanup-issue/ Troubleshooting Windows 7/XP/Vista, Fixes & Tweaks | General Productivity Tips Sun, 21 Mar 2010 03:33:46 +0000 hourly 1 http://www.winhelponline.com/blog/yet-another-serious-disk-cleanup-issue/comment-page-1/#comment-9771 jack nee Mon, 28 Dec 2009 11:09:32 +0000 http://www.winhelponline.com/blog/yet-another-serious-disk-cleanup-issue/#comment-9771 This is an update to my previous e-mail concerning Registry Defense. I verified that running this program will corrupt the Content Index Cleaner hive [remove Folder] and lead to a computer crash using Disk Cleanup. I hope this helps others avoid this condition. This is an update to my previous e-mail concerning Registry Defense. I verified that running this program will corrupt the Content Index Cleaner hive [remove Folder] and lead to a computer crash using Disk Cleanup. I hope this helps others avoid this condition.

]]> http://www.winhelponline.com/blog/yet-another-serious-disk-cleanup-issue/comment-page-1/#comment-9768 jack nee Mon, 28 Dec 2009 02:42:05 +0000 http://www.winhelponline.com/blog/yet-another-serious-disk-cleanup-issue/#comment-9768 Thank you so much. I had the same problem and had to wipe and reload my computer twice. After the second time a large number of bytes appeared under Catalog files after I downloaded and ran Reistry Defense. I finally found your site and downloaded the key fix and the Catalog file now reads zero. I reran Registry Defense and one of the errors it reported pertained to the Content Indexer Cleaner. I elected not to make the fix. I should have let it make it and see if it removed the Folder you talked about. Thank you so much. I had the same problem and had to wipe and reload my computer twice. After the second time a large number of bytes appeared under Catalog files after I downloaded and ran Reistry Defense. I finally found your site and downloaded the key fix and the Catalog file now reads zero. I reran Registry Defense and one of the errors it reported pertained to the Content Indexer Cleaner. I elected not to make the fix. I should have let it make it and see if it removed the Folder you talked about.

]]>