I have traced an article on the Microsoft site headed:
"CPU usage in the Indexing Service (Cisvc.exe) increases
to 100 percent" which is happening on my machine. The
machine is unusable when this happens (frequently) but I
cannot understand why it has only just started. For some
reason I am not entitled to "free" support and wonder if
anyone can help. I gather there is a "hotfix" for this
but cannot trace it. Help/advice gratefully received.
Simon.

Simon,

No need for a Hotfix. Turn the damn thing off.

Start | Run | Type services.msc | OK |
Scroll down to and double click: Indexing Service |
Click the Stop button | In the Startup Type field,
select Disabled | Apply | OK
After you restart your machine it will stay disabled.

From Black Viper
http://www.blackviper.com

[[Indexing Service
This service always has been a major resource hog. I NEVER recommend having
this service enabled. Remove the function via the "Add / Remove Programs"
icon in the control panel (Windows Setup Programs). It uses about 500 K to 2
MB in an idle state, not to mention the amount of memory and CPU resources
it takes to INDEX the drives. I have had people (and witnessed it on other
people's computers) report to me that the Indexing Service sometimes starts
up EVEN while the system is NOT idle... as in the middle of a game. You may
feel, as I do, that this is unacceptable. If your computer suddenly seems
"sluggish," Indexing Service is usually the cause of it.]]

--
Hope this helps. Let us know.
Wes

In news:1220801c4428d$a8b2ab40$(E-Mail Removed),
Simon Brown <(E-Mail Removed)> hunted and pecked:
> I have traced an article on the Microsoft site headed:
> "CPU usage in the Indexing Service (Cisvc.exe) increases
> to 100 percent" which is happening on my machine. The
> machine is unusable when this happens (frequently) but I
> cannot understand why it has only just started. For some
> reason I am not entitled to "free" support and wonder if
> anyone can help. I gather there is a "hotfix" for this
> but cannot trace it. Help/advice gratefully received.
> Simon.

Thank you; didn't occur to me to remove it from Windows
components, either. Yay, full speed again...
Simon

>-----Original Message-----
>Simon,
>
>No need for a Hotfix. Turn the damn thing off.
>
>Start | Run | Type services.msc | OK |
>Scroll down to and double click: Indexing Service |
>Click the Stop button | In the Startup Type field,
>select Disabled | Apply | OK
>After you restart your machine it will stay disabled.
>
>Hope this helps. Let us know.
>Wes
>

Simon;

Watch the speed limit. ;-)

--
Hope this helps. Let us know.
Wes

In news:1294501c4430a$59261b20$(E-Mail Removed),
Simon Brown <(E-Mail Removed)> hunted and pecked:
> Thank you; didn't occur to me to remove it from Windows
> components, either. Yay, full speed again...
> Simon
>
>> -----Original Message-----
>> Simon,
>>
>> No need for a Hotfix. Turn the damn thing off.
>>
>> Start | Run | Type services.msc | OK |
>> Scroll down to and double click: Indexing Service |
>> Click the Stop button | In the Startup Type field,
>> select Disabled | Apply | OK
>> After you restart your machine it will stay disabled.
>>
>> Hope this helps. Let us know.
>> Wes