How to Run Verify and Rebuild Data in QuickBooks Desktop
The first move when QuickBooks Desktop starts misbehaving: how to run Verify Data, read the result, and when Rebuild Data helps — and when it makes things worse.
When QuickBooks Desktop starts throwing odd errors — reports that don't balance, transactions that won't open, random crashes on save — the built-in Verify and Rebuild utilities are the first diagnostic step. They are free, built into every Desktop edition including discontinued versions, and tell you whether the problem lives in your company file or somewhere else.
Before you start
- Switch to single-user mode (
File > Switch to Single-user Mode). Verify and Rebuild refuse to run, or run unreliably, with other users in the file. - Make a manual backup (
File > Back Up Company > Create Local Backup). Rebuild makes its own backup, but you want one you control. - Close every open window inside QuickBooks (
Window > Close All).
Run Verify Data
- Go to
File > Utilities > Verify Data. - Let it finish — on a large file this can take several minutes. Do not kill the process.
- Read the result:
- "QuickBooks detected no problems with your data" — the company file is structurally sound. Your symptom is coming from elsewhere (preferences, the install, a damaged form template, or the network path).
- "Your data has lost integrity" — the file has damage. Continue to Rebuild.
Run Rebuild Data
- Go to
File > Utilities > Rebuild Data. - QuickBooks forces a backup first — accept it and save it somewhere you can find again.
- Wait for "Rebuild has completed", then run Verify Data again. A clean second verify is the real success signal; the "completed" dialog alone is not.
When Rebuild is not the answer
Rebuild fixes list damage and light transaction-level corruption. It does not fix everything, and on a badly damaged file repeated rebuilds can compound the damage. Stop and reassess if:
- Verify still reports lost integrity after two rebuild passes.
- Rebuild crashes, hangs past a couple of hours, or errors out (commonly with a C= error or a -6000-series code — see the error code library).
- The file opens but balances changed after the rebuild.
In those cases the damage is below the level Rebuild can reach and the file needs deeper repair work before you trust it with another day of bookkeeping.
Reading QBWin.log for details
Verify writes its findings to QBWin.log. Press F2 then F3 inside QuickBooks, open the Open File tab, and open QBWin.log. Search for Verify from the bottom up — the lines after the final Verify Started block name the damaged lists or transactions, which tells you how deep the problem goes.