The issue you are experiencing—where the Power Apps Store app crashes immediately upon launch despite reinstallation and resets—is typically caused by a corrupted local cache, conflicting WebView2 runtime instances, or a failure in the authentication handshake with the Windows Account Manager.
Since you are on Windows 11 Enterprise, there is also a higher likelihood of Group Policy or security software interference. Here are the steps to resolve this, ordered from the most likely to the most complex solutions.
Clear the Specific Power Apps Cache Folders
Simply "uninstalling" the app often leaves behind corrupt local data folders in your user profile.
Close the Power Apps app.
Press Windows Key + R, type %localappdata%, and hit Enter.
Navigate to Packages.
Look for a folder named Microsoft.PowerApps_8wekyb3d8bbwe (or similar).
Rename this folder to Microsoft.PowerApps_8wekyb3d8bbwe.old. This effectively clears the cache while keeping a backup.
Try launching the app again.
Force a WebView2 Repair
Even if your WebView2 is "up to date," the runtime instance used by the Power Apps shell might be corrupted.
Open Windows Settings > Apps > Installed Apps.
Search for Microsoft Edge WebView2 Runtime.
Click the three dots (...) and select Modify.
In the dialog that appears, click Repair.
Once complete, restart your PC and try launching Power Apps.
Check for Account Manager Corruption
Power Apps relies on the Windows Account Manager to authenticate. If your cached credentials for your Microsoft 365 account are corrupt, the app will crash at launch while trying to initialize the login.
Open Windows Settings > Accounts > Access work or school.
If you see the account you use for Power Apps listed there, click it and select Disconnect.
Restart your computer.
Launch Power Apps; it will prompt you to sign in. Log back in with your credentials.
Enterprise-Specific: Event Viewer Logs
Since you are on Windows 11 Enterprise, there might be a specific security policy preventing the app from initializing its container.
Press Windows Key, type Event Viewer, and open it.
Go to Windows Logs > Application.
Look for "Error" entries marked with the Source "Application Error" or "AppModel-Runtime" that match the timestamp of your crash.
If you see an entry mentioning Faulting module name: ... .dll, this will pinpoint the exact file causing the crash (e.g., a specific graphics driver or a security DLL).
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Share
Report
All responses (
Answers (
2,345
