Microsoft .NET Framework is a Microsoft component used by programs, such as QuickBooks, to integrate with Web applications. (See Microsoft's .NET Framework Overview for more information.) Perform the recommended solutions below if a damaged or missing .NET Framework causes errors such as the following:

Error 1603
Error 1903
Error 1722
Error 1904

 

IMPORTANT

The following troubleshooting steps are for Windows operating system, which is not an Intuit product. The steps can be complex if errors occur while repairing or uninstalling .NET Framework. If you are not comfortable doing these steps on your own, Intuit recommends you consult with your computer's manufacturer or an IT professional.

Solution 1: Download and run the QuickBooks Install Diagnostic Tool

QuickBooks Install Diagnostic Tool is designed to automatically diagnose and fix issues with Microsoft .NET Framework, MSXML, and C++. Prior to performing any manual steps to resolve Microsoft component related issues, it is recommended to run the QuickBooks Install Diagnostic tool to resolve the issue efficiently.

  1. Download the QuickBooks Install DiagnosticTool.
  2. When prompted, save the file to the local Desktop.
  3. Close any open programs, then double-click on the QuickBooksDesktopInstallDiagnosticTool.exe.
    Note: It may take up to 20mins to complete, depending on your internet speed and computer's performance.
  4. Once the diagnostic has completed, restart your computer to ensure proper update of components.

Optional: Please help us gather feedback on how the QuickBooks Install Diagnostic Tool worked out for you.

Solution 2: Update Windows to the latest release

If you are still getting the same error, download and install Windows Updates. Install missing updates pertaining to .NET Framework, MSXML, and C++.
  1. On your keyboard, press the Windows key.
  2. Type Windows Update in the search bar.
  3. Select Check for Updates.
Note: If you encounter any errors performing a Windows Update, contact a qualified IT professional or Microsoft.

Solution 3: Manually repair .NET Framework

HOW12407