Quick answer

A QuickBooks update failed message means the patch never finished installing: the download was incomplete, Windows blocked the files, or a background process held them open. Reset the update, clear the damaged download folder, install pending Windows and .NET updates, then pull the patch again with Help → Update QuickBooks Desktop. If the installer still stops, reinstall QuickBooks Desktop.

What a failed QuickBooks Desktop update means

QuickBooks Desktop downloads product and payroll tax table updates through the QuickBooks File Copy Service, then runs a Windows Installer package to apply them. When any stage breaks, QuickBooks reports that the update failed, often with a 15XXX code such as 15106 or 15223.

Three different things can fail. A product update changes the QuickBooks program. A payroll tax table update only refreshes tax rates and forms. A pending Windows update is Microsoft's job and can block QuickBooks until Windows restarts. Fixing the wrong one wastes an afternoon.

QuickBooks Online works differently: it updates on Intuit's servers and has no patch to download. This guide applies to QuickBooks Desktop Pro, Premier, Enterprise, Accountant and Desktop Payroll; a failed bank feed or payroll sync in QuickBooks Online is a connection issue, not an update.

Symptoms of a failed update

  • The download finishes, then QuickBooks reports that the update did not complete successfully, or names a 15XXX code.
  • QuickBooks restarts and still shows the old release date under Help → Update QuickBooks Desktop.
  • Payroll shows an outdated tax table and will not process paychecks until the update succeeds.
  • The updater stalls at "Downloading" or "Installing" and never reaches the restart prompt.
  • The failure repeats at the same percentage on every retry, which points at a damaged file in the download folder.

Common causes, ranked

  1. A partial or damaged download. Antivirus, a proxy or an interrupted connection can leave an update file incomplete but apparently valid, and the leftovers fail every retry.
  2. Permissions. QuickBooks or the updater was launched without administrator rights, so the patch cannot write to the program or Components folders.
  3. Locked files and background processes. QBW32.exe, QBUpdate.exe, the database manager or an open company file can hold the exact file the patch needs to replace.
  4. Pending Windows updates and damaged .NET. Intuit lists damaged Windows files as a standard cause of 15XXX errors; a pending restart or broken .NET Framework stops the installer.
  5. Firewall, antivirus or the QuickBooks File Copy Service. Intuit calls out firewall settings and a disabled File Copy Service as update blockers.
  6. Wrong system date and time. An incorrect clock breaks the secure connection used to validate the download.
  7. Damaged Internet connection settings. Corrupted proxy settings in QuickBooks or in Windows block the update servers.
  8. A signature that cannot be verified. If QuickBooks cannot validate the digital signature, the patch is rejected.

Before you begin

Set aside 20 to 40 minutes and have these ready:

  • Your Windows administrator sign-in. Every fix below needs it at least once.
  • Your QuickBooks version and release: press F2 in QuickBooks and write down the product and release.
  • A current backup of every company file, especially before the reinstall step.
  • If you run QuickBooks Desktop Payroll, download the latest tax table after each troubleshooting step so a half-fixed installation never processes payroll with stale rates.

Back up before you rename update folders. The steps below rename damaged download files, and the last step reinstalls QuickBooks. Neither touches your company file when you follow the order, but a fresh backup makes the work reversible.

How to fix a failed QuickBooks Desktop update

1

Confirm what failed and check the clock

Press F2 in QuickBooks to record the version and release you are on, then note the exact error code or message. Right-click the clock in the taskbar, choose Adjust date/time, and set the correct date and time if either is wrong.

An incorrect clock is Intuit's first listed cause for several update errors. Close and reopen QuickBooks after correcting it, then retry the update once.

2

Run QuickBooks as administrator and retry

Close your company file and QuickBooks completely. Right-click the QuickBooks Desktop icon and choose Run as administrator, then answer Yes when Windows asks for permission. Go to Help → Update QuickBooks Desktop, open the Update Now tab, and select Get Updates.

If that run fails with the same code, the downloaded files are probably damaged, so continue.

3

Reset the update and download a clean copy

Still in QuickBooks, go to Help → Update QuickBooks Desktop → Update Now. Select the Reset Update checkbox, then select Get Updates. The reset clears the update state so QuickBooks downloads the patch from scratch instead of reusing the damaged copy.

When the download completes, close and reopen QuickBooks, return to Help → Update QuickBooks Desktop, open the Overview tab and select Update Now.

4

Rename the damaged update folders

Rename, do not delete. Adding .old to a folder name is reversible; deleting it is not. Keep QuickBooks closed for this step so no process holds the files.

Press Windows + E to open File Explorer and go to C:\ProgramData\Intuit\QuickBooks XX\Components, where XX is your version year. Right-click the Components folder, choose Rename, and add .old to the name. QuickBooks rebuilds this folder on the next update.

If the failure continues, check the program folder. For 64-bit QuickBooks 2022 and later, look in C:\Program Files\Intuit\QuickBooks(year)\Components; earlier 32-bit releases use C:\Program Files (x86)\Intuit\QuickBooks(year)\Components. Inside, rename the downloadqbXX folder (for example, downloadqb21 for the 2021 release) by adding .old, then restart QuickBooks and download the update again.

5

Install pending Windows updates and repair .NET

