An app that opens and then suddenly closes can make reinstalling it seem like the obvious solution. Often, however, the installation itself is not the real problem.

A Windows app can crash because of an outdated app, a Windows compatibility problem, damaged app data, a driver issue, interference from another program, corrupted Windows system files, or a problem specific to the user’s Windows account. Reinstalling may fix some of these situations, but it can also waste time if the underlying cause remains.

The better approach is to identify when the crash happens and whether other apps are affected, then work through the least disruptive fixes first.

This guide focuses on Windows 11. Some Windows 10 menus are different, and Microsoft ended support for Windows 10 on October 14, 2025.

First, identify what kind of crash you are dealing with

Before changing anything, reproduce the problem once and pay attention to what happens.

There are several useful patterns:

• The app never opens: The problem may involve compatibility, damaged installation files, missing components, permissions, or another Windows-level issue.
• The app opens but closes after a few seconds: Corrupted app data, an incompatible component, a driver conflict, or another background process may be involved.
• The app crashes only when performing one task: For example, it may crash when opening a particular file, printing, playing video, using a camera, or connecting to an account. That points toward a specific feature or dependency rather than necessarily a damaged installation.
• Several unrelated apps are crashing: Investigate Windows, drivers, available resources, security software, or system-file problems before reinstalling individual apps.
• The problem began immediately after a Windows or app update: Compatibility or an update-related change becomes more relevant.
• Only one Windows account has the problem: The app’s user-specific settings or profile data may be involved.

This distinction matters because reinstalling one application cannot normally correct a problem affecting Windows itself or several unrelated programs.

1. Restart Windows before making bigger changes

A full restart is a simple diagnostic step, not just a generic troubleshooting ritual.

Close the affected application and select Start > Power > Restart.

After Windows starts again, open the app before launching a large number of other programs.

If it works after the restart and continues working normally, the problem may have been temporary. If it crashes again in exactly the same situation, continue troubleshooting rather than repeatedly restarting the computer.

Microsoft also recommends restarting as an early troubleshooting step for Windows application problems.

2. Check whether Windows and the app are up to date

An app and the version of Windows it runs on need to remain compatible. This is especially important if the crashing started after a Windows upgrade or after the application had not been updated for a long time.

Check Windows Update

On Windows 11, open:

Settings > Windows Update

Select Check for updates and install available updates when appropriate. Restart Windows if requested.

For Microsoft Store applications, Microsoft also recommends checking for Windows updates and updating the Store itself.

Check the application itself

If the app has its own updater, open its Help, About, Settings, or update section and check for a newer version.

For a Microsoft Store app:

Microsoft Store > Library > Get updates

Microsoft specifically recommends using the Store’s Library to obtain available app updates.

What the result tells you

If an update fixes the crash, avoid reinstalling the application simply because it previously failed. The problem was more likely related to the version combination or a defect that the newer software corrected.

If everything is already current and the crash remains, move to the next diagnostic step.

[Internal link opportunity: related article about Windows Update problems and troubleshooting failed updates]

3. Check whether the problem affects one app or several

This is one of the most useful tests because it changes the direction of the investigation.

Open two or three unrelated applications that you normally use.

For example, if a photo editor keeps crashing, try a browser, Notepad, and another ordinary desktop application.

If only one app crashes

Concentrate on that application:

• its settings
• its stored data
• its compatibility
• its installation
• its required drivers or components
• software that interacts specifically with it

If several unrelated apps crash

Do not immediately reinstall each application.

Instead, investigate:

• Windows updates
• graphics or other relevant device drivers
• Windows system-file integrity
• third-party security or system-management software
• background software conflicts
• unusual system instability

This approach prevents you from treating a Windows-level problem as a collection of separate application problems.

4. Look at what the app was doing when it crashed

A reproducible crash gives you more information than a random crash.

Try to identify the exact action that triggers it.

For example:

