Since wsreset, PowerShell reinstallation, and a Windows reinstall keeping files and apps were already tried, the next supported checks are the standard Microsoft Store recovery steps in this order:
- Make sure Windows is fully updated
- Go to Start > Settings > Update & Security > Windows Update > Check for updates.
- Install any available updates and restart the PC.
- On Windows 10, if the version is lower than 15063, Store issues can occur, but the listed build 19045.3803 is already much newer.
- Check time and location settings
- Incorrect region, date, or time can cause Microsoft Store launch failures.
- Open the settings for language/region and confirm they match the actual location.
- Update Microsoft Store itself
- If Microsoft Store stays open long enough, open it and go to See more > Downloads and updates > Get updates.
- If it crashes before that, continue with the next steps.
- Run the Windows Store Apps troubleshooter
- On Windows 10 only: go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Store Apps > Run the troubleshooter.
- This is specifically recommended for Store launch errors such as 0x80131500, but it is also part of the general Store app troubleshooting flow.
- Repair or reset the Microsoft Store app
- Use the Windows app repair/reset option for the Store app.
- If Repair does not help, use Reset.
- This can remove app data for the Store app, so saved Store app state may be lost.
- Sign in with the Microsoft account used for Store apps
- Microsoft support recommends signing in first, then working through the Store fixes.
- Also confirm the PC is authorized for Microsoft Store apps.
- If the issue affects only Store apps and they start then immediately fail
- On Windows 10, one documented cause is modified default registry or file permissions for Microsoft Store apps.
- That issue is documented for IT professionals when apps begin to start and then return without opening.
- If none of the above works, contact Microsoft Support
- Since cache reset, reinstall attempts, and even a repair-style Windows reinstall did not resolve it, the supported escalation path is Contact Support.