Why does Store Broker (wshost.exe) keep killing my CPU?

Anonymous
2014-01-24T23:58:25+00:00

I've got a new Windows 8 machine and, for some reason, the Store Broker keeps pegging my CPU. It seems to pop up every time I do anything with the Windows Store (makes sense) or use some Metro apps (also makes sense). However, for some reason, this process takes up 33% of my CPU and never lets go of it once it starts. This causes the machine to get hot which causes the fan to come on and the combination drastically reduces my battery life (from 11hrs to 3).

Aside from frequently checking for and killing this app, is there anything else I can do about this? Is anyone else having this problem? Is it a misconfiguration on my end? I'm running this on a new Surface Pro 2.

Thanks!

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2014-03-19T01:17:01+00:00

I SOLVED this. At least for myself. It's been a 3-day journey. Argh!

The upshot is this:

Kill Store and Store Broker from task list.

Rename the Cache folder to CacheOld at:

C:\Users(Your User Account)\AppData\Local\Packages\WinStore_cw5n1h2txyewy\LocalState

(Your WinStore_gobblygook might be a different bunch of gobbblygook)

Create an empty folder called Cache.

Solved! For me anyway.

Enjoy,

Ron

PS

I have been at this for days. I've read every article and post everywhere. I have updated graphics drivers, set date and time, run wsreset, sfc /scannnow, created new user account (store did work for new account), app troubleshooter, etc, etc, etc...

Today I just started digging around and looking at dates. I don't have log files to back this up but I believe I broke Store with CCleaner. I'm not sure exactly when the Store broke so this is a best guess but it makes some sense since Ccleaner does clean Store cache.

I also recently installed Tor Browser but my gut is that that was totally unrelated.

I might create a sandbox user and try to break Store with Ccleaner to confirm. But honestly I am tired of this little adventure.

Was this answer helpful?

20+ people found this answer helpful.
0 comments

220 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-02-27T02:35:19+00:00

    I've tried setting up a local account.  Doesn't work on my machine either.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-02-26T22:35:00+00:00

    I read that switching from a Microsoft Account to a local account could fix the problem. It is not the case. The issue happens on either account.

    I kindly reject that statement sir. We seem to have the same symptoms on our machines, with no method on the web fixing anything. For me though, when i create and set up a local account on the same machine i am ABLE to use the store and the high cpu usage is non existent. I just want to point out this dissimilarity everyone, FOR ME, A NEWLY CREATED LOCAL ACCOUNT ON THE SAME MACHINE DOES NOT HAVE THE PROBLEM. 

    I'm not saying you're lying at all, i just want to give as much clarification as possible regarding the issue/symptoms. Thanks.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-02-26T19:18:36+00:00

    Unfortunately, I too jumped the gun thinking it was solved with the optional update as the Store Broker process returned and was back to using 30% of my CPU. In addition the store wont load at all, just stuck in a boot loop. I've tried the previous suggestion of closing it and running wsreset.exe and trying all the steps mentioned here: http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_store/windows-8-store-wont-open/5b7d5c6f-1d09-4963-8ae0-b6c51e835920 to no avail.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-02-26T18:08:45+00:00

    Installing the optional windows update kb2919394 seems to have fixed this problem for me.  Since I've rebooted, I've opened the windows store, updated metro apps and opened all of the native MS metro apps, all without the Store Broker service starting up and eating cpu cycles.  I guess I'll start paying a little closer attention to the "optional" windows updates. :)

    I guess this optional update hasn't worked for me.  After no problem with it all day yesterday, when I booted this morning, the damned thing started again when I opened the mail app.  Sorry if I gave anyone false hope.   I know how annoying this is.

    Was this answer helpful?

    0 comments