How to Fix Apps That Open Then Close Immediately in Windows 11 and 10

“Apps open then close immediately” in Windows 11 or Windows 10 can leave you locked out of Microsoft Store apps, Settings, or desktop programs. Corrupted app data is the usual cause, but damaged system files and incorrect permissions can produce the same symptom.

Fix #1: Restart Windows and install updates

A full restart clears stuck app processes. Installing pending Windows and app updates addresses known crashes.

1. Open Start > Power.
2. Select Restart.
3. Open Settings after Windows restarts.
4. Select Windows Update in Windows 11, or Update & Security > Windows Update in Windows 10.
5. Select Check for updates.
6. Install every available update.
7. Restart Windows if prompted.
8. Open Microsoft Store.
9. Select Library.
10. Select Get updates.

Windows Update should report that you’re up to date. Test the affected app again.

Fix #2: Repair or reset the app

The Repair option replaces damaged app components without deleting your data. Reset clears the app’s data, so you’ll need to sign in again.

1. Press Windows + I to open Settings.
2. Open Apps > Installed apps in Windows 11.
3. In Windows 10, open Apps > Apps & features instead.
4. Find the app that closes after opening.
5. Select the three-dot menu beside it in Windows 11, or select the app in Windows 10.
6. Select Advanced options.
7. Select Repair.

A checkmark should appear beside Repair when Windows finishes. Open the app and test it.

If the app still closes:

8. Return to its Advanced options page.
9. Select Reset.
10. Select Reset again to confirm.

The app should return to its default state. This option isn’t available for every desktop program; use Fix #9 if you don’t see it.

Fix #3: Run the Windows Store Apps troubleshooter

Use this fix when Microsoft Store or an app installed through it closes immediately.

1. Open Settings > System > Troubleshoot > Other troubleshooters in Windows 11.
2. Find Windows Store Apps and select Run.
3. In Windows 10, open Settings > Update & Security > Troubleshoot > Additional troubleshooters.
4. Select Windows Store Apps and choose Run the troubleshooter.
5. Apply each recommended repair.
6. Restart Windows when the troubleshooter finishes.

You should see a list of detected problems and their repair status. Test the app after restarting.

Fix #4: Reset the Microsoft Store cache

A damaged Store cache can affect Microsoft Store and several Store apps at once. wsreset.exe clears that cache without uninstalling your apps.

1. Close Microsoft Store.
2. Press Windows + R to open Run.
3. Type wsreset.exe.
4. Press Enter.

A blank Command Prompt window may appear temporarily. It should close automatically, and Microsoft Store should open afterward.

Fix #5: Re-register Microsoft Store

Re-registering reconnects the Store package to Windows. Use this after wsreset.exe fails.

1. Right-click Start.
2. Select Terminal (Admin) or Windows PowerShell (Admin).
3. Select Yes in the User Account Control dialog.
4. Enter this command:

Get-AppxPackage *Microsoft.WindowsStore* |
  Foreach {
    Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"
  }

5. Press Enter.
6. Wait for the command prompt to return.
7. Restart Windows.

PowerShell may show progress briefly. Microsoft Store should remain open when you launch it after the restart.

Fix #6: Repair All Application Packages permissions

Microsoft Store apps run under the built-in All Application Packages security group. If that group loses access to your app package folder, apps can appear briefly and then close.

Changing permissions carries some risk. Create a restore point first, and don’t apply blanket permission changes to C:\Windows, C:\Program Files, or the entire C: drive.

1. Press Windows + R.
2. Enter %localappdata%.
3. Press Enter.
4. Right-click the Packages folder.
5. Select Properties.
6. Open the Security tab.

7. Check whether All Application Packages appears under Group or user names.
8. Select Advanced if the group is missing or lacks access.

9. Select Change permissions if that option appears.

10. Select Add.
11. Choose Select a principal.

12. Enter ALL APPLICATION PACKAGES in the object-name field.
13. Select Check Names.
14. Select OK.

15. Set Type to Allow.
16. Set Applies to to This folder, subfolders and files.
17. Allow the access shown for the group, including reading and running app-package files.
18. Select OK.

19. Review the permissions before applying them.
20. Leave Replace all child object permission entries with inheritable permission entries from this object cleared unless you’re repairing inheritance you know was changed.
21. Select Apply.

22. Restart Windows.

The All Application Packages group should now appear on the folder’s Security tab. If Windows rejects the change or reports access errors, stop instead of taking ownership of system folders.

Fix #7: Restore HKEY_USERS read permission

Try this only when Store apps began failing after a permission change, user-folder move, or disk clone. Back up the registry before editing it.

1. Press Windows + R.
2. Type regedit.
3. Press Enter.
4. Select Yes in the User Account Control dialog.
5. Right-click HKEY_USERS.
6. Select Permissions.

