Skip to content

Published: November 29, 2016 | Applies to:

If Store app not opening in Windows 10 and running App troubleshooter reports unresolved "Windows Store cache may be damaged" message, fix it manually here.

Whenever there happens any issue with Windows Store, users are often suggested to run Windows Store Apps troubleshooter. This built-in troubleshooter helps you to identify the problem with Store and fix it automatically. But sometimes, automatic fixing using this tool may not work, yet you got to know what the issue is so that you can solve it manually.

This post talks about one such issue which is not fixable by Windows Store Apps troubleshooter and it is labelled as “Windows Store cache may be damaged“. We recently came around this problem on a Windows 10 Pro running system for which Store app wasn’t opening and it got stuck at splash screen. Running the troubleshooter found this problem and it seems that we need to fix it manually, as it is quite clear from below screenshot.

FIX Windows Store Cache May Be Damaged In Windows 10

If you’re also reported by this identified and unresolved issue via the Apps troubleshooter, here is how to deal with it.

FIX : ‘Windows Store Cache May Be Damaged’ In Windows 10/8.1/8

FIX 1 – Reset Windows Store In Windows 10/8.1/8

1. Press W8K + R and type C:\Windows\System32 in the Run, hit Enter key. Make sure to replace C: with your system root drive, in case if Windows is installed on some other drive.

FIX Windows Store Cache May Be Damaged In Windows 10

2. In System32 folder, scroll down and find WSReset.exe application. Right click on it and select Run as administrator.

FIX Windows Store Cache May Be Damaged In Windows 10

3. Then hit Yes button in UAC prompt and the application will reset Windows Store without affecting your settings and installed apps, as cleared from below image.

FIX Windows Store Cache May Be Damaged In Windows 10

Once reset operation completes, Windows will automatically open Store app and you can use it now the way you want.

FIX 2 – By Altering Cache Folder In App Directory

1. Press W8K + R and type below mentioned location in the Run and click OK.

C:\Users\<USERNAME>\AppData\Local\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\LocalState

*Substitute C: with system root drive and <USERNAME> with your user account name. AppData folder is hidden by default.

FIX Windows Store Cache May Be Damaged In Windows 10

2. In LocalState folder, if you find Cache folder, rename it Cache.old. Now create new folder and name it Cache. If Cache folder doesn’t exists by default, simply create the empty new folder and name it Cache.

FIX Windows Store Cache May Be Damaged In Windows 10

3. You can now close File Explorer and reboot. After reboot, re-try to run Windows Store Apps troubleshooter, it will again detect the issue but this time it will fix it as well.

FIX Windows Store Cache May Be Damaged In Windows 10

Give another restart to your system and then Store will start working as expected.

Hope this helps!


SHARE: Facebook Google+ Twitter

4 Comments

  • Amazing solution! fix 2 has solved my problem. Many thanks!!!

  • Kapil Arya

    ^^ Glad we could help 😎

  • Still didn’t work for me….I’ve tried EVERYTHING!!! Did everything you suggested, ran the trouble shooter and it’s still says not fixed.

  • Kapil Arya

    ^^ Try to create new user and see if the issue persists on that.

  • Leave a Reply

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

    What's New


    Recent Comments

    • frozen nerd : i also tried uninstalling avast, disabling all startup progr...

      2 hours ago

    • frozen nerd : i have a win 10 home OEM from ASUS tried this and got the ...

      2 hours ago

    • Darren : Thank you, Kapil! The first two netsh commands and reboot ju...

      3 hours ago

    • Charles : I followed your steps but got stuck at step 9 since I couldn...

      9 hours ago

    • Barry : Fantastic! You solved my problem with very clear instruction...

      10 hours ago

    • Keith Fessey : Ok, so whats the difference between the "recovery key" and t...

      14 hours ago


    Windows Group Policy Troubleshooting