Resolved No desktop search programs will index my hard drive

Yesterday I started noticing that Google Desktop Search wasn't returning search results. I uninstalled and then reinstalled, but GDS would only give me an incredibly small number of files that I have on my computer wehn I would search for docs/terms that I know would give me results. I installed Windows Search and Copernic, and the same thing would happen. With both Google and Copernic, when I would click on the index status, I would be told that indexing will start 2 minutes or so after computer is idle, but it would never actually ever start. I disabled my wireless card as well as my antivirus, thinking that perhaps they are doing something that keeps the desktop search program from thinking the computer is idle, but still nothing worked.

I right-clicked on my D partition and it is set for indexing. I'm really not sure what I should do now. I use desktop search continually throughout the day and this is a real pain, not to be able to locate files I know I have.

Since three programs are giving me grief I'm thinkign that it isn't a bug in a program, but something on my hdd. Any suggestions?

 

This guide will show you how to setup the indexing service.

http://articles.techrepublic.com.com/5100-22_11-5533688.html

Check you have all the settings correct and let us now if there is any change.

Did you change anything before this error started? Have you looked in Event Viewer to see if there are any relevant error reports.

 

All the settings are correct. The drive, as well as the My Documetns folder in particular, is set for (fast) indexing. I didn't delete the other folders from the Indexing Service lists, as the article suggested, but speed of the service obviously wasn't the problem.

I do have some errors in my event viewer, although I'm not sure how to interpret them. Windows Search and Google Desktop Management both are showing warnings and errors, like this:

Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3013
Date: 12/28/2010
Time: 8:03:39 PM
User: N/A
Computer: PAUL-NRCW396W1E
Description:
The entry <D:\MY DOCUMENTS\HISTORY US A\AOC AND CONSTITUTION\CONSTITUTION READINGS.DOC> in the hash map cannot be updated.

Context: Application, SystemIndex Catalog

Details:
A device attached to the system is not functioning. (0x8007001f)


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Not sure exactly what it means, though.

 

That error code 0x8007001f and message returns all sorts of different problems unrelated to your problem but Trend Micro anti virus was mentioned, is that what you have. When you switched of the AV did you completely disable it so it was not even running in the background, check in Task Manager.

That .DOC file may be a problem, do you know what it is. You could try moving or deleting it to see if it makes any difference.

Another option is to do a system restore back before the problem started and see if that helps.

 

Mark no I've never had Trend Micro. I currently only have MSSE running. That one doc file is one I created. I don't see that one file as the problem, as I simply can't get any desktop search engine to index my hdd. That file has been on my hard drive for a while, and there weren't any problems before.

I'll try a system restore and see if that works.

 

OK, System Restore can fix a lot of problems but if it does not work I would have your PC checked for any infections in our Malware and Virus forum.

 

Mark, thanks. System restore didn't work. I tried three different restore points, including one I know was prior to the problems with desktop search. Each time, the same result--the system restore utility said that it was unable to restore.

I took your advice and started a new thread in the malware forum:

http://www.windowsbbs.com/malware-virus-removal/97081-malware-problems.html#post546898

Thanks again.

 

Lets see what happens in the Malware forum, I see one of the scans would not complete. We will see what our expert has to say before moving on here.

 

Pete, thanks. I tried that, but the Toshiba utility has so many options to choose from (the only initials I could make sense out of were SCSI and IDE), the program booted up but didn't run--I think I chose some of the wrong options.

Broni has detected a rootkit that was most likely giving me grief.

Just in case there is hardware damage--are you aware of any third-party hard drive diagnostics that I can use?

 

You have a Samsung hard drive, use the Samsung llink in Pete's post and download the Estool for CD ISO.

You have to extract the ISO file and burn the image to a CD with image burning software. Then boot the PC with the disc in the drive having set the CD drive to 1st in the boot order. Answer "Y" on the first page. Then use the Arrow keys to move the highlight down to the drive found by auto detect. Hit Enter, on next screen hit Enter again for "Drive Diagnostics" and it will run.

Not sure where you get Toshiba from

You can check your file system by clicking on Start then Run, enter sfc /scannow (include the gap between c & /)in the run box and hit Enter. You may be asked to insert the OS disc to replace any damaged files.

 

Neither am I.

At any rate, the scan (from the Samsung diagnostic) said that there were no errors on my hdd.

After doing a lot of scanning in the malware forum with Broni, I reinstalled Google Desktop and it is now indexing recent files, so all is well.

Thanks Mark, and to all who replied.

 

Pete, I thought Arie would be the one to remind me of that!

I will do that, but honestly I'd like to wait for a couple of days just to make sure its ok. I do have both of these threads bookmarked so I won't forget.

 

Pete, since we're on the topic, is lack of doing this the cause of my red rectangles in my profile?

 

Interesting. Is there any way I can see who/what threads? Even when I've disagreed with folks I don't ever recall modding them down.

Know what--never mind. I've got better things to do with my time... I'll wear it like a badge of honor.

 

Glad to hear you have it working again, I guess it was some corruption in Google desktop.