QuickBooks Data Damage: How to Recognize and Repair It

What QuickBooks data damage means

Data damage is any mismatch between the records stored in your .QBW company file and the internal tables, lists and targets QuickBooks uses to display them. Your transactions are usually still inside the file — QuickBooks simply cannot read part of it correctly.

Intuit groups the problem into three types: list damage (accounts, customers, vendors, items, employees), transaction damage (one or more entries), and structural damage (the tables underneath). The repair that works depends on which type you have.

Symptoms of data damage

• Verify Data reports "Your data has lost integrity" instead of "QuickBooks detected no problems with your data".
• Account balances no longer match a recent backup, a prior-period report, or the register total — the classic balance drift.
• Lists show blank rows, duplicates, or entries that vanished from pick lists.
• The file opens slowly, freezes, or crashes when you open one specific transaction or report.
• Odd errors appear during everyday tasks; an error code lookup often traces them back to damaged data.
• The file will not open at all and shows a variant of QuickBooks error 6000.

How to read QBWin.log and spot balance drift

QuickBooks writes a diagnostic file called QBWin.log in the folder that holds your company file (the default is C:\Users\Public\Public Documents\Intuit\QuickBooks\Company Files). Open it in Notepad and search for LVL_ERROR, LVL_SEVERE_ERROR, or Error: Verify. Those lines name the exact list or transaction that failed verification.

One entry matters most: Error: Verify Account Balance failed. It prints two numbers — the balance QuickBooks calculated from transactions and the balance stored in the account list. When they differ, reports disagree with each other. That is balance drift, and Intuit's documented repair is a rebuild followed by another verify.

To confirm drift before repairing anything, run the Trial Balance report (Reports → Accountant & Taxes → Trial Balance) and compare it with a known-good backup. A difference that survives two runs is not a rounding issue.

Common causes of data damage

1. Interrupted writes. A crash, power loss, or forced shutdown while QuickBooks is saving leaves internal tables half-written. This is the most common cause seen in practice.
2. Network interruptions in multi-user mode. A dropped connection while another workstation posts a transaction can damage the transaction log or the .ND file.
3. Consumer file-sync services. OneDrive, Dropbox and similar tools lock and version company files behind QuickBooks' back, producing damage that looks random.
4. Hardware faults. A failing drive, RAM, or server can write corrupted blocks silently, re-damaging the file after every repair.
5. Imports and version mismatches. Importing lists or transactions can create duplicate names and orphaned targets, while workstations on different QuickBooks builds widen the gap between the file and the program.

Before you begin

• Back up twice: a QuickBooks backup through File → Back up Company → Create Local Backup, and a folder copy of the .QBW plus its .TLG, .ND and .DSN files. Treat the folder copy as your forensic original.
• Work in single-user mode (File → Switch to Single-user Mode) and ask every other user to stay out.
• Sign in with a Windows account that has full control of the company-file folder and admin rights on the QuickBooks PC.
• Budget time honestly: a large verify can run several minutes and a rebuild an hour or more.

The safe repair order for damaged data

What Rebuild fixes — and what it does not

Rebuild reconstructs the internal tables and indexes that connect your lists and transactions, and it repairs minor data issues, including some list damage. That is why Intuit resolves an error such as Verify Account Balance failed with Rebuild followed by Verify.

Rebuild does not repair everything. Specifically, it does not:

• Fix transaction-level damage corrected in the entry itself: a damaged link, an out-of-balance transaction, or damaged item history.
• Repair encrypted-data damage, such as credit card numbers, Social Security numbers, or bank details that no longer decrypt.
• Merge duplicate names or recreate records that are gone.
• Recover transactions created after your last good backup — that is a restore, not a repair.
• Fix environmental damage. Rebuild a file sitting in a sync folder or on a failing drive and the damage returns.

Verify the repair worked

1. Run Verify Data again and confirm "QuickBooks detected no problems with your data".
2. Run the Trial Balance and compare it with the known-good backup. Investigate every account that differs.
3. Open the transactions named in the old QBWin.log errors and confirm each saves cleanly.
4. Spot-check the lists that failed: customers, vendors, items and the chart of accounts.
5. If you work in multi-user mode, post a test transaction from a second workstation, then delete it.
6. Create a fresh backup and store it off the machine.

If data damage keeps coming back

A file that re-damages after a clean rebuild has an environmental problem. Test the drive with the manufacturer's diagnostics, check the network path, and remove any sync software touching the folder. If the same error survives three rebuilds unchanged, escalate — a file that keeps getting rebuilt can still be recovered if you stop in time.

Prevention

• Move company files off OneDrive, Dropbox, Google Drive and similar sync folders. Use a local drive or a properly shared server folder.
• Verify and rebuild at least twice a year and before every upgrade, and test a restore on the same schedule.
• Keep a tested backup and restore routine; an untested backup is only a file, not a recovery plan.
• Give the server a static IP, disable sleep on the host, keep workstations on the same QuickBooks release, and close QuickBooks with File → Exit instead of ending processes.