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

Anonymous

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!

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

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

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.

0 comments

220 additional answers

Anonymous

2014-02-09T23:51:29+00:00

yea - im getting this as well - takes about 35-50% of my cpu (4770k)

please sort it as im sick of kikking this everytime i bootup
Was this answer helpful?

0 comments No comments
Anonymous

2014-02-08T22:04:41+00:00

Alright ! I think this will be more meaningful to Microsoft Tech people. So I copy and paste the log for a solution.

Is this error related with http://answers.microsoft.com/en-us/windows/forum/windows8\_1-winapps/weather-application/e4630db3-50c2-4cc5-9813-f089494a1145 ??

Log Name: System

Source: Microsoft-Windows-DistributedCOM

Date: 8.2.2014 23:43:39

Event ID: 10016

Task Category: None

Level: Error

Keywords: Classic

User: LOCAL SERVICE

Computer: MonsteR

Description:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID

{C2F03A33-21F5-47FA-B4BB-156362A2F239}

and APPID

{316CDED5-E4AE-4B15-9113-7055D84DCC97}

to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

<EventID Qualifiers="0">10016</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8080000000000000</Keywords>

<TimeCreated SystemTime="2014-02-08T21:43:39.037496200Z" />

<EventRecordID>38259</EventRecordID>

<Correlation />

<Execution ProcessID="768" ThreadID="3416" />

<Channel>System</Channel>

<Computer>MonsteR</Computer>

<Security UserID="S-1-5-19" />

</System>

<EventData>

<Data Name="param1">machine-default</Data>

<Data Name="param2">Local</Data>

<Data Name="param3">Activation</Data>

<Data Name="param4">{C2F03A33-21F5-47FA-B4BB-156362A2F239}</Data>

<Data Name="param5">{316CDED5-E4AE-4B15-9113-7055D84DCC97}</Data>

<Data Name="param6">NT AUTHORITY</Data>

<Data Name="param7">LOCAL SERVICE</Data>

<Data Name="param8">S-1-5-19</Data>

<Data Name="param9">LocalHost (Using LRPC)</Data>

<Data Name="param10">Unavailable</Data>

<Data Name="param11">Unavailable</Data>

</EventData>

</Event>
Was this answer helpful?

0 comments No comments
Anonymous

2014-02-07T18:49:33+00:00

This is happening to me too. Store Broker (WShost.exe) suddenly starts running at 33% CPU utilization.

It is a new Samsung ATIV Book 9 Plus NP940X3G-K04US with Windows 8.1 (64bit).

I just installed KillProcess 4.0 (http://www.tgmdev.be/) to automatically find and kill this process, but this isn't a reasonable long term solution.

I don't expect that it matters, but when I initially started this laptop I logged in via my Windows Live ID, but I shortly thereafter converted to local login only.

I've set my taskbar navigation options to make Windows 8.1 look as much like Windows 7 as possible (and I hope windows 8.2 will look even more like Windows 7) and I never use the Store or any other Windows 8.1 Apps. They can die in a fire as far as I'm concerned.

So anyway, I'm a bit annoyed that this functionality related to Windows 8.1 Apps is trying to run my CPU cores ragged and make the fans on my laptop work overtime.

Please fix it :)

Thanks.
Was this answer helpful?

0 comments No comments
Anonymous

2014-02-07T04:19:14+00:00

end task for store broker (storm hooker) from task manager and retry.
Was this answer helpful?

0 comments No comments