Open Settings → Windows Update, install everything pending, and restart. A pending update can block QuickBooks from replacing shared components.

If update errors continue after the restart, repair Microsoft .NET Framework. Open Control Panel → Programs and Features → Turn Windows features on or off. For .NET Framework 4.5 (or later) and .NET Framework 3.5 SP1, clear the checkbox, choose OK, restart, then reselect it and restart again. If Windows refuses the repair, run the Microsoft .NET Framework Repair Tool from Microsoft's download page.

6

Clear firewall, antivirus and Internet blocks

In QuickBooks, open Help → Internet Connection Setup, choose Use my computer's Internet connection settings to establish a connection when this application accesses the Internet, and select Next. Open Advanced Connection Settings, and on the Advanced tab select Restore Advanced Settings, then OK and Done.

Confirm the QuickBooks File Copy Service is running in services.msc and is not disabled. Add the QuickBooks program folder and the downloadqbXX folder to your antivirus exclusions using the vendor's documented method, and make sure your firewall allows update traffic. Disable download accelerators while you test.

7

Run Quick Fix my Program and the Install Diagnostic Tool

Install the QuickBooks Tool Hub, open it, and select Program Problems → Quick Fix my Program. The tool shuts down lingering QuickBooks processes and runs a quick repair.

Then select Installation Issues → QuickBooks Install Diagnostic Tool and let it run; it can take up to 20 minutes. Restart Windows when it finishes. The QuickBooks Tool Hub guide explains the other tools if you need them later.

8

Install the update manually from Intuit

If the built-in updater still fails, download the manual update for your exact version from Intuit's official Downloads & Updates page, save it to a local drive, right-click it and choose Run as administrator. A manual update bypasses the File Copy Service download stage, clearing the partial-download class of failures.

If the manual update ends with error 1328 or error 1603, work those paths instead of retrying: error 1328 means the patch could not apply to a file, and error 1603 is a fatal installer condition. For a payroll tax table that still will not update, work the payroll tax table troubleshooting steps after the program update succeeds.

9

Reinstall QuickBooks Desktop as the last resort

When updates and repairs keep failing, reinstall QuickBooks Desktop. Open Control Panel → Programs and Features, select your QuickBooks version, and choose Uninstall/Change → Remove. Restart Windows, then reinstall from a fresh download as administrator and reapply updates.

A reinstall does not touch your company files, but it resets program folders and preferences, so keep your backup. If QuickBooks will not start after updating, see the won't-open-after-update guide before reinstalling again.

Verify the update

  1. Open Help → Update QuickBooks Desktop and confirm the Overview tab shows no updates waiting.
  2. Press F2 and check that Product Information matches the update you installed.
  3. Open your company file, choose Window → Close All, then run File → Utilities → Verify Data and confirm it reports no problems.
  4. If you run Desktop Payroll, confirm the tax table version is current before processing payroll.
  5. Create a fresh backup and store it off the machine.

If the update still fails

Try the digital signature route. Close QuickBooks, go to C:\Program Files\Intuit\QuickBooks, right-click QBW32.exe and choose Properties. Open the Digital Signature tab, confirm Intuit is selected, choose Details → View Certificate → Install Certificate, and click Next through to Finish. Restart the computer, then download the update again.

If error 1334 appears during the retry, move to the error 1334 install path. If the update hangs rather than fails, use the update stuck guide instead of reinstalling. When more than one copy of the same version year is installed, QuickBooks update errors are expected, and manual updates for each copy are the documented workaround.

After all of that, damaged Windows files or an endpoint-security policy may be blocking MSI writes. Escalate to Intuit support or an IT professional with the error code, the F2 version, and the steps you completed.

Prevention

  • Keep Windows fully updated, especially before QuickBooks year-end and payroll deadlines.
  • Leave automatic updates enabled, or schedule a monthly window when nobody needs the program for 30 minutes.
  • Run updates as a Windows administrator with every company file closed.
  • Keep antivirus exclusions documented so the next patch is not quarantined in silence.
  • Never install the same version year twice on one computer, and download installers only from Intuit's official Downloads & Updates page.

Frequently asked questions

Does a failed update damage my company file?

No. An update changes program files, not the .QBW company file. The risk is an interrupted patch leaving the program unstable, so back up first and run Verify Data once the update succeeds.

Can I keep using QuickBooks without installing the update?

Usually yes for product updates, but not for payroll tax tables. An outdated tax table means incorrect withholding, and older releases eventually lose support. Finish the update or use the manual update route before your next payroll run.

Why does the update fail at the same point every time?

That pattern points at damaged files left in the download folder rather than the network. Use the Reset Update checkbox, then rename the Components and downloadqbXX folders so QuickBooks rebuilds them, and retry.

Do I need to uninstall QuickBooks to make the update work?

No, not until the documented fixes fail. Run as administrator, reset the update, clear the damaged folders, install pending Windows and .NET updates, and use the Tool Hub. A reinstall is the documented fix when update or repair runs end with errors like 1334, 1328 or 1603.

What if QuickBooks Online says an update failed?

QuickBooks Online has no patch to install; Intuit updates it on the server. A failed update message there usually refers to a payroll or bank feed sync, which is a connection or service issue.

Sources & further reading