The app opens normally but crashes whenever I open a particular document.

That is different from:

The app crashes immediately after I launch it.

If the crash occurs while opening one particular file, test another file of the same type. If other files open normally, the original file or the application’s handling of that file deserves attention.

If the crash happens whenever you use a feature such as printing, video playback, graphics acceleration, a camera, or an external device, investigate that feature before reinstalling the entire application.

Write down the exact error message if Windows displays one. Also note whether the application becomes unresponsive first or simply disappears.

That information can become important if you eventually need the software publisher’s support team.

5. Use Windows’ built-in Repair option before Reset

Windows 11 provides a repair option for some applications without requiring a complete reinstall.

Go to:

Settings > Apps > Installed apps

Find the affected application, select the More option next to it, then choose Advanced options if that option is available.

Select Repair.

Microsoft notes that Repair is not available for every application. When supported, it is intended to fix application problems without removing the app.

Why Repair should come before Reset

Repair is a relatively low-impact test.

If the app starts working after Repair, open it and perform the action that previously caused the crash. Do not assume that simply reaching the main window proves the problem is fixed.

For example, if the crash originally occurred while exporting a file, perform a small test export.

If the same crash returns, continue to the next step.

6. Be careful with Reset because it can remove app data

If Repair is unavailable or does not solve the problem, Windows may offer Reset in the same Advanced options area.

Reset is different from Repair.

Microsoft explains that Reset can return an app to its default state and may remove app data.

Before selecting it, check whether the application stores anything locally that you need, such as:

• locally saved settings
• unsynced work
• custom templates
• locally stored profiles
• application-specific data

The exact effect depends on the application, so check the software publisher’s documentation if the app contains important data.

After Reset, open the application and test the original failure point.

If the app works after Reset but loses a configuration you depended on, restore the settings gradually. Reintroducing everything at once can make it difficult to identify which setting caused the original problem.

7. Check whether Windows recently changed

Timing is a valuable troubleshooting clue.

Ask yourself:

Did the crashing begin after a Windows update, Windows upgrade, driver update, or major application update?

Older applications can develop compatibility problems after a newer Windows version changes system behavior, security features, or other underlying components. Microsoft provides a Program Compatibility Troubleshooter for older applications that have problems on current Windows versions.

On Windows 11, you can find the compatibility troubleshooter under:

Settings > System > Troubleshoot > Other troubleshooters

Look for Program Compatibility Troubleshooter when it is available.

This is particularly relevant when:

• the application used to work correctly
• Windows was recently upgraded
• the application is older
• the crash appears related to compatibility rather than one specific document or task

If the app is supplied by a company, also check that publisher’s support documentation for the supported Windows versions.

8. Check graphics and other relevant drivers

Some applications depend heavily on particular hardware components.

Graphics-intensive software is an obvious example, but other programs can also depend on device drivers for printing, audio, networking, cameras, storage devices, or specialized hardware.

If the crash happens when using a particular hardware-related function, check the corresponding driver rather than assuming the application installation is damaged.

For example, if a program consistently crashes when rendering video or displaying 3D content, investigate the graphics driver.

Windows provides driver management through Device Manager, while Windows Update can also provide driver updates. Microsoft recommends keeping device drivers current when addressing compatibility problems.

Do not install random driver packages from unofficial download sites just because a search result promises a newer driver. When possible, use Windows Update or the hardware manufacturer’s official support site.

[Internal link opportunity: related article about Windows graphics or driver troubleshooting]

9. Check whether security software is interfering

Security software can interact with applications, particularly when a program accesses files, networks, protected folders, or other resources.

That does not mean you should immediately disable antivirus protection.

First, check Windows Security for alerts and review whether the affected application or one of its files has been identified as a threat.

Open:

Windows Security > Virus & threat protection

From there, you can review current threats and protection history and run a scan. Microsoft also provides Quick scan, Full scan, and Microsoft Defender Offline options.

