4 ms·

In Vista RTM and sp1 turning off indexer was a great solution. It was monster on the drive and memory (5-10 min startups on computers that should be up in 30-6

In Vista RTM and sp1 turning off indexer was a great solution. It was monster on the drive and memory (5-10 min startups on computers that should be up in 30-60 seconds and were after you turned things like that off). They fixed it in sp2. Superfetch was just as bad as well as the windows defender. Most of that was fixed in win7. I now let all 3 of those services run. The issues were fixed... The problem is these 'solutions' never go away. They are never revisited. So people just keep applying them because 15 years ago they had an issue with them.

rasz 5y ago
but why would you let indexer run at all when Everything (https://www.voidtools.com https://www.voidtools.com) runs faster, is more accurate, and is a small standalone executable?
- OrvalWintermute 5y ago
  In general I do not like Microsoft's integrated indexer because I noticed it really slowed down performance, and seemed to hog memory. Appreciate the utility you pointed out, will happily look into it.
- abrookewood 5y ago
  Please try Everything if you have never tried it before. It is BLAZINGLY fast. From memory it runs off the File Allocation Table to achieve its speed.
  - 112233 5y ago
    Looks like it still needs to build index of file names for searching. If you need to search local ntfs drive, try https://sourceforge.net/projects/swiftsearch/ https://sourceforge.net/projects/swiftsearch/ It does not build any indexes, and always shows up to date results (by scanning MFT)
    - rasz 5y ago
      It doesnt, running it in the background to build up cache is optional.
- EVa5I7bHFq9mnYK 5y ago
  They are completely different products. Everything searches just file names, while Windows indexer also searches file contents. It is a much more time consuming task.