QuickBooks Error 12031: Update Download Timeout
Error 12031 stops a QuickBooks Desktop payroll or program update mid-download; this guide covers the causes our engineers find and how to clear them.
Error 12031 appears while QuickBooks Desktop is fetching something, usually a payroll tax table and sometimes a program update. The transfer stalls, the update window reports the code, and nothing installs. The fault sits in the connection, not in your books, and our engineers clear it from the workstation in most cases.
The exact error message
You will see the code in the update progress dialog once the transfer dies. The wording varies slightly between releases, but the dialog carries a line of this form:
A network timeout occurred while QuickBooks tried to connect to the server.
Older builds describe a failed connection to the update server and print the number beside it. Either way, the dialog offers a retry, and the retry fails the same way until the connection problem underneath is fixed.
The meaning of error 12031
QuickBooks Desktop does not download updates with networking code of its own. It hands each transfer to the Windows internet layer and passes that layer's result back to you. Code 12031 is a Windows internet error: the connection to the download server was reset before the transfer finished.
Our engineers treat it as a broken download rather than a fault in the program or the file. Your company data plays no part in the exchange. Payroll updates trigger it most often because the tax table download is the largest scheduled transfer the software makes.
Common triggers
Any one of these will produce the code. The first is the most common in our experience.
- An unstable connection. Wi-Fi dropouts, a saturated shared line, or an outage at the provider will cut a long transfer partway.
- Stale internet settings in Windows. The program inherits proxy and security protocol settings from the operating system, so a leftover proxy entry breaks the download.
- Security software. Antivirus tools that inspect encrypted traffic can reset a transfer they cannot parse, and a firewall rule can block the updater outright.
- A recent version upgrade. Each release installs into a new versioned folder, so firewall allowances written for the previous release stop matching.
- A drifted system clock. Certificate checks fail when the date or time is wrong, and the secure connection is dropped at the start.
The fix, step by step
Work through the scenarios in this order. The first one clears most cases on its own.
Retry with a clean cache.
- Close and reopen QuickBooks Desktop, then open the Help menu and choose Update QuickBooks Desktop.
- On the Update Now tab, tick Reset Update before you do anything else. This discards the partial files from the failed attempt, and without it the retry often fails the same way.
- Select Get Updates and let it run. Two or three attempts are reasonable before you move on.
Rule out the line.
- Connect the workstation to the router with an ethernet cable if you can, and pause other heavy traffic on the network.
- Retry the update. If it still stalls, repeat the attempt on a different network, a phone hotspot for instance.
- A success on the second network points at the primary line or its equipment. Reboot the router, wait a full minute, and try once more.
Refresh the Windows internet settings.
- Close QuickBooks, press the Windows key and R together, type inetcpl.cpl, and press Enter.
- On the Connections tab, open LAN settings. Clear the proxy fields unless your network genuinely uses one.
- On the Advanced tab, tick Use TLS 1.2 in the security list. Newer releases of the software require it for secure downloads.
- Apply the changes, reopen QuickBooks, and run the update again.
Correct the clock.
- Open Settings, then Time & Language, then Date & Time.
- Confirm the time zone, switch automatic time on, and retry the update.
Adjust the security software.
- In Windows Security, open Firewall & network protection and choose Allow an app through firewall.
- Tick every QuickBooks entry, and the update agent if one is listed, for private and public networks.
- If you run third-party antivirus, turn off its encrypted traffic scan temporarily and retry. If the update then completes, add a permanent exception rather than leaving the scan disabled.
Preventing a recurrence
Run large updates on a wired connection while the line is quiet, because a stalled transfer is far less likely then. After any version upgrade, revisit the firewall allowances; the new install path will not match the old rules. Leave automatic time sync switched on. Keep Windows itself current too, since the security protocols the updater relies on come from the operating system. If your connection drops often, take it up with the provider before the next payroll date. The tax table download is where the weakness will surface first.