QuickBooks Error 136: Causes and Safe Repair Steps

Last reviewed 2026-09-07

QuickBooks Error 136 is a crash-class error: QuickBooks closes without warning while you are opening or working in a company file, and reopening usually repeats the crash. In most cases the cause is damage inside the company file itself, not a setting or a permissions problem. This page shows you how to confirm that, repair the file safely, and recognize when it needs a specialist.

What is actually going on?

When QuickBooks hits a stretch of data inside the company file it cannot read or reconcile, it shuts down rather than keep writing on top of the problem. That defensive exit is what you are seeing. The number alone is thin on detail; the behavior around it tells you far more. The two questions that matter are which file triggers the crash, and whether the program runs normally with a different file.

Why does QuickBooks throw Error 136?

Damage usually gets in during an interrupted save: a power cut, a forced shutdown, or a dropped network connection while QuickBooks was mid-write. Oversized, bloated files crash more readily, because more of the database must stay consistent on every save. A damaged program installation can mimic the same crash, though it is the less common culprit. A single broken transaction or list record is often enough; the file does not need to look sick otherwise.

Make a safety copy before anything else

Close QuickBooks and, at the folder level, copy the company file and its matching transaction log to a separate folder, ideally on a different drive. This copy is your insurance for every step that follows. Rebuild and restore both write to the file, so never run them against your only copy. If the crashes are recent, note the date they started; that tells you which backups predate the damage.

Is it the file or the program?

Open the sample company that installs alongside QuickBooks. If the sample opens and behaves, your installation is fine and the problem lives in your data file; carry on below. If the sample crashes too, suspect the installation: run the repair tools in Intuit's QuickBooks Tool Hub, then test again. This one test saves people hours of fixing the wrong thing.

Work through the repair steps in order

Each step either fixes the file or tells you something. Stop at the first one that clears the crash, then move to the final checks.

1. Bring a copy local. If the file lives on a mapped network drive or a shared folder on another machine, copy it to the desktop and open it from there. Network storage multiplies the ways a save can be interrupted, and the test costs you nothing.
2. Restore a recent backup. Open a backup from before the crashes began. If it runs cleanly, the damage is recent, and you only need to re-enter the entries made since that backup. Leave the damaged file and its log untouched; those recent entries can still be pulled from them.
3. Run Verify, then Rebuild. From the File menu, verify first to locate damage, then rebuild to attempt the repair, and verify again at the end. A clean second pass is the goal. If a second rebuild does not clear what verify finds, stop; repeated runs rarely help and can cost you data. Files that keep failing at this stage are the daily work of our QuickBooks Verify and Rebuild repair service.
4. Round-trip a portable file. Save a portable company file, close your company, then restore the portable under a new name. The restore rebuilds the database structure and often clears damage the basic repair misses. Test the restored copy before you trust it.

The transaction log is your safety net

The transaction log sits beside your company file and records entries before they are written into the main database. After crashes, that log is often much larger than the company file, which means it holds entries the main file never received. Do not delete or rename it; the entries inside are recoverable, and renaming the log throws them away silently. When a file cannot be repaired in place, we regularly recover transactions from the QuickBooks transaction log.

When should the file come to us?

Hand the file over when it will not open even from a local copy, when backups refuse to restore, or when rebuild keeps failing on the same findings. Missing transactions, shifted balances, or accounts that suddenly will not reconcile all point the same way, especially with payroll in the window. Send the company file, its log, your most recent backup, and the date the trouble started; that is normally all we need. Our QuickBooks data recovery service for a file that will not open covers what happens next.

Did the repair hold?

Run verify one more time and expect a clean report. Check your key totals against the last good backup, then reconcile the bank and credit card accounts for the current period. When everything ties, take a fresh backup straight away and keep the safety copy for a few weeks. Open the file again the next morning before you declare victory; crashes that have truly gone stay gone.