QuickBooks Condense Data Stuck at 99 Percent: Stop It Safely and Retry

A Condense Data run that stalls at 99 percent or dies with an unrecoverable error can be stopped safely and made to finish.

Condense Data freezing at 99 percent, or quitting with an unrecoverable error, is one of the most common failures we see on large company files. The two failures are not the same problem. A stall at the end is often the utility still working. A hard crash usually means file damage, or a cutoff date that forces too much relinking in one pass. Here is how we stop the run safely, clear the real cause, and get the condense to finish.

Why does the condense stall at 99 percent?

The progress bar is an estimate, not a meter. The final phase of a condense rewrites every transaction you are keeping, then re-points its internal links at the new summary entries. On a file with a high transaction count, that phase runs the longest, so the bar can sit at 99 percent while the disk stays busy.

An unrecoverable error is different. It means the utility hit a damaged transaction, or a broken link, that it cannot rewrite. Waiting does not fix that. The file has to be checked, and repaired if needed, before the run is attempted again.

Stop the stalled run safely

1. Open Task Manager and find QBW32.EXE on the Processes or Details tab. Watch its CPU and disk activity for a minute or two.
2. If either number moves, the condense is still working. Leave it alone, even when the bar has sat still for a long while.
3. If both stay flat and the window reports Not Responding, end the task. This is blunt but survivable, because the working file is only swapped for the condensed copy at the very end.
4. Reopen the company file and run File > Utilities > Verify Data. A file left mid-run often passes; if it fails, restore rather than force repairs.
5. If the file will not open at all, restore the backup the wizard made before starting, or your own manual backup, and work from that copy.

Prepare the file before any retry

Never restart a condense on the same terms that crashed it. Set these conditions first:

• Make a full manual backup, verify it, and keep it outside the working folder.
• Switch to single-user mode under File > Switch to Single-user Mode, with every other user logged out.
• Close third-party apps and sync tools that touch the file, and pause any scheduled antivirus scan.
• Run the condense on the machine that hosts the file, not across the network.
• Note the file size before you start, so the result can be proven afterward.

Rule out file damage first

A condense will not complete on a damaged file. It fails, and it fails late, which is why the error feels random. Work through this in order:

1. Run File > Utilities > Verify Data in single-user mode.
2. If Verify reports damage, run Rebuild Data, accept the backup prompt, and let it finish untouched.
3. Verify again afterward, and repeat the Rebuild once or twice if errors persist.
4. If Verify still fails after repeated rebuilds, stop. The damage sits deeper than the built-in tools reach, and it must be repaired before any condense. That is the kind of file our QuickBooks Verify and Rebuild repair service exists for.

Do not start a condense while Verify is failing. That turns a stall into a certainty.

Pick a cutoff date the condense can finish

The further back the cutoff, the more transactions the utility must summarize and the more links it must rewrite. A date that swallows the whole history in one pass is the most common cause of a stall. Make the run smaller instead:

• Choose the day after a fiscal year end that is closed, filed, and fully reconciled.
• Reconcile every bank and credit card account through that date before you start.
• Apply open credits, clear stale undeposited funds, and void invoices you will never collect.
• Condense the oldest year only, verify, then repeat with an earlier date in a separate run.

Newer Desktop editions offer a lighter path inside the Condense wizard: remove only the audit trail and keep every transaction. It usually completes where the full run fails, and it still shrinks the file. You give up the editing log, not the accounting. Files running Advanced Inventory or heavy integrations are the exception; their link counts keep the full run fragile regardless of date.

Signs the condense actually completed

Do not trust the completion message alone. Check these:

• Register entries before the cutoff are replaced by journal entries dated at the cutoff, each marked as condensed.
• A balance sheet and a trial balance dated after the cutoff match the same reports from your pre-run backup.
• Verify Data passes clean on the condensed file.
• The file size has dropped, and the archive backup holds the original detail if you ever need it.

If the condense still fails

When a file passes Verify, the date is modest, and the run still dies, the fault is usually structural. It sits in the link structure that Verify does not fully test. No cutoff date works around that. The file has to be repaired first, then condensed.

Where the aim is simply shrinking a very large file, condensing an oversized QuickBooks company file can be tested before you commit the downtime, so the decision rests on evidence rather than another failed evening.

Order matters above all: repair, verify, then condense. Reversing that order is how a 99 percent stall becomes a file that will not open at all.