Online

How to Fix QuickBooks Installer Error 1722

How to Fix QuickBooks Installer Error 1722

QuickBooks Desktop, like all other Windows applications, requires additional Microsoft components to function properly. QuickBooks encounters error 1722 during installation and operations if the Microsoft.Net Framework is damaged, outdated, or missing from Windows. Here you will read about how to fix QuickBooks installer error 1722 and if you want to know more about Quickbooks features like how to set up company information in QuickBooks online and the best QuickBooks apps to organize your documents then click on these links.

Other errors in the same scenario include errors 1603, 1903, and 1904. Today, we will discuss QuickBooks error 1722, which is an installer error that appears while installing QuickBooks on computers running Windows operating systems, as well as its causes and resolution, so read the entire article for detailed instructions.

What Causes QuickBooks Installer Error 1722

QuickBooks installation is halted by error 1722 only if the Microsoft.Net Framework is damaged/corrupted or outdated, or if other Windows components such as MSMXL and C++ are outdated. When a user encounters error 1722, he or she will receive the message “Error 1722: There is a problem with this Windows Installer package.” A program that was run as part of the setup did not complete as expected. Contact your package vendor or support staff. On the users’ screen, the action NewCustomerAction1, location: C: UsersJohn1.QUAAppDataLocalTempFP AX MSI Installer.exe, command:” appears. Updating Windows with the most recent updates resolves any issues caused by out-of-date Windows components, and you can easily resolve QuickBooks installer errors such as 1722, 1603, 1903, and 1904. To get a quick resolution, follow the step-by-step instructions provided below.

Steps to Repair QuickBooks Desktop Error 1722

Step 1:  Resolve Installation Errors using QuickBooks Install Diagnostic Tool

Intuit created the QuickBooks Install Diagnostic tool to address issues that prevent the installation of QuickBooks Desktop and installation errors. When you run the Install Diagnostic Tool, it will repair all of the required installation files and components for installing and running QuickBooks. Follow the steps below to quickly resolve QuickBooks error 1722 using the QuickBooks Install Diagnostic Tool.

  • Go to the QuickBooks Tool Hub official download page.
  • Install Tool Hub by saving the installation file to your computer’s desktop.
  • When the download is finished, double-click the downloaded file on the desktop.
  • To complete the installation, follow the instructions provided by the programme installer.
  • Run Tool Hub and select QuickBooks Installation Diagnostic Tool from the Installation Issues tab.
  • QuickBooks Install Diagnostic Tool will automatically scan and repair any installation errors, which may take some time depending on the performance of your computer.
  • Restart Windows and try installing QuickBooks again after the QB Install Diagnostic Tool has finished repairing the QuickBooks installation error.

Step 2: Install the Latest Microsoft Windows Updates

QuickBooks requires a perfect environment to be installed, and if your Windows operating system is acting up, you will be unable to install any application, including QuickBooks. Installing Windows updates ensures that your operating system is free of problems that could disrupt QuickBooks Desktop installation.

  • In the Run Windows text box, press Windows + R and type Control Panel.
  • Enter Windows Update in the top search bar and press Enter.
  • Select Windows Update and then click the Check for Updates button.
  • When Windows detects updates that need to be installed, click Update Now.
  • When prompted, restart Windows.
  • Windows will now install all available Microsoft.NET Framework, C++, and MSMXL updates.
  • Try installing QuickBooks again after Windows has finished installing all of the updates and you have returned to the Desktop screen.

Read Also: How to Fix QuickBooks Error H303