QuickBooks Error 1723: Damaged Installer Package Script

QuickBooks Desktop error 1723 means Windows cannot run a script inside the installer package; our engineers explain the triggers and the repair steps.

Error 1723 is a Windows Installer failure, not a fault in your company file. It appears while QuickBooks Desktop is being installed, repaired, updated, or removed, and it means the installer cannot run a component it needs. Your accounting data is not involved. The repair happens on the Windows side, and it follows a short, predictable set of steps.

The message on your screen

The full text reads:

Error 1723: There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.

You will see it when a QuickBooks Desktop installation starts, when a repair or update runs, or when you try to remove the program. Windows words the message slightly differently between versions. The number 1723 does not change, and neither does its meaning.

What does error 1723 mean?

Every QuickBooks Desktop installation runs through the Windows Installer service, msiexec, from an .msi package. That package carries scripts and libraries the installer must execute in order. Error 1723 says one of those libraries could not be launched. Either it is missing from the package, it is damaged, or Windows cannot run it because of permissions or missing runtime components.

QuickBooks itself is rarely the root cause. The message is Windows reporting that the package it received is incomplete, or that the environment it runs in is not whole.

What triggers it?

We see the same handful of causes across cases:

• An interrupted or corrupted download, so the installer package arrives incomplete.
• A Windows Installer service that is stopped, damaged, or no longer registered.
• Missing or broken Microsoft Visual C++ redistributables, which supply many of the DLLs an install needs.
• A setup run without administrator rights.
• Antivirus software blocking or quarantining a file mid-install.

How do you fix error 1723?

Start with the QuickBooks Install Diagnostic tool from the QuickBooks Tool Hub. It automatically repairs many of the Windows components behind this error and settles a fair share of cases on its own. If the error survives that, work through the scenarios below in order.

Scenario 1: The installer copy is damaged

This is the most common trigger.

1. Download a fresh copy of the full QuickBooks Desktop installer. Save it to the local desktop, not to a network drive or USB stick.
2. Right-click the setup file and choose Run as administrator.
3. If the error returns, press Windows+R, type %temp%, clear the folder, and run the installer again.
4. Confirm the download completed in full before reusing a saved copy. A truncated file will fail the same way every time.

Scenario 2: The Windows Installer service is unhealthy

1. Press Windows+R, type services.msc, and press Enter.
2. Locate Windows Installer. If it is stopped, right-click it and choose Start.
3. If the service will not start, or the error persists, open Command Prompt as administrator and run msiexec /unregister, then msiexec /regserver, then restart the computer and try again.

Scenario 3: A runtime library is missing or broken

The DLL named in the message is usually part of the Microsoft Visual C++ redistributables.

1. Open Control Panel and go to Programs and Features.
2. For each Microsoft Visual C++ Redistributable entry, click Change and choose Repair. Restart when prompted and repeat for the remaining entries.
3. Run the QuickBooks installer once more.

Scenario 4: Security software or background processes interfere

1. Press Windows+R, type msconfig, and press Enter.
2. On the General tab, choose Selective startup and load system services only.
3. On the Services tab, tick Hide all Microsoft services, disable the rest, and restart.
4. Temporarily disable third-party antivirus, install or remove QuickBooks, then restore normal startup and re-enable your protection.

Scenario 5: The error appears during an uninstall

A damaged package can block removal as easily as installation. Run the uninstall again under Scenario 4's selective startup. If removal still fails, install the same QuickBooks version over the broken copy so a complete package exists, then uninstall cleanly.

Stopping it from coming back

• Keep Windows Update current; redistributable and installer repairs ride along with it.
• Download the installer once, save the full copy, and keep it until the installation is confirmed working.
• Run installations and removals from an administrator account.
• Exclude installer files from real-time antivirus scanning for the duration of a large install rather than switching protection off and forgetting it.
• Never close an install mid-run or power the machine off during an update. A half-written package invites this error next time.

If the message survives every scenario above, the Windows installation itself is likely too damaged for a clean result on your own. Our engineers carry out QuickBooks Desktop installation and uninstall repairs as remote sessions, and a short examination is usually enough to tell whether the machine needs deeper work.