Windows 8.1 Store Broker (wshost.exe) use high cpu usage

All metro/modern apps works fine on my Surface 2 Pro Windows 8.1, including calendar, mail, and Facebook. However, when I open the Task Manager, I notice that Store Broker (wshost.exe) takes around 31% CPU usage and easily hits 100%, even don’t open any store app. If I try to download new app or game from market or install updates, it just spins the wheels and shows error “Your purchase couldn’t be completed” message. My tablet has been installed Kaspersky Internet Security and also applied lastest Windows updates, and it seems to be a new bug. Any way to resolve the problem?

Many people have experienced the same problem about that Windows 8.1 Store Broker (wshost.exe) process causes the cpu high usage and kills the CPU. Making clean install the OS still can’t fix the issues. Microsoft doesn’t release any related patch for that definitely, so you have to use a temporary fix to get rid of it.

* If the Microsoft Store feature is enabled, the system will be messed by the Store Broker. So you need to disable access to the Store for all users.
1. First sign in as an administrator. Head to Start Screen, type regedit.exe and press Enter.
2. Navigate to the following key:

HKEY_CURRENT_USER\Software\Policies\Microsoft\WindowsStore

3. In the right pane, double-click on the RemoveWindowsStore, and change its value from 0 to 1.

test2

6 thoughts on “Windows 8.1 Store Broker (wshost.exe) use high cpu usage

  1. If we change that value what is the risk to the performance of the Windows Store. As the command ” RomoveWindowStore” seems horrible! :P

  2. There’s finally a solution for this problem. From Ron over at the Microsoft Community…

    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!

    Worked like a charm for me.

  3. From Ron, on Microsoft Community:

    %HOMEDRIVE%
    cd %LOCALAPPDATA%\Packages
    for /D %%F in (winstore*.*) do cd %%F
    cd LocalState
    ren Cache CacheOld
    md Cache

    I’ve tried to help users in other forums that have trouble with this fix and some are just not getting it.

    Copy and paste the block above to notepad and save to the Desktop as FixMe.bat.

    Double-Click the Desktop file and it should fix things.

    (Note: You must End Task in Task Manager on both Store and Store Broker for this to work.)

    (Note: This has no error-checking and makes no accommodation for being run a second time. If you reuse this then you must get rid of the OldCache folder 1st.)

  4. WSHost.exe always penetrate your Firewall, this App will absolutely call to home, let me go out the Firewall, plz plz! This always bugging you?
    Solution:
    In Windows 8.1 Registry you didn’t find “HKEY_CURRENT_USER\Software\Policies\Microsoft\WindowsStore” cause Microsoft isn’t a fool!
    So what to do now…
    Easily change the Name from WSHost.exe to WSHost.ex_ so that it would’nt be find.

    2 Locations:
    c:\Windows\WinStore\WSHost.exe
    c:\Windows\WinSxS\amd64_microsoft-windows-store-client-ui-wshost_31bf3856ad364e35_6.3.9600.16384_none_04418e7c83ec6c33\WSHost.exe

    Caution:
    WSHost.exe belongs to TrustedInstaller and not the Administration Group so you must change the rules. First go to extended Options change the Owner of the file to Administration and then go back and edit TrustedInstaller only to read the file. If you didn’t do that Microsoft change automaticaly the name to the origin.

    This description is only for you if you didn’t use the WinStore!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>