When WSReset doesn’t resolve Store Broker issues

What do you do when WSReset.exe (called either as a direct command or from Microsoft’s Apps troubleshooter) doesn’t solve your Windows Store or Store Broker service issue in Winodws 8/8.1?

In my case, Store app didn’t open, WSReset.exe temporarily allowed it to start only to get an empty white screen and no UI responsiveness, while Service Broker service was reported by Task Manager as using around 90% of CPU.

To resolve the problem the solution (found on Microsoft Answers Web site) was simple yet obscure:

  • Stop Store app and Store Broker service processes from Task Manager;
  • Rename Cache folder to Cache.old within %UserProfile%\AppData\Local\Packages\WinStore_cw5n1h2txyewy\LocalState (%UserProfile% path prefix is usually C:\Users\{Username});
  • Create a replacement (new, empty) Cache folder inside LocalState parent;
  • Restart Windows Store app.

About Sorin Dolha

My passion is software development, but I also like physics.
This entry was posted in Computers and Internet and tagged , , , . Bookmark the permalink.

Add a reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s