Skip to content

.NET Framework troubleshooting article: Update intro based on discussion #34004

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Feb 15, 2023
Merged

.NET Framework troubleshooting article: Update intro based on discussion #34004

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
404026a
Update intro based on disucssion
adegeo Feb 14, 2023
542a929
Convert markdown image code to new style
adegeo Feb 14, 2023
b40871f
Fix absolute link
adegeo Feb 14, 2023
b9a48c0
Tweak title
adegeo Feb 14, 2023
0e56bbf
merge error section into intro
adegeo Feb 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 11 additions & 17 deletions docs/framework/install/application-not-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,21 +1,15 @@
---
title: Troubleshooting 'This application could not be started'
description: Learn what to do if you see a 'This application could not be started' dialog box.
ms.date: 10/06/2021
title: Fix .NET Framework 'This application could not be started'
description: Learn what to do if you see a 'This application could not be started' dialog box when running a .NET Framework application.
ms.date: 02/13/2023
---
# Troubleshooting a 'This application could not be started' error message
# "This application could not be started" error when running a .NET Framework application

Applications that are developed for .NET Framework typically require that a specific version of .NET Framework be installed on your system. In some cases, you may attempt to run an application without either an installed version or the expected version of .NET Framework present. This often produces an error dialog box like the following:
When you attempt to run a .NET Framework application, you may receive the "This application could not be started" error message. When this error is caused by an installed version of .NET Framework not being detected, or by .NET Framework being corrupted, use this article to try to solve that problem.

![This application could not be started](media/application-not-started/app-could-not-be-started.png)
:::image type="content" source="media/application-not-started/app-could-not-be-started.png" alt-text="This application could not be started dialog box.":::

## Error causes

This error typically indicates one of the following conditions:

- A .NET Framework installation on your system has become corrupted.

- The version of .NET Framework needed by your application cannot be detected.
If you still can't run the application after completing all the steps in this article, then the issue may be caused by some other reason, like a corrupted file system, missing dependencies, or a problem with the application. In that case, you can try contacting the app publisher or post a question to [Microsoft Support Community](https://answers.microsoft.com/) or [Microsoft Q&A](/answers/tags/97/dotnet) for more help.

## How to fix the error

Expand All @@ -25,17 +19,17 @@ To address this issue so that you can run your application, do the following:

1. If the .NET Framework Repair Tool recommends any additional action, such as those shown in the following figure, select **Next**.

![Repair tool recommended changes](media/application-not-started/repair-tool-recommended-changes.png)
:::image type="content" source="media/application-not-started/repair-tool-recommended-changes.png" alt-text="Repair tool recommended changes.":::

1. The .NET Framework Repair Tools displays a dialog box shown in the following figure to indicate that changes are complete. Leave the dialog box open while you to try rerun your application. This should succeed if the .NET Framework Repair Tool has identified and corrected a corrupted .NET Framework installation.

![Repair tool changes complete](media/application-not-started/repair-tool-changes-complete.png)
:::image type="content" source="media/application-not-started/repair-tool-changes-complete.png" alt-text="Repair tool changes complete.":::

1. If your application runs successfully, select the **Finish** button. Otherwise, select the **Next** button.

1. If you selected the **Next** button, the .NET Framework Repair Tool displays a dialog box like the following. Select the **Finish** button to send diagnostic information to Microsoft.

![Unable to resolve the problem](media/application-not-started/repair-tool-no-resolution.png)
:::image type="content" source="media/application-not-started/repair-tool-no-resolution.png" alt-text="Unable to resolve the problem with the repair tool.":::

1. If you still cannot run the application, install the latest version of .NET Framework that's supported by your version of Windows, as shown in the following table.

Expand All @@ -55,7 +49,7 @@ To address this issue so that you can run your application, do the following:

1. In some cases, you may see a dialog box like the following, which asks you to install .NET Framework 3.5. Select **Download and install this feature** to install .NET Framework 3.5, then launch the application again.

![Windows Features dialog box suggesting to install .NET Framework 3.5](media/application-not-started/install-3-5.png)
:::image type="content" source="media/application-not-started/install-3-5.png" alt-text="Windows Features dialog box suggesting to install .NET Framework 3.5.":::

## See also

Expand Down