I just installed MDS 3.01 since I've recently installed Office 2007
and wanted the integrated instant search feature. I was using Copernic
Desktop search before but thought I'd uninstall that and see if I
could live with MDS instead.

I basically set it up to index all my harddrives. At first when it
started indexing it seemed to be fine. But then this morning, I found
that the process C:\WINDOWS\system32\SearchProtocolHost.exe was
consuming all my CPU and rendering the computer virtually unusable.
This despite the message in Indexing Status that claimed "Indexing
speed is reduced while you use your computer" or "indexing
paused..."!

In order to use my computer I needed to hit the "Snooze" button. It
took about a minute or 2 before the CPU activity stopped, but
eventually it did and my computer became responsive again. I did this
a couple of times (set at 15 minute snooze). The second time, indexing
never started again (until I unchecked the snooze option in the tray
icon's popup menu). Now it seems to be okay again, indexing in the
background without monopolizing my computer's resources...

What's going on? I thought the point was that the indexer is supposed
to be well behaved and back off immediately if I'm trying to use the
computer. Is there any way to fix this (short of uninstalling the
search engine)?

Thanks!

Windows Desktop Search: Technical Resources Overview:
http://www.microsoft.com/windows/pro...resources.mspx

The above is about the extent of available support for Windows Desktop
Search. Good luck.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L.ORG http://66.39.69.143/

Magritte wrote:
> I just installed MDS 3.01 since I've recently installed Office 2007
> and wanted the integrated instant search feature. I was using Copernic
> Desktop search before but thought I'd uninstall that and see if I
> could live with MDS instead.
>
> I basically set it up to index all my harddrives. At first when it
> started indexing it seemed to be fine. But then this morning, I found
> that the process C:\WINDOWS\system32\SearchProtocolHost.exe was
> consuming all my CPU and rendering the computer virtually unusable.
> This despite the message in Indexing Status that claimed "Indexing
> speed is reduced while you use your computer" or "indexing
> paused..."!
>
> In order to use my computer I needed to hit the "Snooze" button. It
> took about a minute or 2 before the CPU activity stopped, but
> eventually it did and my computer became responsive again. I did this
> a couple of times (set at 15 minute snooze). The second time, indexing
> never started again (until I unchecked the snooze option in the tray
> icon's popup menu). Now it seems to be okay again, indexing in the
> background without monopolizing my computer's resources...
>
> What's going on? I thought the point was that the indexer is supposed
> to be well behaved and back off immediately if I'm trying to use the
> computer. Is there any way to fix this (short of uninstalling the
> search engine)?
>
> Thanks!

On Dec 19, 4:11 pm, "PA Bear" <PABear...******.com> wrote:
> Windows Desktop Search: Technical Resources Overview:http://www.microsoft.com/windows/pro...ktopsearch/tec...
>
> The above is about the extent of available support for Windows Desktop
> Search. Good luck.
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE, OE, Security, Shell/User)
> AumHa VSOP & Adminhttp://aumha.net
> DTS-L.ORGhttp://66.39.69.143/
>
> Magritte wrote:
> > I just installed MDS 3.01 since I've recently installed Office 2007
> > and wanted the integrated instant search feature. I was using Copernic
> > Desktop search before but thought I'd uninstall that and see if I
> > could live with MDS instead.
>
> > I basically set it up to index all my harddrives. At first when it
> > started indexing it seemed to be fine. But then this morning, I found
> > that the process C:\WINDOWS\system32\SearchProtocolHost.exe was
> > consuming all my CPU and rendering the computer virtually unusable.
> > This despite the message in Indexing Status that claimed "Indexing
> > speed is reduced while you use your computer" or "indexing
> > paused..."!
>
> > In order to use my computer I needed to hit the "Snooze" button. It
> > took about a minute or 2 before the CPU activity stopped, but
> > eventually it did and my computer became responsive again. I did this
> > a couple of times (set at 15 minute snooze). The second time, indexing
> > never started again (until I unchecked the snooze option in the tray
> > icon's popup menu). Now it seems to be okay again, indexing in the
> > background without monopolizing my computer's resources...
>
> > What's going on? I thought the point was that the indexer is supposed
> > to be well behaved and back off immediately if I'm trying to use the
> > computer. Is there any way to fix this (short of uninstalling the
> > search engine)?
>
> > Thanks!

Yeah, I tried that first:

"Does indexing slow down the PC?

For both Windows Vista and Windows Desktop Search on Windows XP, the
indexing process has built-in logic that enables it to be "smart"
about what users are doing on the PC. When Windows Search sees that
the user or another application is actively using the PC, the indexing
process backs off to enable the user or application to take full
advantage of CPU power. This is also the case even when you have
installed a third-party desktop search offering. Once the PC enters an
idle state, Windows Search updates the index."

Not very useful... Is there a better forum in which to get help?

Thanks!

Magritte wrote:
> On Dec 19, 4:11 pm, "PA Bear" <PABear...******.com> wrote:
>> Windows Desktop Search: Technical Resources
>> Overview:http://www.microsoft.com/windows/pro...ktopsearch/tec...
>>
>> The above is about the extent of available support for Windows Desktop
>> Search. Good luck.
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-Windows (IE, OE, Security, Shell/User)
>> AumHa VSOP & Adminhttp://aumha.net
>> DTS-L.ORGhttp://66.39.69.143/
>>
>> Magritte wrote:
>>> I just installed MDS 3.01 since I've recently installed Office 2007
>>> and wanted the integrated instant search feature. I was using Copernic
>>> Desktop search before but thought I'd uninstall that and see if I
>>> could live with MDS instead.
>>
>>> I basically set it up to index all my harddrives. At first when it
>>> started indexing it seemed to be fine. But then this morning, I found
>>> that the process C:\WINDOWS\system32\SearchProtocolHost.exe was
>>> consuming all my CPU and rendering the computer virtually unusable.
>>> This despite the message in Indexing Status that claimed "Indexing
>>> speed is reduced while you use your computer" or "indexing
>>> paused..."!
>>
>>> In order to use my computer I needed to hit the "Snooze" button. It
>>> took about a minute or 2 before the CPU activity stopped, but
>>> eventually it did and my computer became responsive again. I did this
>>> a couple of times (set at 15 minute snooze). The second time, indexing
>>> never started again (until I unchecked the snooze option in the tray
>>> icon's popup menu). Now it seems to be okay again, indexing in the
>>> background without monopolizing my computer's resources...
>>
>>> What's going on? I thought the point was that the indexer is supposed
>>> to be well behaved and back off immediately if I'm trying to use the
>>> computer. Is there any way to fix this (short of uninstalling the
>>> search engine)?
>>
>>> Thanks!
>
> Yeah, I tried that first:
>
> "Does indexing slow down the PC?
>
> For both Windows Vista and Windows Desktop Search on Windows XP, the
> indexing process has built-in logic that enables it to be "smart"
> about what users are doing on the PC. When Windows Search sees that
> the user or another application is actively using the PC, the indexing
> process backs off to enable the user or application to take full
> advantage of CPU power. This is also the case even when you have
> installed a third-party desktop search offering. Once the PC enters an
> idle state, Windows Search updates the index."
>
> Not very useful... Is there a better forum in which to get help?

Not that I know of, hence my last reply.

I've had similar problems with each version of WDS (except the latest) and
the only solution I could find was un-install it and start over.

Frank

"PA Bear" <PABearMVP******.com> wrote in message
news:Ou%23A3NqQIHA.5400@TK2MSFTNGP04.phx.gbl...
> Magritte wrote:
>> On Dec 19, 4:11 pm, "PA Bear" <PABear...******.com> wrote:
>>> Windows Desktop Search: Technical Resources
>>> Overview:http://www.microsoft.com/windows/pro...ktopsearch/tec...
>>>
>>> The above is about the extent of available support for Windows Desktop
>>> Search. Good luck.
>>> --
>>> ~Robear Dyer (PA Bear)
>>> MS MVP-Windows (IE, OE, Security, Shell/User)
>>> AumHa VSOP & Adminhttp://aumha.net
>>> DTS-L.ORGhttp://66.39.69.143/
>>>
>>> Magritte wrote:
>>>> I just installed MDS 3.01 since I've recently installed Office 2007
>>>> and wanted the integrated instant search feature. I was using Copernic
>>>> Desktop search before but thought I'd uninstall that and see if I
>>>> could live with MDS instead.
>>>
>>>> I basically set it up to index all my harddrives. At first when it
>>>> started indexing it seemed to be fine. But then this morning, I found
>>>> that the process C:\WINDOWS\system32\SearchProtocolHost.exe was
>>>> consuming all my CPU and rendering the computer virtually unusable.
>>>> This despite the message in Indexing Status that claimed "Indexing
>>>> speed is reduced while you use your computer" or "indexing
>>>> paused..."!
>>>
>>>> In order to use my computer I needed to hit the "Snooze" button. It
>>>> took about a minute or 2 before the CPU activity stopped, but
>>>> eventually it did and my computer became responsive again. I did this
>>>> a couple of times (set at 15 minute snooze). The second time, indexing
>>>> never started again (until I unchecked the snooze option in the tray
>>>> icon's popup menu). Now it seems to be okay again, indexing in the
>>>> background without monopolizing my computer's resources...
>>>
>>>> What's going on? I thought the point was that the indexer is supposed
>>>> to be well behaved and back off immediately if I'm trying to use the
>>>> computer. Is there any way to fix this (short of uninstalling the
>>>> search engine)?
>>>
>>>> Thanks!
>>
>> Yeah, I tried that first:
>>
>> "Does indexing slow down the PC?
>>
>> For both Windows Vista and Windows Desktop Search on Windows XP, the
>> indexing process has built-in logic that enables it to be "smart"
>> about what users are doing on the PC. When Windows Search sees that
>> the user or another application is actively using the PC, the indexing
>> process backs off to enable the user or application to take full
>> advantage of CPU power. This is also the case even when you have
>> installed a third-party desktop search offering. Once the PC enters an
>> idle state, Windows Search updates the index."
>>
>> Not very useful... Is there a better forum in which to get help?
>
> Not that I know of, hence my last reply.