gringopig

The application will no longer delete the .jrs and .edb database files I believe... This has to be commended as the Search database should not bbe corrupted now. Have you tested this MrT? :-)

I remember more the article pointed to in the linked url http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/e286be80-ed7e-4026-b6b7-d512ff642db5 I experienced exactly those symptoms. The search errors I may not have experienced in the same way. The article though is specifically what I saw before I switched the MS Search option off in CCleaner. :-)

From memory, they weren't specifically 'search' errors, they were a cluster of errors (corrupt indexes and logfiles, ESENT errors and JET database errors) which were recorded every time it happened. The message was that the index had been 'corrupted' and was being re-built and upon inspection, the Indexer, which had been complete and populated was now building from scratch again. I didn't happen every time as some files may have been in use when CCleaner was run but it was these files that can be 'analyzed' that had been corrupted (actually deleted!) :-)

The point is that it shouldn't really 'return' to >256,000 files. That means that it's being reset. Look in the event log under Administrative Events. There is cleaning and there is interfering with a critical Windows function. I believe CCeaner is doing the latter.

OK. Type index into the Windows 7 search box and select Indexing Options. Note the number of entries reported. If you have multiple drives - add them as this will build a considerable number of entries. Mine is 273,462 with a number of drives added. The default set is smaller. Allow some time at idle for the index to be built up. Disks will spin! Select MS search in CCleaner. Run it and then reboot. Once up, type index into the search box again and after the delayed time period has elapsed you will see that the index has been broken and is rebuilding from scratch. Look in the event viewer and note all the errors about files being corrupt at the time of boot. (corrupt indexes and logfiles, ESENT errors and JET database errors) After I de-selected this MS Search option I have had no re-occurences of this issue. CCleaner is definitely breaking an important function of Windows, causing unnecessary disk thrashing. I have just done an analyse test on MS Search and it looks like the files will still be 'cleaned'

Yes, this option most certainly breaks Windows Indexer. A very poor choice to thrust this choice on unsuspecting users. I have had to warn countless friends to whom I have recommended CCleaner, to turn this off http://forum.piriform.com/index.php?showtopic=34030&hl=&fromsearch=1

I always think that CCleaner should be like the healing maggot; a medical marvel - eating away at the dead flesh. What horror though if these squirmy friends should burrow deep and eat the heart!

Er, no actually. I have 271,930 items indexed spread on multiple hard drives and it is not a trivial thing to keep on rebuilding the database on almost every boot. Add on to that all the debugging and re-installation of MS Office and registry hacks to reset the Search function in order to try to track this issue down. Not trivial. Add to that the normal user of this program who installs and forgets, trusting the developer not to set a parameter which, by default actually breaks an essential Windows component! Those 14 errors in Event Viewer are not the result of some harmless cleaning of unnecessary files and folders. I would urge the developers to either switch this off by default or preferably, to remove it entirely! I have been recommending CCleaner to friends and family for a long time now and believe me, NONE of them even know what Windows Search is, never mind about how it works. What they DO mind is the churning of ancient HDDs. Power users may choose to clean the operational files of an integral Windows component, normal users should not be forced to...

Hi all, I recently have been trying to find the reason as to why my Windows 7 machines are having the Windows search index rebuilt at boot due to corruption ans strongly suspect that it a the new setting in Application; that of 'MS search'. Just after boot but before the Windows search service starts, Event Viewer will throw up loads of errors about corrupt indexes and logfiles, ESENT errors and JET database errors - requiring the index to be rebuilt from scratch and consequently my 270k items on 4 HDDs are then re-indexed! This has not happened all the time but as it has just come to my attention, I now see this happen often and only at boot. I have noticed a new setting in CCleaner under Applications - Windows and I suspect this is what's breaking the index. It wasn't in version 3.08.1475 and must have been added in subsequent builds! This function deletes important files from the ProgramData/Microsoft/Search/data/Applications, depending on whether the files are locked by the OS or not. May I suggest this function is REMOVED? Or at least make it unselected by default as many users will be re-indexing constantly and be blissfully unaware of this. It is actually breaking an important function of Windows. I am testing to make sure this is the culprit but surely the developer's do not intend these consequences?

That's the same thing. The icon just disappears from the start menu list, leaving that self-same blank icon. It goes from all Windows functions which require an icon. I was going to leave a link to a screenshot of the fault, so I re-installed v2.24.1010 just as before to get it and, what would you know? The icon is OK. How irritating. I'll keep an eye on it just in case it goes walkies but I didn't do anything special this time and I had repeated the exercise numerous times to confirm the fault: going back and forward from v2.23.999 to v2.24.1010 and back to prove to myself that I wasn't doing something stupid. I probably didn't reboot however. Cheers...

Hi there. I've encountered a bug in the latest build v2.24.1010 on upgrading in Win7 RC1 x64 The start menu icon is missing and a blank generic one is seen instead. I update 'over the top' and have not seen this happen but for the last update from 2.23.999 to 2.24.1010. I can upgrade the older build over the top and the start menu icon comes back. It is not pinned but is populating the start menu as a commonly used program. Any ideas?