Quick answer
QuickBooks error 1722 is a Windows Installer (MSI) failure: the QuickBooks setup started a helper program, and it did not finish. The usual causes are a stopped Windows Installer service, a blocked RPC connection, MSI leftovers from a failed uninstall, or a damaged .NET or MSXML component. Work through the fixes below in order, without registry editing.
What error 1722 means when you install QuickBooks
The full message is: "Error 1722: There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor." Microsoft defines 1722 as a custom action failure, which means a helper program the installer launched crashed, returned an error, or never signaled that it finished. QuickBooks Desktop depends on several of those helpers, including Microsoft .NET Framework and MSXML, so the fault is often in a shared Windows component rather than in the QuickBooks files themselves.
The error can appear in three places, and each one points somewhere different:
| When it appears | What it usually points to |
|---|---|
| During a fresh QuickBooks Desktop install | Windows Installer service state, RPC, permissions in %temp%, or a missing Microsoft component |
| During an update or the PDF converter stage | Antivirus blocking a helper program, or a damaged cached package |
| During an uninstall or a reinstall | MSI leftovers from an earlier failed removal, or files still locked by QuickBooks processes |
Symptoms that come with error 1722
- The installer runs for a while, reaches a specific stage, rolls back, and shows 1722 near the end.
- The same error number appears with a companion code such as 1603, or 1801 when the QuickBooks PDF Converter is the piece that fails.
- An uninstall stalls or fails, and QuickBooks still appears in Programs and Features afterward.
- Reinstalling over the existing installation fails at the same point every time.
- Event Viewer logs an
MsiInstallerfailure at the same minute as the dialog.
Common causes, ranked by how often they occur
- The Windows Installer service is stopped or disabled. If the service cannot start, every MSI-based setup fails. Check it first because the fix takes under a minute.
- RPC is not running. Windows Installer talks to the Remote Procedure Call (RPC) service and the RPC Endpoint Mapper. If either is stopped, helper programs cannot communicate, and 1722 is a common result.
- MSI leftovers from a failed uninstall. When a previous removal was interrupted, Windows keeps a product entry and a cached package that no longer match the files on disk. The next install tries to reconcile them, fails, and rolls back.
- Permissions and locked files. The account running setup needs full control of
%temp%and the QuickBooks folders. QuickBooks processes that survive a normal close keep files locked and produce the same failure. - Damaged Microsoft prerequisites. QuickBooks setup depends on .NET Framework, MSXML, and Visual C++ runtimes. A partially installed or half-updated version blocks the setup that needs it.
- Antivirus and endpoint security. Real-time scanning of every extracted file slows the install, and some products block the custom actions that register DLLs.
- A corrupt installer download. A partial download of
QuickBooks.exefails at the same point every time.
Before you begin
- Back up every company file. Copy the
.QBWfile and its folder to an external drive or another computer. These repairs do not touch your data, but a current backup removes all risk. - Sign in as a Windows administrator. A standard account cannot start services or modify Program Files.
- Have your product and license numbers ready. Find them in the Customer Account Management Portal (CAMPs) or in the original purchase email.
- Budget 45 to 90 minutes. The Install Diagnostic Tool alone can run up to 20 minutes.
Do not use registry cleaners. Every fix in this guide works without touching the registry. Registry cleaners remove Windows Installer keys that Windows and QuickBooks need, which turns a fixable 1722 into a much larger problem.
How to fix QuickBooks error 1722
Restart Windows and close every QuickBooks process
Save your work, then restart the computer instead of reopening QuickBooks. A pending restart from an earlier .NET or Windows update is one of the most common reasons a helper program refuses to run. After the restart, press Ctrl + Shift + Esc, open the Details tab, and end any instance of QBW32.exe, QBDBMgr.exe, QBDBMgrN.exe, or QBCFMonitorService.exe.
Start the Windows Installer and RPC services
Press Windows + R, type services.msc, and press Enter. Confirm that Remote Procedure Call (RPC) and RPC Endpoint Mapper are both Running. Then open Windows Installer, set Startup type to Manual, select Apply, right-click the service, and select Start. If it will not start, open an elevated Command Prompt and run net start msiserver, then read the error text. Restart Windows and retry before moving on.
Clear the MSI leftovers the safe way
Open Control Panel → Programs and Features (on Windows 11, Settings → Apps → Installed apps). If QuickBooks is listed, select it, choose Uninstall/Change, and let the uninstall finish. Then open File Explorer and check the folders where QuickBooks installs:
C:\Program Files\Intuit\QuickBooks (year)orC:\Program Files (x86)\Intuit\QuickBooks (year)C:\ProgramData\Intuit\QuickBooks (year)C:\Users\(current user)\AppData\Local\Intuit\QuickBooks (year)
If a folder remains, right-click it, select Rename, and add .old to the end of the folder name. Renaming preserves the contents but takes the folder out of QuickBooks' path, so the next install starts clean. If Windows returns "access denied", end QBDBMgrN.exe, QBDBMgr.exe, QBCFMonitorService.exe, and QBW32.exe in Task Manager and try again.
Fix permissions on the temp folder
An installer that cannot write to %temp% fails its custom actions and reports 1722. Press Windows + R, type %temp%, and press Enter. Right-click a blank area of the folder and choose Properties → Security → Edit. Select your Windows user name, check Full control in the Allow column, and select OK twice. If your account is not listed, add it first, then grant the same permission.
Run the QuickBooks Install Diagnostic Tool
Close QuickBooks, download the current QuickBooks Tool Hub from Intuit, install it, and open it. Select Installation Issues, then QuickBooks Install Diagnostic Tool, and let it run; it can take up to 20 minutes. The tool diagnoses and repairs the Microsoft components QuickBooks setup depends on, such as .NET Framework and MSXML. Restart the computer when it finishes, then run the QuickBooks installer again. For the wider repair order, see how to fix QuickBooks errors and the error 1603 guide, which shares most of its causes with 1722.
Install QuickBooks in Selective Startup
Press Windows + R, type msconfig, and press Enter. On the General tab, select Selective startup and Load system services. On the Services tab, check Hide all Microsoft services, select Disable all, clear the Hide all Microsoft services check box, check Windows Installer, and select OK. Restart when prompted, run the QuickBooks installer, then open msconfig again, return to Normal startup, and restart.
Download a fresh full installer
Delete the installer file you have and download the full version again from your Intuit account or the Customer Account Management Portal. Right-click the new QuickBooks.exe, choose Run as administrator, and pick Custom and Network Options so you can follow each stage. Failing twice at the same percentage on two separate downloads is a strong sign the problem is environmental, not the file.
Use the Clean Install Tool as the last resort
Back up first. The Clean Install Tool renames QuickBooks folders so the next setup starts from scratch. Back up company files and note your license and product numbers before you run it. Never delete C:\Windows\Installer; Windows needs its cached packages to uninstall or repair programs.
Open the QuickBooks Tool Hub, select Installation Issues, then Clean Install Tool. Choose your QuickBooks product and year, select Continue, and let the tool rename the damaged folders with an .OLD extension. Restart the computer and install QuickBooks from the fresh installer. If your version is not listed or the tool fails, use the manual folder rename from Step 3 instead; that is the same procedure Intuit documents for a reinstall. The clean install guide covers the sequence in more detail.
Verify the fix
- Open QuickBooks Desktop and press F2. Confirm the product name, version, and license number match what you expect.
- Activate the product if prompted, then let QuickBooks check for updates.
- Open a sample company file first. If it opens, open your own company file from its local folder.
- Close and reopen QuickBooks once, and confirm Programs and Features shows a single QuickBooks entry.
- Create a fresh backup of each company file and store it off the machine.
If error 1722 persists
Two failures in a row at the same stage usually mean a Windows component is still damaged. Finish every pending Windows update, including optional .NET updates, restart, and run the Install Diagnostic Tool again. If the uninstall entry is broken and QuickBooks cannot be removed at all, do not force it with a third-party uninstaller; work with an IT professional or Microsoft support on the Windows Installer component itself. Errors in the 1400 range, such as error 1402, follow the same permissions-and-MSI pattern. If setup stalls with a frozen progress bar instead of an error number, the installation stuck guide covers the safe abort and cleanup order.
Prevention
- Keep the full installer for your version in a safe folder so a repair never depends on a new download.
- Install Windows updates before QuickBooks, and restart when Windows asks.
- Add the Intuit program folders to your antivirus exclusions using the vendor's documented method.
- Avoid registry cleaners, PC tune-up tools, and deleting the
C:\Windows\Installerfolder. - Don't cancel an installer that appears paused for a few minutes; canceling during a custom action is the fastest way to create the MSI leftovers that cause 1722.
Frequently asked questions
Is error 1722 a QuickBooks problem or a Windows problem?
It is a Windows Installer message, so the error number comes from Windows even though QuickBooks triggered it. The piece that failed is usually a shared component such as .NET, MSXML, or a helper that an antivirus product blocked. Treat it as an environment problem and the fix becomes predictable.
Can I install QuickBooks without uninstalling the old version?
Usually yes, and an Express install is designed to upgrade over the previous version. If 1722 appears during the upgrade, the old installation may be in a partial state, so uninstall it from Programs and Features first. If the uninstall also fails with 1722, rename the program folders as shown in Step 3 and then install fresh.
Does the Clean Install Tool delete my company files?
No. It renames QuickBooks program and settings folders, not your data. Company files live where you saved them, commonly under C:\Users\Public\Public Documents\Intuit\QuickBooks\Company Files. Back them up before any repair anyway.
Do I need to edit the registry to fix error 1722?
No. Service state, RPC, temp-folder permissions, the Install Diagnostic Tool, and Selective Startup resolve the large majority of 1722 reports without registry changes.
Why does 1722 appear only when I uninstall?
Uninstallments fail when a QuickBooks process still locks a file or when the cached MSI package no longer matches what Windows thinks is installed. Restart Windows, end the QuickBooks processes listed in Step 1, and retry the uninstall once. If it still fails, move to the Clean Install Tool or the manual rename in Step 3 instead of retrying the same uninstall.