[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] Vista and Itunes - THE OFFICIAL BLOG OF THE SBS DIVA
Sun, Dec 23 2007 23:24 bradley

Vista and Itunes

From the managed newsgroup ... a post on fixing indexing on Vista when it's fighting with Itunes... 

From the problem description of the post you submitted, my understanding
is: the CPU usage of the process Searchindexer.exe always keeps sticking at
100%. As I understand, you have done some research on Google and found that
the XML file of the program "iTunes" may be the root cause. If I have
misunderstood about your concern, feel free to let me know.

According to your description as well as our experiences, if the process
"Searchindexer.exe" always occupies the 100% CPU resource. The most common
cause of this behavior is one of the following factors:

1. The Search index is corrupt
2. Third party software or program (such as: ITunes in this case) running
in the background, which interferes with the Windows Search service

If one of above conditions is true, we may find the behavior that the Task
Manger shows that the CPU pegged at 100% with most of the usage the
searchindexer, but the "Control Panel" =>"Indexing Options" shows it is not

Firstly, let's add the XML file to the exclusion list of the Index Search
(per your request) to see if it helps. To do so, please refer to the steps

Step One: Add the XML file type to the exclusion list
1. Click Start, type: Indexing Options in the Start Search bar and then
press Enter.
2. Click Advanced button. Click Continue if it prompts.
3. Click "File Types" tab
4. In the list, please uncheck the checkbox of "XML - XML filter"
5. Click OK.

After that, we will be prompted to rebuild the Index completely. Click OK
to continue.

It may take some time to rebuild the Index catalogs and the Index Options
in Control Panel will show us its progress during the rebuilding period.
The index speed is reduced due to user activity, so I suggest we run this
progress without any other active background processes. Based on my
experience, the approximate time it costs is equal to the time that we do a
virus full scan on the same machine.

Once this procedure is complete, please reboot the machine and then check
if the issue still persists. If so, we recommend that you contact the
ITunes support service to require an updated version, which works with
Vista Windows Search function. For your convenience, I have included the
contact link of Apple for you below:

Apple Support

NOTE: This response contains a reference to a third party World Wide Web
site. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or
information found on these sites; therefore, Microsoft cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
from the Internet.

However, if the step one does not resolve our current issue, let's try the
advanced method to rebuild the index manually:

Step Two: Rebuild Index via Advanced Method
1. Keep the Windows Search service in the "Disabled" status.
2. Click on Start, and enter REGEDIT in the search field. Press Enter and
then Allow if prompted for permission to run regedit.exe.
3. Browse to: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Search 

4. Right-click on "Windows Search" and choose Permissions. Verify that
Administrator is the owner and has full control of the key.
5. Within the "Windows Search" registry key, find the
SetupCompletedSuccessfully value. Change the value to 0 if not already set.
6. Take ownership and delete the following registry:

HKLM\Software\Microsoft\Windows Search\Applications\windows
HKLM\Software\Microsoft\Windows Search\CatalogNames\windows
HKLM\Software\Microsoft\Windows Search\Databases\windows
HKLM\Software\Microsoft\Windows Search\Gather\windows
HKLM\Software\Microsoft\Windows Search\Gathering
HKLM\Software\Microsoft\Windows Search\UsnNotifier\windows 

7. After that, please delete the default index location folder. You can do
this from the command prompt with administrative privileges (run as
administrator) by typing the following:

rd %ProgramData%\Microsoft\Search\Data\Applications\Windows /S /Q

8. Go to the Services.msc and then re-enable and start the "Windows Search"
service. Please check if this service is able to start this time.
9. Once we are able to start the "Windows Search" service, please wait
approximately one minute and then check the SetupCompletedSuccessfully
registry value and it should now be set to 1 and the Search service should
rebuild the index database.

Step Three: Prepare the Clean boot
If the issue still occurs, let's disable all startup items and third party
services when booting. This method will help us determine if this issue is
caused by a loading program or service. Please perform the following steps:

1. Click the Start Button type "msconfig" (without quotation marks) in the
Start Search box, and then press Enter.

Note: If prompted, please click Continue on the User Account Control (UAC)
2. Click the "Services" tab, check the "Hide All Microsoft Services" box
and click "Disable All" (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".

Then, restart the computer. When the "System Configuration Utility" window
appears, please check the "Don't show this message or launch the System
Configuration Utility when Windows starts" box and click OK.

Please test this issue in the Clean Boot environment, if the issue
disappears in the Clean Boot environment, we can use a 50/50 approach to
quickly narrow down which entry is causing the issue.

Is our issue resolved?

Please let me know the results at your earliest convenience. If anything is
unclear in my post, please don't hesitate to let me know and I will be glad
to help. Thank you for your efforts and time.

Please note that: Performance issues can be difficult to troubleshoot and
resolve in a newsgroup setting due to the number of variables and the
amount of time required to narrow down possible causes and observe the
effects. We will assist as best as we can, but you may wish to consider
contacting CSS for a more timely resolution for these type issues.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.

Filed under: