Windows store does not open - missing PurgeCaches

Anonymous
2012-12-02T04:12:22+00:00

Windows store does not open; always goes back to start screen. When I opened, wsreset.exe, then I got this error message...

Windows cannot find 'ms-windows-store:PurgeCaches'. Make sure you typed the name correctly, and then try again.

What should I do? Note that the store actually works in other user account.

Windows for home | Previous Windows versions | Microsoft Store

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
2013-10-18T17:08:25+00:00

This command line solution (power shell to be exact) I found in other thread fix it for me

http://answers.microsoft.com/en-us/windows/forum/windows8\_1-windows\_store/just-updated-to-windows-81-and-the-windows-store/c4cf204d-bd99-426c-b800-9c9125ae739c

Answer

Luis Cantero replied on

-

Please run the following in a Command Window to re-register the Store app:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml

Was this answer helpful?

80+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2014-10-08T02:46:07+00:00

Don't do anything else other than cutting and running this code make sure you do nothing else other than Running this.

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml

I wish i have known this before i re-freshed my wndows 8. What happened to me was that i deleted the packages folder C:\Users\**********\AppData\Local\Packages\.* i thought it was temp files or cache. Microsoft should change the location of this package folder or add recognizable name such as Store Apps Packages.

Thanks for your help.

Was this answer helpful?

80+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2015-04-10T00:54:56+00:00

Running    powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml   at the command line (Search->Run->cmd.exe) is the answer! I've been having this problem for months and this finally fixed it. THANK YOU TO WHOMEVER FIGURED THIS OUT!!!!!!!!!!

Was this answer helpful?

1 person found this answer helpful.
0 comments

141 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-03-01T04:48:53+00:00

    I got this error what should I do ?

    Please Help me out.

    Add-AppxPackage : Deployment failed with HRESULT: 0x80073D02, The package could not be installed because resources it modifies are currently in use.

    error 0x80073D02: Unable to install because the following apps need to be closed Microsoft.MicrosoftEdge_41.16299.248.0_neutral__8wekyb3d8bbwe.

    NOTE: For additional information, look for [ActivityId] cca8326a-b0b2-0003-9816-abccb2b0d301 in the Event Log or use the command line Get-AppxLog -ActivityID

    cca8326a-b0b2-0003-9816-abccb2b0d301

    At line:1 char:134

    • ... temProperty).Path | Add-AppxPackage -Register -DisableDevelopmentMode

    +                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : NotSpecified: (C:\WINDOWS\Syst...ppxManifest.xml:String) [Add-AppxPackage], Exception

        + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-12-15T16:11:23+00:00

    Exact same issue.  The store worked perfectly, allowing me to upgrade to Win 8.1.  It's not working after the upgrade, however.  The live tile informs me about new apps in the store, but when I click the tile, the splash screen comes up for a second before dumping me back into the desktop.

    running wsreset gives me

    ms-windows-store:PurgeCaches

    The remote procedure call failed.

    Was this answer helpful?

    0 comments