When a built-in Windows app such as Photos, Calculator, or the Microsoft Store opens to a blank window or closes on launch, the fix is almost always a corrupted app package, an expired Store license, or a damaged system component — in that order of likelihood. Repairing it takes one of three routes: Settings, PowerShell, or a Windows reinstall. Each has a different success rate. Using Microsoft's own app-reset tool in Settings clears the local app data and re-registers the package in about two minutes, and that single action resolves the majority of launch failures.
What Windows Actually Stores When an App Fails to Launch
Every modern Windows app ships as an AppX or MSIX package, and Windows keeps three separate things on disk: the installed package files, a per-user data folder, and a registration entry that ties the package to your account. Any of the three can break independently. A package can install cleanly while its registration entry points at a stale version, which is why the app tile appears but nothing happens when you click it.
The per-user data lives under %LOCALAPPDATA%\Packages, in a folder named after the package family identifier — for the Photos app that is Microsoft.Windows.Photos_8wekyb3d8bbwe. When you reset an app, Windows deletes and rebuilds that folder. When you repair it, Windows leaves the data alone and re-verifies the package files. Those are genuinely different operations, and Microsoft exposes both in Settings for exactly this reason.
Windows 11 shows a Repair button and a Reset button side by side; Windows 10 shows only Reset. That difference matters if you are following a guide written for the other version. Repair preserves settings and sign-in state. Reset wipes them. Try Repair first on Windows 11, because it is non-destructive and often enough.
A failed launch is not the same as a failed update. If the app opens but crashes mid-task, the package registration is probably fine and the problem sits in a dependency — the Visual C++ redistributable, a .NET runtime, or the app's own cache. Those cases respond to different fixes than a launch failure, and the sections below separate them.
Fix 1: Clear and Re-Register the App Through Settings
This is the fastest route and the one to run first. It does not require admin rights, does not touch other apps, and takes under five minutes including the relaunch.
1: Open Settings with Win + I. 2: Go to Apps > Installed apps on Windows 11, or Apps > Apps & features on Windows 10. 3: Find the misbehaving app. Use the search box at the top of the list rather than scrolling. 4: Click the three-dot menu next to the app name and choose Advanced options. 5: If you are on Windows 11 and a Repair button exists, click it and test the app. 6: If Repair does not help, click Reset. Confirm when prompted. 7: Relaunch the app from the Start menu and check whether it opens.
If the Advanced options page is greyed out, the app is either a Win32 program rather than a packaged app, or your account lacks the permissions to modify it. Win32 apps have no Repair or Reset buttons, so move to the reinstall route instead. If Reset completes but the app still fails, note whether the failure changed shape — a blank window turning into an immediate close tells you the package now loads and the crash is downstream.
Running the repair twice in a row rarely helps. If one Reset leaves the app broken, the package files themselves are damaged, and only a re-registration or reinstall will rebuild them from source.
Fix 2: Rebuild the Store's Own Cache When the Store Itself Breaks
The Microsoft Store cannot repair itself through the same Settings page, because the reset option that appears for other apps applies to the Store install but not to its cached catalog. That catalog lives at %LOCALAPPDATA%\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\LocalCache, and clearing it forces the Store to rebuild its index from Microsoft's servers on next launch. The command wsreset.exe does this in one step.
Press Win + R, type wsreset.exe, and press Enter. A blank command window opens for roughly 10 to 30 seconds and then closes; the Store relaunches by itself. Do not close the blank window manually — that interrupts the reset and can leave the cache half-cleared. If the window closes and the Store still shows a grey page or throws error codes starting with 0x8, the problem is the Store install rather than the cache, and the PowerShell re-registration in the next section is the right move.
One edge case catches people: wsreset.exe fails silently if the Store package is not registered for the current user, which happens on machines where the Store was removed and reinstalled under a different account. Check by signing out and back into the same account you use daily before running it.
If the blank window persists past two minutes, kill it and check whether the Windows Update service is running. The Store's cache rebuild queries the update service, and the reset stalls when that service is disabled.
Fix 3: Reinstall a Single App with Winget or PowerShell
When Resetting gets you nowhere, you rebuild the package from source. winget is the cleanest route on Windows 11 and on Windows 10 version 1809 or later with App Installer present, because it uses a package identifier and avoids wildcards that match the wrong app.
| Step | Command | What it does |
|---|---|---|
| Check winget is present | winget --version | Prints a version number if App Installer is installed |
| Remove the package | winget uninstall Microsoft.Windows.Photos | Uninstalls Photos for the current user |
| Reinstall from the Store source | winget install --id 9WZDNCRFJBH4 -s msstore | Pulls the current Photos package by Store product ID |
| Verify | Get-AppxPackage Photos | Lists the package and its install location |
The product ID in that table is specific to Photos. For Calculator the ID differs, and using the wrong one installs the wrong app silently. Look up the correct ID on Microsoft's Store listing page for the app rather than guessing. On Windows 10 where winget is absent, use Get-AppxPackage -allusers | Remove-AppxPackage and then Add-AppxPackage -register against the manifest path — a two-command sequence that fails if the manifest was deleted along with the package.
The failure mode to know: uninstalling a built-in app through PowerShell can remove it for every account on the machine if you include -allusers. On a shared PC, that means other users lose the app too. Drop the switch unless you intend a machine-wide removal.
Microsoft's own support documentation recommends reinstalling through Settings first and PowerShell second; it does not publish a repair script for individual consumer apps, so any third-party "repair tool" claiming to do this is wrapping these same commands.
Fix 4: Run the Built-In Windows App Troubleshooter and DISM
Two Microsoft utilities target corrupt system components that break store apps en masse: the Windows Store Apps troubleshooter and the Deployment Image Servicing and Management tool, usually called DISM. Run them when several apps fail at once rather than one.
The troubleshooter moved in Windows 11 and now sits under Settings > System > Troubleshoot > Other troubleshooters > Windows Store Apps > Run. It checks the app's registration, the Windows Update service state, and the Store cache in sequence, and it applies fixes automatically. It takes about a minute. On Windows 10 the same tool lives under Update & Security > Troubleshoot.
For DISM, open an elevated command prompt and run DISM /Online /Cleanup-Image /RestoreHealth. This command repairs the component store that every packaged app depends on, and it downloads replacement files from Windows Update, so it needs an internet connection. It commonly takes 10 to 20 minutes. Follow it with sfc /scannow, which checks protected system files against the repaired store. Run SFC after DISM, not before — SFC repairs from the component store, so an unrepaired store gives SFC bad source files.
Expect DISM to report "The restore operation completed successfully" and SFC to report either "did not find any integrity violations" or that it repaired files. If DISM returns error 0x800f081f, the source files could not be found, which usually means Windows Update is blocked or the machine is on a metered connection. Reconnect on an unmetered network and rerun before trying anything more drastic.
Fix 5: Correct the Clock, Region, and License Before You Reinstall
A surprising share of "app won't open" cases are licensing failures caused by a wrong system time. Store apps validate licenses against a Microsoft server, and a clock more than a few minutes out causes validation to fail, which the app reports as a launch failure rather than an error message. Check Settings > Time & language > Date & time and confirm Set time automatically is on.
Region matters for a narrower set of apps. Some Store apps check the region setting at launch and refuse to start if the license region does not match, which shows up most often on machines set up in one country and used in another. Changing the region under Time & language > Language & region and restarting can resolve it. The trade-off is that region also affects the Store catalog you see.
The licence itself can be reacquired without a reinstall. Open the Store, go to Library, and click Get updates — this re-queries the license server for every owned package. On a machine with dozens of apps the check takes a couple of minutes. If a specific app shows as owned but not installed, its license is intact and the problem is the local package.
If the account is a local account rather than a Microsoft account, Store apps that require a Microsoft sign-in will fail at launch regardless of package health. Signing into the Store with a Microsoft account once fixes it permanently for that user.
Fix 6: Match the Repair Route to the Failure You Actually See
Not every failure deserves the same fix, and working through them in order wastes time if you skip the diagnosis step. The table below maps symptom to route, based on where the failure happens in the launch sequence.
| Symptom | Most likely cause | First fix to try | Typical time |
|---|---|---|---|
| Tile visible, nothing happens on click | Broken package registration | Settings > Repair, then Reset | 2–5 minutes |
| App opens to a blank white window | Corrupt local cache | Settings > Reset | 2–5 minutes |
| App closes within a second of launch | Missing dependency (VC++ or .NET runtime) | Install the missing runtime | 5–10 minutes |
| Store app fails, Store itself grey or blank | Store cache or Store package | wsreset.exe, then re-register Store | 5 minutes |
| Several apps fail at once | Damaged component store | DISM then SFC | 15–30 minutes |
| App fails only on one user account | Per-user registration | Re-register for that user | 5 minutes |
The blank-window case is distinct from the instant-close case, and people conflate them. A blank window means the package loaded and the UI failed to render, which points at the app's cache. An instant close means the process never got far enough to draw anything, which points at a dependency or a license check.
Dependency failures cluster around apps that render media or use a particular UI framework. Installing the current Microsoft Visual C++ Redistributable from Microsoft's download page resolves a large share of them, and it is harmless if the runtime was already present.
Fix 7: Repair Office, Edge, and Other Non-Store Apps Differently
The Settings Repair button does not exist for desktop programs like Office, Edge, or Adobe apps, and pressing people to look for it wastes time. These programs carry their own repair routines, and where they do not, reinstalling over the existing install without uninstalling first is the correct move.
Office has the most complete built-in repair. Open Settings > Apps > Installed apps, find Microsoft 365 or Office, choose Modify, and pick Quick Repair or Online Repair. Quick Repair takes a couple of minutes and fixes most launch problems; Online Repair downloads a fresh copy and takes 15 minutes or more but fixes corruption Quick Repair cannot reach. Microsoft documents both options and recommends Quick Repair first.
Edge repairs through Settings > Apps > Installed apps > Microsoft Edge > Modify > Repair, which exists because Edge ships as a system component on Windows 11. If that option is missing, download the Edge installer from Microsoft and run it — it repairs in place and preserves your profile.
Adobe and other third-party apps mostly offer a repair option in their own uninstaller or a separate cleanup tool. There is no universal Windows mechanism for them, and a System Restore point from before the breakage is often faster than chasing the vendor's cleanup utility.
Fix 8: When to Stop Repairing and Reset Windows Instead
Repair stops being rational at a specific point, and knowing where that line sits saves hours. If DISM reports unrecoverable corruption after two runs on different networks, if more than a handful of built-in apps fail simultaneously, or if newly created user accounts show the same failures, the damage is at the system level and reinstalling Windows is faster than chasing it.
A cheaper intermediate step exists: Settings > System > Recovery > Reset this PC with the Keep my files option reinstalls Windows while leaving personal files in place. It removes installed programs, so it is not free, but it preserves documents, photos, and downloads. Microsoft's documentation states that Keep my files takes roughly 20 to 40 minutes on a machine with a solid-state drive, though older hardware and large user profiles push it past an hour.
Before any reset, confirm your Microsoft account is linked so that Store apps can be reacquired from Library afterward. Store purchases and free apps both reinstall from that list without repurchase.
The judgment call is cost. A reset costs an evening of reinstalling programs; continuing to troubleshoot a system-level fault costs an unknown number of evenings with no guaranteed end. Past the second failed DISM run, the reset is usually the cheaper option.
Fix 9: Prevent Repeat Failures with These Four Habits
Most repeat failures trace to four habits, and all four are cheap to adopt. The first is letting Windows Update finish rather than interrupting it — a half-applied cumulative update is a leading cause of store app breakage, because it can leave the component store inconsistent until the next update completes the job.
The second is keeping enough free space on the system drive. Store apps unpack and stage updates in a working folder, and Microsoft's guidance for Windows 11 recommends keeping at least 15 to 20 GB free on the system drive; below that, updates can fail mid-write and leave a package half-registered. Check under Settings > System > Storage.
The third is avoiding third-party "PC cleaner" utilities that delete files under %LOCALAPPDATA%\Packages. Those folders hold app registrations and caches, and cleaners that treat them as junk break apps in a way that looks like corruption but is really deletion. If an app breaks right after a cleanup run, this is the first thing to suspect.
The fourth is pausing driver and firmware updates from the manufacturer's utility rather than disabling Windows Update entirely. Updates keep the component store healthy; the failures come from partial application, not from updating at all.
FAQ
Does resetting an app delete my files and photos?
Reset deletes the app's own settings, sign-in state, and local cache, not your documents or photos library. Files that the app saved into your Pictures or Documents folders stay put; what disappears is the app's internal database, so for something like the Photos app you may need to re-point it at your folders. Repair leaves everything intact. Run Repair on Windows 11 first for that reason.
Why does the Repair button not appear for my app?
Repair only exists for packaged apps on Windows 11, and only where the package declares that it supports repair. Win32 desktop programs have no such button at all. If the Advanced options page shows only Move, Reset, or nothing actionable, treat the app as a desktop program and use its own repair routine or reinstall over the top.
Can I repair all built-in Windows apps at once?
Yes, with a single PowerShell line that re-registers every package: Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}. Run it in an elevated window. Expect a wall of red error text for packages that cannot be re-registered — that is normal and often harmless, but it means the command is not a clean sweep.
How long should DISM take, and what if it errors out?
On a healthy machine DISM with RestoreHealth completes in 10 to 20 minutes. Error 0x800f081f means it could not reach a file source, nearly always because Windows Update is blocked, the connection is metered, or a proxy is interfering. Fix the connection and rerun; do not switch to a third-party repair tool, which cannot repair the component store.
Is it safe to uninstall and reinstall a built-in app like Photos or Calculator?
Yes, as long as you reinstall from the Store rather than leaving it removed. Both reinstall cleanly from the Store Library. The risk is uninstalling with the all-users switch, which removes the app for every account on the PC and can require an administrator to restore it for the other users.
Why do apps break again after a Windows update?
A cumulative update can replace shared system files that packaged apps depend on, and if the update does not complete, the app loads expecting the new version and finds the old one. Letting Windows Update finish, then rerunning DISM, resolves it. Repeated breakage after every update points at a failing drive rather than a Windows bug.
Does a third-party repair tool do anything Windows cannot?
Almost never for store apps. The reputable ones call the same DISM, SFC, and PowerShell commands described here, wrapped in an interface. Some add registry cleaning that can break app registration further. If a tool claims to repair Windows apps, ask which command it runs; the answer is usually one of the four already covered.
What if only one user account has the problem?
Per-user failures mean the package is installed machine-wide but the registration is broken for that profile. Sign in as the affected user and re-register the app from an elevated PowerShell in that session. If a brand-new account works fine, the original profile's app data is the culprit, and copying the profile to a new account is sometimes faster than repairing it.