High CPU usage from Windows Explorer process when searching from Start10

from Stardock Forums

Hi,

I've noticed that every time I search from the Start10 menu, there is a spike of high CPU usage by Windows Explorer process for a few minutes.

Funny thing is, I have ticked the option to use Cortana Search instead of Start10 search.

Tests I have done:

* If I open the regular Windows Start menu (using CTRL+Windows Key) and search from there, there is no CPU spike.

* If I search from Windows+S there is no CPU spike.

* If I untick the Cortana search option and use Start10 search, there is a CPU spike.

* If I enable Cortana search then open the Start10 menu with the Windows Key and start typing, the search results are from Cortana, but CPU usage spikes... just like if I was using Start10 search.

* If I search multiple times in quick succession, CPU usage keeps on adding up until it eventually hits 100%.

I see two issues here:

1. Start10 search is causing CPU spike

2. Start10 search is being triggered even if the option to use Cortana search is enabled.

My Windows version is 20H2 build 19042.746.

3,994 views 6 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. I don't see this happening on my system. Might be something unique with your system. Anyway, I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

The issue seems similar to this one: https://forums.stardock.com/495882/page/1/#3755309

From the thread it sounds like the issue is caused by the choice of indexing locations.

I only have Start10Ctrlpnl as an indexing location.

Search results are shown very quickly, so it's odd that Start10 is causing something to happen in the background, which isn't required to show search results. Especially odd that this thing gets triggered when I'm not using the Start10 search feature.

Galactic Civilizations III
Reply #3 from Stardock Forums Top

I have forwarded the issue for Support. I think it best to wait for them to respond on this.

Thank you,

Basj,
Stardock Community Assistant

Reply #4 from Stardock Forums Top

Quoting Pauly550, reply 2

The issue seems similar to this one: https://forums.stardock.com/495882/page/1/#3755309

From the thread it sounds like the issue is caused by the choice of indexing locations.

I only have Start10Ctrlpnl as an indexing location.

Search results are shown very quickly, so it's odd that Start10 is causing something to happen in the background, which isn't required to show search results. Especially odd that this thing gets triggered when I'm not using the Start10 search feature.
End of Pauly550's quote

And what about his solution posted here?

https://forums.stardock.com/495882/get;3755221

Is it something you have tried?

Sean Drohan
Stardock Support Manager

Reply #5 from Stardock Forums Top

Thank you for the report.

In testing we found that it would perform a Start10 search as well as the cortana search the first time a search is performed since login.

We also found search was not terminated on close of menu sometimes.

The next update for Start10 should contain fixes for both these issues.

Reply #6 from Stardock Forums Top

Quoting sdRohan, reply 4

And what about his solution posted here?

https://forums.stardock.com/495882/get;3755221

Is it something you have tried?

Sean Drohan
Stardock Support Manager
End of sdRohan's quote

 

I have reset my search settings as posted in the other thread, but now instead of "Windows Explorer" using high CPU, it is "Microsoft Windows Search Indexer" that uses high CPU instead. Otherwise the symptoms are the same: I start a search, results are shown instantly, but the search will trigger a process that runs in the background and persists after the search is complete.

Quoting Neil, reply 5

Thank you for the report.

In testing we found that it would perform a Start10 search as well as the cortana search the first time a search is performed since login.

We also found search was not terminated on close of menu sometimes.

The next update for Start10 should contain fixes for both these issues.
End of Neil's quote

Thank you!