7. Select All Application Packages.
8. Confirm that Allow is selected for Read.

9. If the group is missing, select Add.
10. Enter ALL APPLICATION PACKAGES.
11. Select Check Names.
12. Select OK.
13. Allow Read permission.
14. Select Apply.
15. Select OK.
16. Close Registry Editor.
17. Restart Windows.

Apps should now be able to read the required user registry data. Don’t grant Full Control or copy permissions across other registry hives.

Fix #8: Repair Windows system files

If several unrelated apps close after opening, Windows itself may have damaged components. Run DISM first so System File Checker has a healthy component source.

1. Right-click Start.
2. Select Terminal (Admin).
3. Select Yes in the User Account Control dialog.
4. Run:

DISM /Online /Cleanup-Image /RestoreHealth

5. Wait until DISM reaches 100%.
6. Run:

sfc /scannow

7. Wait for the scan to finish.
8. Restart Windows.

DISM should report that the restore operation completed successfully. SFC will tell you whether it found and repaired corrupted files.

Fix #9: Repair the affected desktop program

Traditional desktop programs don’t use Microsoft Store’s Repair and Reset controls consistently. Repair or reinstall the program through Settings instead.

1. Open Settings > Apps > Installed apps in Windows 11.
2. In Windows 10, open Settings > Apps > Apps & features.
3. Select the affected program.
4. Choose Modify if available.
5. Select the program’s Repair option.
6. Restart Windows after the repair finishes.
7. Uninstall and reinstall the program if no repair option exists.

The program should launch without closing. If games or graphics-heavy programs still crash, install the current graphics driver supplied by your PC or GPU manufacturer.

Fix #10: Check the Settings app policy

Use this fix only if Settings opens then closes immediately. The Local Group Policy Editor is available on Windows Pro, Enterprise, and Education editions.

1. Press Windows + R.
2. Type gpedit.msc.
3. Press Enter.
4. Open User Configuration > Administrative Templates > Control Panel.
5. Double-click Prohibit access to Control Panel and PC settings.
6. Select Disabled.
7. Select Apply.
8. Select OK.
9. Restart Windows.

Settings should remain open after you sign back in. On a work-managed PC, contact your administrator because the domain may reapply this policy.

Fix #11: Use a clean boot to find software conflicts

A clean boot temporarily disables non-Microsoft services and startup programs. If the app works afterward, re-enable items in small groups until the conflict returns.

1. Press Windows + R.
2. Type msconfig.
3. Press Enter.
4. Open the Services tab.
5. Select Hide all Microsoft services.
6. Select Disable all.
7. Open the Startup tab.
8. Select Open Task Manager.
9. Disable each enabled startup app.
10. Restart Windows.
11. Test the affected app.

If the app stays open, a disabled service or startup program caused the crash. Re-enable the items gradually, restarting between tests, then uninstall or update the conflicting software.

Check Event Viewer for Event ID 5961

Event Viewer can confirm an app activation failure, but it doesn’t prove that permissions caused it. Check it when Store apps still close after the earlier fixes.

1. Right-click Start.
2. Select Event Viewer.
3. Expand Applications and Services Logs > Microsoft > Windows.
4. Open the available app-activation or TWinUI operational log.
5. Select Find in the Actions pane.
6. Enter 5961.
7. Select Find Next.
8. Double-click a matching event.

A matching entry may contain output similar to this:

Log Name: Microsoft-Windows-TWinUI/Operational
Source: Microsoft-Windows-Immersive-Shell
Event ID: 5961
Level: Error
Description:
Activation of the app for the Windows.Launch contract failed with error: The app didn't start.

The event confirms that Windows couldn’t activate the app. Use its timestamp to ensure it matches your latest launch attempt.

When the fixes don’t work

Test the app from a new local Windows account. If it works there, your original user profile is damaged. If apps close under every account after SFC, DISM, and a clean boot, use Settings > System > Recovery in Windows 11 or Settings > Update & Security > Recovery in Windows 10 to review Windows recovery options.

Conclusion

Fix #2, repairing or resetting the affected app, usually solves apps opening and closing immediately. Repeated failures across unrelated programs point to damaged Windows files, a broken user profile, or failing storage rather than one bad app. You can also try to fix missing Windows default apps or fix a freezing Windows 10. For more information on troubleshooting Windows issues, visit Help Desk Geek. If you’re experiencing problems with Microsoft Store apps, you can try to fix problems with apps from Microsoft Store or fix problems that block programs from being installed or removed. Additionally, you can try to clear the TPM chip in Windows 11 or pause, defer, or disable Windows updates to resolve any issues related to Windows updates.