How to Repair a Damaged QuickBooks Company File

What a company file repair can and cannot fix

QuickBooks stores everything in one working file, the .QBW, supported by a transaction log (.TLG) and network files. When part of that structure stops matching what QuickBooks expects, the result is data damage: lists lose entries, reports drift, transactions refuse to save, or the file will not open.

Intuit classifies damage in three types. List damage affects accounts, customers, vendors, items and employees. Transaction damage affects one or more entries. Structural damage affects the tables that hold everything. A good repair addresses them in that order, because repairing one layer often reveals damage in the next. Early warning signs are covered in the data damage guide.

What repair cannot do: recreate missing transactions, merge a physically truncated list, or decrypt personal data that no longer decrypts. Those cases end in a restore or professional recovery.

Before you begin: the backup strategy

Every serious repair starts with three copies, none of which overwrite an existing file:

• A QuickBooks backup (.QBB). Use File → Back up Company → Create Local Backup and select Complete verification so QuickBooks tests the backup before saving it. A .QBB includes accounting data, templates, letters, logos, images and related files, though not payroll forms.
• A file-level folder copy. Copy the folder holding the .QBW together with its .TLG, .ND, .DSN and .ADR companions to an external drive. This is the copy a recovery technician needs if repairs fail.
• The last known-good backup. Locate the most recent .QBB created before the symptoms began. That file is your restore point and possibly your comparison baseline.

Test at least one backup before trusting it: restore it to a temporary folder under a new name and open it. If it opens, your recovery point is real. The full routine is in the backup and restore guide.

Reading Verify Results like a technician

The Verify Data utility produces one of three outcomes, and each one changes what you do next:

• "QuickBooks detected no problems with your data" — no damage found. If users still see wrong balances, compare reports against a known-good backup and check QBWin.log for entries from the last failed run.
• "Your data has lost integrity" — damage was found. Proceed to Rebuild Data and verify again afterward.
• A specific error message — open the Verify Results window, choose Expand All, and select See Online Article beside each entry for the fix Intuit documents.

Behind the results window, QuickBooks keeps a text log called QBWin.log in the folder that contains the company file. Search it for LVL_ERROR and LVL_SEVERE_ERROR lines; they contain the record numbers, types and dates you need for manual repairs. A few logged errors signal unrecoverable damage — see the escalation section below.

The professional repair procedure

Common repairable errors and their manual fixes

These are the documented repairs for the most common repairable errors. Always rebuild and verify first — several clear during a rebuild and never need a manual edit.

When to stop and escalate

Technicians who escalate early save files that repeated rebuilds would destroy. Stop repairing and escalate when:

• The first rebuild takes more than two hours — Intuit's own guidance is to contact support at that point.
• The same error returns unchanged through two or three verify/rebuild cycles.
• You see damage Intuit lists as unrecoverable, including -6150, 1006, C=44, "Database disk image is malformed", or "Warning, no such table:schemaHistory". Those need an older backup or a new file.
• Encrypted data — credit card numbers, Social Security numbers, bank details — no longer decrypts.
• The file still will not open after File Doctor, or it lives on a server that is also failing.

At that point the options are Intuit Data Services, which accepts .QBW uploads for paid recovery, a local recovery technician, or last-resort QuickBooks Auto Data Recovery for Pro, Premier and Enterprise on Windows. The data recovery service guide explains what each expects. Keep the original file exactly as it is; every write to a damaged file can reduce what a specialist recovers.

How to test the repaired file

1. Run Verify Data one final time and confirm "QuickBooks detected no problems with your data".
2. Compare Trial Balance, Profit & Loss and Balance Sheet reports against a known-good backup, especially accounts that originally drifted.
3. Open every transaction that appeared in QBWin.log and confirm it saves and reopens cleanly.
4. Spot-check list counts for customers, vendors, items and employees against the backup.
5. Open the file from a second workstation in multi-user mode.
6. Create a fresh backup, store it off the machine, and check QBWin.log again after the first full day of use.

Prevention

• Back up on a schedule and test a restore every quarter. A repair procedure is only as good as the backup behind it.
• Run Verify Data at least twice a year and before every QuickBooks upgrade, so damage is caught while it is still minor.
• Keep the company file out of OneDrive, Dropbox and similar sync folders.
• Put the server on a UPS, give it a static IP, disable sleep, exit QuickBooks with File → Exit, and replace failing drives before they corrupt a write.