Windows Vista Search Indexer Stopped Working

Windows Update woes . It ensures that most Windows users are automatically kept up to date with the latest security patches for their OS. Especially now that is no longer tied to Microsoft's Internet Explorer browser, I'm a big fan (with one exception). Unfortunately, on rare occasions, the Windows Update client gets in a corrupted state and things get messed up in a big way. This can be difficult to diagnose or troubleshoot.

I recently performed some simple maintenance on a set of company PCs. They were fairly recent, albeit somewhat underpowered Dell desktops with 2.

A small problem: my machine keeps haunting me with "Microsoft Windows Search Indexer stopped working and was closed". Microsoft Windows 7, Windows XP and Windows Vista operating systems have so many internal software services that are designed to serve the connected hardware.

GHz Celerons and 1. GB of RAM running Windows Vista Home Basic 3. For the relatively light office work with people browsing, and using Office 2.

Word, Excel and e- mail, this should be sufficient however. All employees using those PCs, one in particular, had been complaining of generally sluggish performance. Replacing the bloated anti- virus software with something a little more lightweight, the crappy Adobe Reader with Foxit's (free) alternative and upgrading the RAM to 2. GB made all the employees a darn sight happier. All, except one. This one PC responded slowly to everything. Even sitting idle at the desktop, with no open applications, there was constant disk thrashing. Task Manager also revealed a continuous 1.

CPU usage. Task manager set to show processes from all users revealed that most of this was the Windows Search Indexer. One would have to wonder what it was indexing continuously. Shutting down indexing didn't have much effect, as the CPU cycles were now simply absorbed by a few other processes and the disk thrashing continued. They were Trusted. Installer. exe and wermgr. The former is the . Particularly the resource monitor was of interest.

How to Fix Microsoft Windows Search Indexer Stopped. One such issue is with Windows Vista and it relates to the

This can be accessed from the . Resource monitor showed that the disk I/O was a reasonably constant 5. MB/sec. It also shows which files are being read/written.

Some files, such as C: \$Mft and C: \$Log. File are part of the normal operation of NTFS file systems and frequent access to those, while an indication that something else may be amiss, does not point directly to the problem. Other accesses were more suspicious. There was an inordinate number of accesses to C: \Windows\Logs\CBS\CBS. C: \Windows\Logs\CBS\CBS. These are Vista's patch logs, containing information that was stored in Windows.

Update. log on Windows XP. There was also a very large number of writes to ..\Microsoft\Windows\WER\Report. Queue and C: \Windows\Software. Distribution\Download.

A quick check at the logs files and in the Report. Queue showed that the system was silently logging and reporting an error roughly every 5 seconds, writing mini core dumps every time as well as continually attempting to locally store updates and failing. A few tests showed that this machine did indeed fail to download updates, getting stuck at 0 or sometime during the download process or when it did install them, it would get stuck on Configuring updates Stage 3 of 3 at 0, 9. Still, that only allows booting back into Windows, by ignoring the pending update, and doesn't solve the underlying problem. Of course, this left Windows Update in an inconsistent state and it ended up throwing the dreaded catch- all 0x.

FFFF error code. Fortunately, Microsoft have an excellent knowledge base article that describes what registry settings to delete to get it working again. After that, I could take the time to figure out why it was getting stuck. The update function had gone haywire, having stored close to a hundred thousand files, making the C: \Windows\Software. Distribution\Download folder a ridiculous 2. GB in size, accounting for some 4. After stopping the Windows Update service, it is possible to just delete the folder. You can even delete the entire C: \Windows\Software.

• I have the problem in windows XP and I can't find the unblock option when I right click on the file. I tried pretty much all solutions available on the web, but still.
• Please perform the following steps: Please go to Pearl button (Start) and click on the Search programs and files For more information about the change from Start to.
• Search Indexer Stopped Working. Microsoft Windows Search Indexer stopped working and was. I got this Search Indexer message again so apparently whatever was.
• If Windows Search or Search Indexer is not working. If on searching in Windows 8, Windows 7 or Windows Vista. Microsoft Windows Search Indexer Stopped Working.
• Windows Search makes searching for files on your PC a lot faster, but if you find that things slow down when Windows indexes files or that Search isn’t working as.
• Microsoft Windows Search Indexer has stopped working.
• Good article, fixed the PDF search in windows 7 64 bit for me, but one complaint. Your article is not printable. Chrome has the best print feature of all browsers and.

Distribution folder, thus resetting all of Windows Update, but Windows Update will require a lot more time on its next run. The sheer number of files caused that delete operation to take more than an hour. After that, I manually installed what is basically the Windows Update Update.

It took a few hours of forensics and thumb twiddling, but finally all updates had gone through, including Vista SP2 and the system was running normally again. The disk thrashing had stopped, CPU usage was down to single digits and everything responded smoothly. Having a smoothly running system turned one complaining employee into a happy camper again.