Windows 10: WSReset purge cache issue

Here's my setup. I have three accounts, a local admin, an MS account, and a local standard user. I can't run Windows Store properly on my MS account, while it runs fine on the local standard user. A window just briefly flashes before closing. I deleted the MS account, then created another local account. The Store runs perfectly fine, until I changed it to my MS account again and the same issue occurs.

I ran Appsdiagnostic10.diagcab and it advised running a cache reset, which boils down into another issue I'm experiencing. WSReset shows this error. Also, I already ran SFC /scannow, then reran wsreset. Still wsreset throws the same error.





I've been searching around Google for similar issues, but the errors other people encounter are different though.

:)

 

Windows Store Crashes After Update

The wsreset did't help. It says something about purge cache, and then the app didn't start.

 

Windows 10 Store will not open

That did not solve the problem. I ran WSreset again and got the same purge cache error.

 

Welcome to the TenForums @riceBox

While it may yield the same results have you tried the Windows 10 TroubleShooter for Store Apps.

Type troubleshooting into Cortana search bar. The Troubleshooting app should be at top. Click. When Window open, upper left, "View All"

When you start Store Apps trouble shooter click on "Advance" left side of Window, run as administrator, then Next.

 

Yep, it did yield the same issue, with WSReset unable to purge the Store cache.








Also, I already tried re-registering Store via powershell. Still no cigar.

 

Been searching. Not a lot of real ideas other that reset (Windows) and repair Install Windows.

See this link. Reset seem drastic, but an in place repair. Have a read.

Repair Install Windows 10 with an In-place Upgrade

Before performing I would have an Image (Macrium Reflect) so at least you can get back to this point.

Got this from this thread .

How to reinstall Windows Store App and other default Windows apps?


Ken

 

Gonna check this as well on a fresh and updated Win10 VM to see if it would experience the same issue. If it didn't, then I'll start fresh again on the actual machine.