Run Verify Data on a Copy, Not the Live QuickBooks File

A history of corruption makes running Verify Data on your live QuickBooks Desktop file a risk. Our engineers outline a safer way to check the file.

Verify Data is the built-in integrity check for a QuickBooks Desktop company file. On a healthy file it is routine housekeeping. On a file with a history of corruption, our engineers will not run it against the working copy. The check walks the entire database, and a structurally weak file can fail partway through the pass. The safe pattern is straightforward: verify a copy on a local drive, in single-user mode, and read the log that the check produces.

Can Verify Data damage a fragile file?

Verify only reads, so the pass itself is not meant to change anything. The danger sits around it. A file with existing structural damage can crash at the exact spot where the weakness lives, and an abrupt stop leaves the file improperly closed.

When Verify finds damage, QuickBooks offers Rebuild at once, and Rebuild writes to the file. Accept that prompt on the live file and you are rebuilding your only copy. Files stored on a network share carry a further hazard, because a dropped connection can cut the pass off mid-stream. All of these risks turn harmless the moment the file being checked is a disposable copy.

Before you copy anything

Three preconditions come first. Every user logs out of the company file and closes QuickBooks, including the machine hosting the file in a multi-user setup. You take a genuine backup, either a QBB created from inside QuickBooks or a second copy of the QBW stored somewhere safe. And the local drive needs free space comfortably larger than the file itself, since the verify pass wants working room.

Copy the company file to a local drive

1. Close QuickBooks on every machine that touches the file.
2. In Windows, browse to the folder that holds the live company file.
3. Copy the QBW file to a folder on the workstation's own internal drive. If a TLG transaction log file sits beside it, copy that too. Skip USB sticks and network locations; the point is a stable local disk.
4. Rename the copy so it cannot be mistaken for the original. QuickBooks does not care what a company file is called.

Run Verify on the copy

5. Open QuickBooks, choose File > Open or Restore Company, and open the copy from its new location.
6. Switch to single-user mode before anything else, from the File menu. In multi-user mode, parts of the check are skipped and errors may never reach the log, so treat this step as mandatory.
7. Choose File > Utilities > Verify Data. If QuickBooks offers to back up first, accept; a backup of a copy costs nothing.
8. Let the pass run to the end. Do not cancel midway, and stop the machine from sleeping. On a large file this can take a while.
9. If damage is reported and Rebuild is offered, run Rebuild on the copy, as many passes as it wants. The copy can absorb that. The live file never has to.

Read the QBWin.log

Verify writes its findings to QBWin.log, a plain text file that opens in Notepad. Current releases put it in the same folder as the company file that was open, so look next to your copy first. If it is not there, search the workstation's drive for the file by name. The log accumulates entries, so find the newest run by its date and time stamp and read that block.

A clean pass ends with a completion notice and no lines flagged as errors. A damaged one lists specifics: failed integrity checks, malformed transactions, mismatched records, usually paired with a recommendation to rebuild. Those lines are the real diagnosis, and the log is small, holding findings rather than your books, so it travels well if the file ever needs outside analysis.

Signs the check worked

The copy finishes the pass and returns a verdict instead of crashing. The dialog either reports no problems or reports problems while the copy still opens afterward. The newest block in the log carries no error lines. And the live file is untouched: its modified date sits exactly where it was before you copied it. If days pass before anyone acts on the results, make a fresh copy first; transactions entered since the first copy were never tested.

The limits of the copy-first method

Verifying a copy is diagnosis, not repair. Damage found on the copy exists in the original too, because the copy is a byte-for-byte snapshot. Rebuild run on the copy produces a repaired copy, not a repaired original, and promoting it over the live file is a separate decision. Make it only after the log confirms every error cleared.

Some damage survives repeated rebuilds, such as broken transaction links or reports that stay out of balance, and no verify-and-rebuild loop reaches that. Files in that state need repair work on the data itself; see our QuickBooks Verify and Rebuild repair service page for what that involves.

There is a mirror case worth knowing. The copy can verify clean while the live file still misbehaves. That points the search away from the data and toward the network, the hosting setup, or a mismatched program release on a workstation.