Search First! Then browse:
Categories |
Full Archive |
By Date |
Newsletter
Summary: Cidaemon is the "Content Indexing Daemon", which is a background process that builds a fast search index of the files on your computer.
What is cidaemon?
That's the "Content Indexing Daemon"; a background process that builds a fast search index of the files on your computer. Chances are you don't need it, and can disable the indexing service. "Black Viper" has a good overview of XP Services.
•
Article C2046 - June 14, 2004
How in the heck do I disable cidaemon? I see all kinds of comments about it but nothing I see tells me what to do about it.
Posted by: John Terdik at March 21, 2007 10:09 PMI realize cidaemon.exe is a Windows indexing service but if I sort the process list by name there are 2 of them. One of them takes a non-trivial amount of CPU time when I leave the computer alone for a while (expected), but quickly goes to zero when I touch my mouse.
Is it normal to have two of them on the process list? I double checked the spelling and they are in fact two separate processes running ( like multiple svchosts).
Thanks.
Posted by: kevin at November 8, 2007 4:11 PMThanks, everytime I take my computer off sleep mode and when I start it up, this process starts and it is really annoying.
Posted by: Reuel at December 17, 2007 4:52 PMHelped me do what I needed. Very relevant and effective stuff. Keep it up.
Cheers!
Posted by: Nani at December 31, 2007 1:32 PMhttp://www.adobe.com/cfusion/knowledgebase/index.cfm?id=330414
and/or
http://kb.adobe.com/selfservice/viewContent.do?externalId=330414
refer to solutions for the following problem:
Many Acrobat 7.0.x acr*.tmp files created in the Windows\Temp folder
Posted by: sheldon richter at February 4, 2008 2:02 PMIn my case, the hint about acr*.tmp files in the windows\temp folder was a good lead. Inside that folder I had over 20,000 files, and I think most were acr* files. Too many files made Explorer crash, so from command prompt I was able to delete all files in the temp folder, and the indexing service recovered to normal cpu usage.
Posted by: Fixed It at June 27, 2008 6:47 AMI had a problem where CIDaemon started using a lot of CPU as well. It happened after I installed Nero. Here was the solution for me...
http://kobyk.wordpress.com/2007/09/28/the-case-of-the-windows-desktop-search-cpu-hog/
Turns out nero uses an RTF file extension for files that aren't really RTF and these cause CIDaemon to thrash because it thinks they are actual RTF files and use tons of CPU. Rename the files in the nero directory with RTF extensions and the problem goes away! They are only used for VCD's so you probably don't need them anyway.
Posted by: Joe at February 2, 2009 9:00 PMcidaemon.exe, along with Indexing Services make the difference in Windows 2000 on minimalist hardware between just able to run Windows and having and enjoyable computing experience. It's never advisable to simple turn off anything Windows developers include with your system without first finding out why the problem exists and how to repair it. There is a "hotfix" available for this issue from Microsoft support. My advice is to download it and continue to use Indexing. If maintaining Windows takes too much of your time or unduly frustrates you how about trying Linux? Ubuntu now endorsed by IBM INVENTOR of the Personal Computer!
Posted by: JS Kaplan at March 3, 2009 11:49 AMAll hail Leo! I've been looking for a solution to cideamon.exe running all the time for weeks. Why couldn't I just have found Leo the first search??? Good to have my puter back on track. Thanks loads.
Posted by: LeighArias at March 23, 2009 1:27 PMGreat! This stopped cidaemon.exe from running automatically. I think there was a conflict between it and Google Desktop that was slowing my machine down significantly. Processing faster now though.
Posted by: jgdeutsch at May 13, 2009 6:27 PM