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

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. :)

Hi,

I would suggest you to install that update as well. That update includes a lot of bugfixes.

Regards-

Madeni K N,

I have an optional update, kb2919394, should I install this optional update before doing what you ask?

Hi,

In order to check what could be causing this problem, we want to have a look at the Process Monitor logs from the computers that shows this behavior. Process Monitor is an advanced monitoring tool. I am describing the method of how to collect a log using process monitor below, please read through it first. Once you have followed the steps and have the log file ready, post a reply in this thread and we will collect the log from you via a Private Message.

Before you run Process Explorer, make sure that these criteria are met in the computer where you have the issue (and where we will collect the logs):

1. All available Windows Updates should be installed.
2. The task killing utilities that you might have used to kill the problematic task automatically must be uninstalled from the computer.
3. You must be logged in to the computer using an Administrator user account

First, create a new folder in your C Drive, and name it something like ProcMon.

Then, download and save Process Monitor from this link. A zip file will be downloaded, please extract its contents to the folder you created earlier in your C Drive.

Now, create another folder in your C Drive, and name it to Logs. We will use this folder later to collect the log.

After that, go back to the folder where you have extracted the Process Monitor files, right click on the Procmon executable file and click on Run as Administrator.

If there is any UAC prompts, click Yes.

Process Monitor will now open up. It starts automatically recording events from the computer as and when it starts running. But it does not create a log file that we can read. We will now have to configure Process Monitor to create a log file in the folder we created earlier for this purpose.

In order to do that, first we will have to stop Process Monitor from recording things. Click on this button for that:

Once you click on the button I have highlighted above, it will turn to a button like this:

Once you see that red marked button, you are sure that Process Monitor has stopped recording events. Its time for configuring it to write logs to our folder.

Click File, and click Backing files..  :

Then, in the next pop-up Window, you will have to specify the location for log creation along with a name of the log file that Process Monitor will create. Have a look at this screenshot:

I have used my own location here. I would suggest you to go with C:\Logs\TestLogs.pml if you have created the folder as suggested in the third step above.

Once you have typed in the path, click OK. You will see a prompt like this:

Click OK here as well.

Now close Process Monitor, and close all other open applications and windows.

Now, here is the important part - Next time when you see the issue happening in the computer, Run the Process Monitor program as Administrator (by right clicking on it and then clicking on Run as Administrator) for about 10 seconds. After 10 seconds of running, click on the button I showed in the first image above to stop recording. Then close Process Monitor and open the Logs folder. You should see a file by the name TestLogs in there. Once you have this file, please let us know by replying to this post. We will collect those logs via Private Messages.

We will wait for your responses on this. Let us know if you face any issues, we will be glad to be of help.

Thank you and have a good day.