If you suspect malware, a security scan is more appropriate than simply reinstalling the application.

Do not create an antivirus exclusion just to make the crash disappear

Adding an exclusion means Microsoft Defender Antivirus will no longer check the excluded item with real-time protection. Microsoft explicitly warns that exclusions can leave a device and its data more vulnerable.

If security software appears to be blocking legitimate software, check the application’s official support documentation or the security product’s documented troubleshooting process rather than permanently weakening protection.

10. Check Windows system files if multiple applications are failing

If several unrelated programs are crashing, Windows system-file corruption becomes more relevant.

Microsoft provides the Deployment Image Servicing and Management (DISM) tool and System File Checker (SFC) for repairing Windows components and protected system files.

Open Command Prompt as administrator and run:

DISM.exe /Online /Cleanup-image /Restorehealth

Wait for the operation to complete.

Then run:

sfc /scannow

Wait until the verification reaches 100 percent.

Microsoft recommends running DISM before SFC in this repair process.

How to interpret the result

If DISM completes successfully and SFC reports that it repaired corrupted files, restart Windows and test the affected applications again.

If SFC reports that it found no integrity violations, that does not prove the application itself is healthy. It simply makes Windows protected system-file corruption less likely as the immediate explanation.

If the commands report errors that they cannot repair, follow Microsoft’s current repair guidance rather than repeatedly running the same commands.

11. Use Event Viewer when you need evidence about the crash

If the application continues crashing, Windows may have recorded useful information about the failure.

Search Windows for:

Event Viewer

Open it and go to:

Windows Logs > Application

Look around the time of the crash for an Application Error event.

Microsoft’s documentation identifies Event ID 1000 as an actual application crashing event and notes that it can contain details such as the faulting application and faulting module.

You do not need to understand every field.

Look for information such as:

• the application name
• the time of the crash
• the faulting application
• the faulting module
• the exception code

Why this information matters

Suppose the same module appears every time the application crashes. That can provide a useful lead for the software publisher or support technician.

On the other hand, if the crash information changes from one attempt to another, the problem may require broader investigation.

Do not delete Event Viewer logs just because you see errors. An error entry is evidence to investigate, not automatically proof that Windows is damaged.

12. Test for interference from background software

If the app works normally after a clean boot, another startup application or service may be interfering with it.

Microsoft’s clean-boot procedure starts Windows with essential drivers and startup programs so that software conflicts can be isolated.

This is a more advanced test, so use it when simpler checks have not explained the problem.

The general process is:

1. Search for System Configuration or run msconfig.
2. Open the Services tab.
3. Select Hide all Microsoft services.
4. Disable the remaining services.
5. Open Task Manager from the Startup tab.
6. Disable the relevant enabled startup items.
7. Restart Windows and test the affected application.

Microsoft warns that a clean boot can temporarily remove some functionality, so keep track of what you change. After testing, return Windows to normal startup.

What the clean-boot result means

The app works in a clean boot:
A background application or service is a strong suspect. Re-enable items systematically rather than turning everything back on at once. This helps isolate the conflict.

The app still crashes:
The problem is less likely to be caused by interference from another startup program or service. Continue with application-specific, driver, Windows, or publisher troubleshooting.

[Internal link opportunity: related article about Windows startup programs and background processes]

13. Check for malware when the crash is accompanied by other warning signs

An ordinary application crash does not automatically mean malware is involved.

However, investigate security more seriously if the crashes appear alongside unusual symptoms such as unexpected pop-ups, unexplained system slowdowns, unfamiliar programs, browser redirects, or other suspicious behavior.

Microsoft recommends using Windows Security and Microsoft Defender scans when malware is suspected. Microsoft Defender Offline can run after a restart without loading the normal Windows environment, making it harder for persistent malware to hide.

Save your work before starting an Offline scan because Windows will restart the PC.

