QuickBooks Error C=13: Damage Inside a Company File List

QuickBooks Error C=13 points to damage inside one of your company file lists; this guide explains what it means, what triggers it, and how to clear it.

Error C=13 stops QuickBooks Desktop while it reads one of the lists inside your company file. The code has been around for decades, and our engineers still see it regularly in files that arrive for review. In most cases the built-in verify and rebuild utilities clear it, and this page walks through that work in order.

What does the error message say?

The dialog usually reads:

Error C=13: Error reading one of the lists. The disk may be full.

Exact wording varies a little between releases. Some versions add a note that a data problem prevents QuickBooks from continuing. During a backup you may instead see a recoverable error message that offers to run a rebuild. Where the code appears changes; what it means does not.

What does C=13 mean?

Every company file holds two kinds of data: transactions, and the lists those transactions point to. The lists include the chart of accounts, items, customers, vendors, and employees. An internal index keeps each list in order and gives every entry an identifier that transactions reference.

C=13 is raised when that index, or a record within it, cannot be read cleanly. The program expects a known structure, finds something else, and stops rather than guess. The line about a full disk is standard text carried in the message. Genuine disk exhaustion is a rare cause, and damaged list data is the common one.

The code never names the list at fault. That is why the repair routine runs across the whole file rather than one list.

What triggers error C=13?

Nearly every case we trace comes back to an interrupted write. The typical sequence: QuickBooks is open, a workstation loses power or is forced off, and the save never finishes. A list index is left half-written, and the next open fails.

Other triggers include:

• A network drop while the file is hosted in multi-user mode.
• Storing the file in a folder a cloud service syncs, so the sync engine touches it while it is open.
• Keeping the file on removable media that is unplugged mid-session.
• A failing sector on the drive where the file sits.
• Damage left over from an earlier fault that was never rebuilt.

Large, long-lived files with big lists fail more often than small ones. There is simply more to write, and more that can be interrupted.

How do you fix error C=13?

Work through the scenarios below in order. The first clears most files on its own.

Run verify and rebuild

1. Have every other user close the company file, then switch to single-user mode from the File menu.
2. Take a manual backup before anything else, so you can go back if needed.
3. Open the File menu, choose Utilities, then Verify Data. The verify pass reads the whole file and reports what it finds.
4. If verify reports damage, accept the rebuild prompt, or choose Utilities, then Rebuild Data. Let it make its own backup first.
5. Allow the rebuild to finish even when it looks stalled. On a large file it can run a long time and often appears frozen near the end.
6. Click OK on the summary, then run Verify Data again. Repeat the rebuild and verify cycle up to two more times if damage remains.
7. If verify passes but one list still misbehaves, open that list from the Lists menu and re-sort it by name. Re-sorting rewrites the display order and clears some stuck states.

Rule out the drive and the file's location

1. Check free space on the drive holding the company file. Rebuild needs scratch room, so clear space if the drive is nearly full.
2. If the file sits in a synced folder or on removable media, close QuickBooks, copy it to an internal drive, open it there, and run verify and rebuild again.
3. If the drive reports errors in Windows, copy the file to another disk and rebuild the copy.

Restore a known good backup

1. Note the date the error first appeared and the last transactions you trust.
2. Choose File, then Open or Restore Company, then Restore a backup copy, and pick a backup made before the error.
3. Restore to a new file name so the damaged copy stays intact.
4. Verify the restored file, then re-enter the transactions recorded since that backup.

When rebuild cannot clear it

Repeated rebuild cycles fail when the damage sits in structures the utility cannot rewrite. Running as a Windows administrator or restoring on another machine will not change that outcome. At that point the file needs manual repair of the damaged list, which is the work our data repair service performs.

How can you stop it from coming back?

Prevention mostly comes down to protecting the file while it is open.

• Keep the company file on a stable internal drive or a properly configured host, never in a folder a cloud service syncs.
• Put the host machine on an uninterruptible power supply, and shut down only after every user has closed the file.
• Back up daily with full verification enabled, and keep several generations instead of overwriting one.
• Run Verify Data once a month as a health check. It catches damage before an error interrupts work.
• Keep lists lean by merging duplicate customers, vendors, and items, since fewer records means less to write on every save.

A file that verifies clean, sits on healthy hardware, and is backed up daily rarely produces a C= code. If one appears anyway, run verify first and let it tell you where you stand.