QuickBooks Error C=64: Data Damage During Verify or Rebuild

QuickBooks error C=64 appears when the program hits damaged data while verifying or rebuilding your company file. Learn what it means and how to clear it.

Error C=64 belongs to the C= family of QuickBooks Desktop codes, and it is one of the clearer members. It means the program struck a record inside your company file that it cannot read. The sections below cover the message you saw, the cause behind it, and the repair path our engineers follow, in the order we see it succeed.

What does the error message say?

Most occurrences reach us as the standard Windows crash notice raised by QuickBooks:

QuickBooks has encountered a problem and needs to close. We're sorry for the inconvenience.

The details pane of that notice names the code as C=64. When the fault strikes during a repair attempt, the code instead appears inside the Verify and Rebuild results, usually with a note that it was received while reading or rebuilding data. Both wordings point to the same thing: a record the database engine cannot parse.

What does error C=64 mean?

The C= prefix comes from the older numbering that the QuickBooks data engine still uses for structural faults. A C= code tells you the engine walked into a record whose layout no longer matches what it expects: a list entry, a transaction, or a link between two transactions. The number marks the point in the read where the engine gave up.

Our engineers read C=64 as damage caught during a sequential pass through the data, which is precisely what Verify Data and Rebuild Data perform. The code is a symptom, not the disease. The disease is the damaged record, and every fix has to end at that record.

What triggers error C=64?

Damage found by a routine check. Someone runs Verify Data after month end, it reports problems, Rebuild starts, and C=64 appears partway through. The damage was already there; the check merely exposed it.

An interrupted write. Power loss, a forced shutdown, or a dropped network connection while QuickBooks was saving leaves half-written records behind. The file still opens, but a record's structure is inconsistent.

Unreliable storage. A failing drive, a bad sector under the file, or a network share that cuts out mid-write produce the same half-written result.

Age and size. Very large files, with hundreds of thousands of targets or more, carry more links that can break. Damage accumulates quietly for years before any check runs.

Upgrading a damaged file. An old file that was never verified can throw C=64 the first time a newer version rebuilds it.

How do you fix error C=64?

Work on a copy first. Close QuickBooks and copy the company file to a safe location before anything else. Run every step below against that working copy.

Damage caught by Verify or Rebuild

1. Open the file in single-user mode and run Rebuild Data from the Utilities menu. Let QuickBooks create the backup it asks for.
2. When Rebuild finishes, run Verify Data. Some faults clear only after repeated passes, so run the pair up to three times.
3. If Verify still fails, restore your most recent backup to a local folder, then run Verify on it before you trust it. A backup that has never been verified is an assumption, not a recovery plan.
4. If no backup verifies clean, the damage sits in records the built-in tools cannot rewrite. Our engineers repair this class of fault directly in the data tables and return a file that verifies.

An interrupted write or a dropped connection

1. Copy the file to a folder on the workstation's local drive, open it there, and run Rebuild locally. Never rebuild over a network share.
2. On a multi-user setup, check that the host machine is stable: wired networking, no sleep timers, and no one closing QuickBooks from Task Manager.
3. Fix recurring interruptions before the file, or the next rebuild will fail the same way.

Unreliable storage

1. Move the file off the suspect disk or share immediately and work from the local copy.
2. Run a disk check on the old drive so bad sectors are marked and skipped.
3. Treat repeated C= codes on one machine as a hardware signal, not a software one.

An oversized or very old file

1. Press F2 in QuickBooks and read the transaction and target counts on the Product Information screen.
2. If the counts are high, plan a reduction. Retired history can be removed while reports stay intact, and our engineers perform that reduction directly on the file.
3. Repair the damage first, then reduce. Shrinking a damaged file can lock the fault in.

How do you keep error C=64 from coming back?

Run Verify Data monthly, after the close, so damage is caught while a clean backup still exists. Restore and verify one backup each quarter; an untested backup is not a backup. Keep the file on a local drive on the host machine, put that machine on a battery backup, and never end QuickBooks by force. Verify an old file in its current version before upgrading it. Watch the target counts on the F2 screen once or twice a year, and reduce the file before rebuilds start taking hours. None of this prevents a failing disk, so tested backups remain the real safety net.