Verify/Rebuild Stuck at 99% or Condense Fails

5-minute fixVerified for QB 2021–2025Easy–Medium difficulty

Quick Answer

When Verify Data hangs or Condense fails, run the process locally (not over network), reset sidecar files, and simplify the environment. Do this: Copy the .QBW to C:\QBTemp on the host, rename .ND/.TLG, run Verify/Rebuild in Single-user (Admin), then reopen from the local path. If it succeeds locally, move the repaired file back to the server and rescan with Database Server Manager.

What is this issue?

Verify/Rebuild and Condense are I/O-heavy. Network latency, stale sidecar files, or minor list damage can stall the operation even though the data is repairable.

Problem statement:

Environment (network/locks) or sidecar corruption prevents Verify/Rebuild/Condense from completing.

Error Verify/Rebuild: Verify/Rebuild stuck or Condense fails

QuickBooks maintenance operations hang due to network, locks, or sidecar file issues.

Symptoms:

•Verify Data hangs near 99%
•Rebuild never completes or throws vague errors
•Condense aborts with no clear reason
•Works on server console but fails from workstations

Resolution Steps:

1.
Work locally on the host (no network path)
2.
Rename .ND/.TLG (fresh sidecars)
3.
Run Verify then Rebuild in Single-user (Admin)
4.
Test Portable company file route (forces a clean reindex)
5.
If condensing, clean lists and reduce targets first

Quick Fix (≈5 Minutes)

Step 1: Prepare a local workspace

Create C:\QBTemp\ on the host/server.
Copy YourCompany.qbw into C:\QBTemp\.

Step 2: Reset sidecars (in the same folder as the working file)

Rename YourCompany.qbw.nd → .nd.old (if present).
Rename YourCompany.qbw.tlg → .tlg.old (safe; won't touch your data).

Step 3: Open locally

Launch QuickBooks as Admin → File → Open or Restore Company → browse to C:\QBTemp\YourCompany.qbw.

Step 4: Run Verify → Rebuild

File → Utilities → Verify Data
If prompted, allow QuickBooks to run Rebuild immediately after Verify.

Step 5: If Verify/Rebuild still stalls

Create a Portable company file (.QBM) from the local copy → Restore it as a new .QBW in C:\QBTemp\ → run Verify again.
This rewrites indexes and often bypasses stubborn damage.

Step 6: Move back to the server & rescan

Replace the server copy with your repaired .QBW (after hours, all users out).
On the host, run Database Server Manager → Scan the data folder to recreate .ND.

Detailed Solution Steps

Single-user, Admin, no background services

File → Switch to Single-user Mode (Admin).
Close other apps that hook files (backup tools, EDR, indexing).
Ensure fast local disk (avoid USB/network targets during repair).

Clean list issues before condense

Lists → Customer/Vendor/Item → Re-sort each list (View → Re-sort List).
File → Utilities → Verify Data again.
Remove or fix damaged memorized reports and custom forms (common condense blockers).

Shrink targets for condense

Run Verify clean first.
If condensing, choose options that remove transactions older than the target date but keep lists.
Consider running condense in chunks: older years first.

Check file size & TLG growth

If .TLG is massive, making a manual verified local backup trims it.
If backup fails, rename .TLG (you'll lose incremental log continuity; full backup recommended after repair).

If errors persist

Try on a new Windows profile on the host (rules out user-profile issues).
Repair QuickBooks from Apps & Features.
As a last resort, export critical lists (IIF), create a new empty company, and re-import; then bring over beginning balances (heavy, but rare).

Why does this happen?

Common causes

•
Network latency/locks interrupt I/O during Verify/Rebuild
•
Stale/damaged .ND or oversized .TLG logs
•
Minor list/index damage that portable restore reindexes
•
Background tools (AV/backup/sync) holding file handles

How to Prevent It

Best Practices

Run Verify/Rebuild locally on the host during off-hours
Keep a quarterly verified backup to trim .TLG
Standardize data at D:\QBData and keep it off OneDrive/Dropbox
Add AV exclusions for QB program/data paths
Keep QuickBooks on the latest maintenance release

FAQs

Will renaming .TLG lose transactions?

No. .TLG is a log. Your actual data is in .QBW. You'll lose ability to roll forward from an old backup; take a fresh full backup after.

Is Portable (.QBM) safe?

Yes—.QBM is a compact transfer format; restoring it rebuilds indexes and often clears structural glitches.

Can I condense across a network share?

Don't. Always condense locally on the host.

Related Resources

Error 6000-83 Solution

Fix file corruption issues

Read-Only Network Share

Fix permissions for network shares

H202/H505 Server Change

Fix multi-user errors after server changes

QuickBooks Backup Guide

Complete backup and restore instructions

Need Professional Help?

If you're still experiencing issues with Verify/Rebuild or Condense, our QuickBooks data experts are here to help.

Get Expert Support