Do not download an unknown “crash fixer” or registry cleaner simply because it claims to detect the cause. Use Windows’ built-in tools and the application’s official support resources first.

14. Consider whether the Windows user profile is involved

If the application crashes for one Windows account but works normally under another appropriate test account, that is a useful clue.

It suggests that user-specific application settings or profile data may be involved rather than the entire Windows installation.

Do not immediately delete the original profile.

Instead, use the result as diagnostic information and check the application’s documentation for how it stores and resets user settings. For applications containing important local data, make sure that data is backed up before removing or resetting anything.

15. When reinstalling the application finally makes sense

Reinstalling becomes more reasonable when you have evidence that the problem is specific to the application and the less disruptive repairs have not fixed it.

For example:

• only one application crashes
• Windows and the application are updated
• Repair did not solve the problem
• Reset did not solve it or is unavailable
• other applications work normally
• relevant drivers appear healthy
• Windows system-file checks do not reveal a problem
• the application publisher recommends reinstalling

Before uninstalling, check whether the application stores important local data or requires a license, activation code, account sign-in, or exported settings.

Then uninstall it through the normal Windows or application-specific process and obtain the installer from the publisher’s official website or Microsoft Store when applicable.

Avoid third-party download sites offering modified installers.

After reinstalling, do not immediately restore every extension, plugin, custom setting, or add-on. Start with the clean installation and reproduce the original problem first.

That makes the result much more informative.

A practical decision path

When an app keeps crashing, the troubleshooting sequence can be simplified to this:

Only one app crashes?

→ Restart Windows
→ Update Windows and the app
→ Test the exact action that causes the crash
→ Try Repair
→ Consider Reset after checking its data consequences
→ Check compatibility and relevant drivers
→ Check Event Viewer
→ Reinstall if the evidence points to the application itself

Several unrelated apps crash?

→ Restart Windows
→ Install available Windows updates
→ Check drivers and recent system changes
→ Run DISM and SFC
→ Check for background software conflicts
→ Check Windows Security
→ Investigate broader Windows stability problems

The crash began immediately after a major Windows change?

→ Check compatibility
→ Check for application updates
→ Check relevant drivers
→ Review Microsoft’s current recovery and troubleshooting options rather than repeatedly reinstalling the application.

What you should not do

Do not reinstall every application at once

If several applications are crashing, mass reinstallation can hide the actual cause and consume significant time.

Do not delete application folders manually

An application’s files may be stored in several locations, and manually deleting folders can remove useful configuration or data without properly removing the software.

Use the application’s documented uninstall process.

Do not edit the Registry as a first-line fix

Registry changes can affect Windows and applications beyond the program you’re trying to repair. If a documented Microsoft or software-publisher procedure requires a Registry change, follow that procedure carefully and create the recommended backup first.

Do not disable antivirus permanently

If security software is involved, determine why it is interfering rather than leaving the PC unprotected. Microsoft warns that disabling protection or adding exclusions can increase security risk.

Do not reset Windows because one application crashes

Windows recovery options become progressively more disruptive. Microsoft recommends starting with less disruptive recovery methods and warns that some recovery actions can result in data loss.

A single unstable application is normally not enough reason to reset the entire operating system.

How to verify that the problem is actually fixed

A successful launch is only the first test.

Reproduce the action that originally caused the crash.

For example:

• If opening a specific file caused the crash, open that file or another representative file.
• If exporting caused the crash, perform a small export.
• If printing caused the crash, send a test document to the printer.
• If the application crashed after several minutes, leave it running long enough to reproduce the original condition.
• If the crash happened while signing in, complete the sign-in process and use the affected feature.

Then restart Windows once more and test the application again.

If the application works both immediately after the fix and after another normal restart, the result is more meaningful than a single successful launch.

If the crash returns, note exactly what you did immediately before it happened. That new observation may point toward the next diagnostic step.

When to stop troubleshooting yourself

