Nov 11, 2026
Windows

Windows 11 Apps Won’t Open or Keep Crashing: A Practical Diagnosis Guide

Find out whether a Windows 11 app failure is caused by the app, missing runtimes, corrupted files or a recent change—and try safer fixes first.

Desktop application window with a neutral warning badge
On this page
  1. 1. Capture the exact symptom
  2. 2. Restart and check for a stuck instance
  3. 3. Repair the program if Windows offers it
  4. 4. Update or reinstall from the original publisher
  5. 5. Check for missing Visual C++ dependencies
  6. 6. Review Windows Update timing—without assuming causation
  7. 7. Check Windows Security carefully
  8. 8. Repair Windows components if multiple apps are affected
  9. When you should stop troubleshooting
  10. FAQ

When an application refuses to open on Windows 11, the first question is whether one program fails or several unrelated programs fail. That distinction can quickly separate an app-specific problem from a system-wide issue. Work through the checks below in order; there is no need to replace DLL files, edit the registry or reinstall Windows immediately.

1. Capture the exact symptom

Does nothing happen when you click the program? Does a splash screen appear and close? Is there a missing-DLL message, an access-denied prompt or a crash report? Write down the full error text, application version and whether the failure started after an installation or Windows update. These details matter far more than the generic phrase “won't open.”

2. Restart and check for a stuck instance

Restart Windows once. If the problem returns, open Task Manager and see whether an instance of the application is running but unresponsive. End the task only if it is safe to lose any unsaved work, then relaunch it. Avoid ending unfamiliar system processes.

3. Repair the program if Windows offers it

Go to Settings → Apps → Installed apps. Find the application, open its menu and select Advanced options if present. Choose Repair first. If Repair does not exist, some traditional desktop applications provide Change or Repair through Control Panel → Programs and Features.

Microsoft explicitly notes that repair and reset features are not available for every app. Reset may remove app-specific preferences or local data, so back up anything important before using it.

4. Update or reinstall from the original publisher

Check for a supported application version and install updates using the publisher's updater or official download. If reinstalling, confirm that you have any product license, activation details and user data you need. For games, use the library client's file verification option first.

5. Check for missing Visual C++ dependencies

If the message specifically names MSVCP140.dll, VCRUNTIME140.dll or VCRUNTIME140_1.dll, inspect the application's prerequisites. Install or repair the correct Microsoft Visual C++ Redistributable rather than placing individual DLLs into Windows directories. Match x86/x64/ARM64 to the application, not simply the PC.

6. Review Windows Update timing—without assuming causation

Open Windows Update → Update history and note recent updates. A failure beginning on the same day as an update is a clue, not proof the update is responsible. Check Microsoft's release health reports and the app publisher's incident notices. Avoid uninstalling security updates as a first resort; it may remove protection or introduce other risks.

7. Check Windows Security carefully

Open Windows Security and inspect Protection history if you suspect a quarantine event. Do not restore or exclude a file until you have verified its source. An unfamiliar executable or DLL found in an unexpected location warrants extra caution.

8. Repair Windows components if multiple apps are affected

If core Windows features or several unrelated apps fail, Microsoft's DISM and SFC guidance may be appropriate. Run DISM first, followed by sfc /scannow in an elevated Command Prompt. If the problem persists, use logs and the app publisher's support channels to narrow it down.

When you should stop troubleshooting

On a work PC, stop before changing managed security settings or system services. If the application handles financial or sensitive data, back up data before resets and avoid unverified repair utilities. If you see signs of malware, treat that as a security incident rather than a routine app crash.

FAQ

Can an app crash without a missing DLL? Yes. Corrupted app data, incompatible extensions, permissions and other causes can produce similar symptoms.

Does reinstalling Windows always help? No. It is disproportionate before checking app repair and runtime dependencies.

What should I send to support? The app version, Windows build, exact message, relevant event time and the steps already attempted.

Sources

  1. Repair apps and programs in Windows — Microsoft
  2. Latest Supported Visual C++ Redistributable Downloads — Microsoft
  3. Use System File Checker — Microsoft