Consider contacting the application’s publisher when:

• the application consistently crashes while other software works normally
• you can reproduce the crash reliably
• reinstalling does not help
• Event Viewer provides repeatable crash information
• the application requires a specialized driver, plugin, or service
• the problem affects important work and you cannot safely experiment further

Give support as much useful information as possible:

• Windows version
• application name and version
• when the problem started
• what action triggers the crash
• exact error messages
• whether other applications are affected
• what troubleshooting steps you already tried
• relevant Event Viewer information

If the computer is managed by an employer or school, contact the organization’s IT department before changing system configuration. Microsoft also recommends contacting the program manufacturer when application-specific troubleshooting does not resolve the problem.

How to reduce repeat crashes

There is no single setting that prevents every application crash, but a few habits make future problems easier to diagnose.

Keep Windows and regularly used applications updated. Use official software sources. Keep appropriate security protection enabled. Maintain backups of important work, particularly when an application stores files locally.

Also pay attention to when problems begin. If an application becomes unstable immediately after an update, driver change, new plugin, or new security product, record that change. It gives you a much stronger starting point than simply knowing that “the app stopped working.”

The most useful troubleshooting habit is to change one significant thing at a time and test the original failure condition afterward. That turns a frustrating crash into a problem you can progressively narrow down.

Frequently Asked Questions

Why does an app keep crashing but other Windows apps work?

When only one application is affected, the problem may be specific to that application’s files, settings, compatibility, dependencies, or interaction with a particular feature. Start with updates, the application’s Repair option, and the exact action that triggers the crash before considering a reinstall.

Should I repair or reset a Windows app first?

Use Repair first when it is available. Microsoft describes Repair as an option for fixing supported apps without losing their data. Reset is more disruptive because it can return the app to its default state and may remove app data.

How can I tell whether Windows itself is causing apps to crash?

If several unrelated applications are crashing, look beyond one application. Check Windows updates, relevant drivers, background software, Windows system files, and security issues. DISM and SFC can check and repair certain Windows component and protected system-file problems.

Can an antivirus program cause an application to crash?

Security software can sometimes interfere with software, but you should not assume that is the cause or disable protection immediately. First check Windows Security for alerts and scan results. If there is a legitimate compatibility problem, follow the security product’s or application’s official troubleshooting instructions. Microsoft warns that exclusions reduce the files and processes Defender checks.

What is the point of checking Event Viewer?

Event Viewer can provide evidence about an application failure. Application Error events can identify the affected application and, in some cases, the faulting module and exception information. That information can help distinguish an application-specific problem from a broader Windows issue and can be useful when contacting software support.

Sources Used:

• Microsoft Support — Repair apps and programs in Windows: Supported the current Windows 11 Repair and Reset workflow and the distinction between Repair and Reset.
• Microsoft Support — Fix problems with apps from Microsoft Store: Supported the current Microsoft Store troubleshooting sequence, including Windows updates, Store updates, Repair/Reset, and reinstalling Store apps.
• Microsoft Support — Make older apps or programs compatible with the latest version of Windows: Supported compatibility troubleshooting and the Program Compatibility Troubleshooter.
• Microsoft Learn — The application or service crashing behavior troubleshooting guidance: Supported the use of Event Viewer and Application Error Event ID 1000 when investigating application crashes.
• Microsoft Support — How to perform a clean boot in Windows: Supported clean-boot testing and the interpretation of results when background services or startup programs interfere with an application.
• Microsoft Support — Using System File Checker in Windows / Use the System File Checker tool: Supported the current DISM and SFC repair procedure and the recommended order.
• Microsoft Support — Virus and Threat Protection in the Windows Security App: Supported current Windows Security scanning options and the warning about security exclusions.
• Microsoft Support — Recovery options in Windows: Supported the principle of using less disruptive recovery options before more disruptive Windows recovery actions and the associated data-loss considerations.