QuickBooks C-Series Error Guide
How to Fix QuickBooks Error C=387
You were creating an invoice, opening a form, or running a report — and QuickBooks stopped with: "Unexpected Error: An error has occurred in QuickBooks. Please note the C= value — C=387." The software may have closed entirely, or the action you were performing simply failed.
At QuickFix Bookkeeping, C=387 is one of the more satisfying errors to resolve — because the majority of cases are caused by a damaged form template that takes under two minutes to fix. The problem is that most guides make you run through five complex methods before telling you about it. We lead with it.
The QuickFix Bookkeeping Distinction
C=387 has two very different trigger scenarios — and the fix for one has almost nothing to do with the fix for the other.
Scenario A — Template error
Error triggered by a specific form or template
A damaged invoice, sales receipt, purchase order, estimate, or other form template is causing the crash. The error appears specifically when creating or opening that type of transaction — but other functions work fine. This is the most common cause and the fastest to fix — often resolved in under two minutes by creating and deleting a test transaction.
Start with Method 1
Scenario B — File or installation error
Error triggered broadly — not tied to one template
The company file has internal data damage, the QuickBooks installation is corrupted, the Windows registry has invalid entries, or the .NET Framework is damaged. The error appears across multiple functions with no consistent single trigger. More involved to fix — but fully resolvable with the right sequence.
Start with Method 3
What Is QuickBooks Error C=387?
Error code
C=387
QuickBooks Desktop
Part of the C-series unexpected errors
What it means
Error C=387 is QuickBooks encountering something internally that it cannot handle — either a damaged form template it was trying to render, corrupted data in the company file it was trying to process, or a broken program component it was trying to execute. The software shuts down rather than risk data corruption.
Your financial data is almost certainly safe. C=387 is almost never a data loss event — it is a crash during processing. Your company file records are intact in the vast majority of cases.
What Causes QuickBooks Error C=387?
Scenario A — Template causes
📄
Damaged Invoice or Form Template
One or more form templates — invoices, sales receipts, estimates, purchase orders, or payroll forms — have become corrupted. QuickBooks crashes every time it tries to load or render the damaged template. Other templates and functions work normally.
🖊️
Customised Template Corruption
A heavily customised template — with logos, custom fields, or complex layout modifications — is more vulnerable to corruption after a QuickBooks update or a system crash. The customisations themselves can contain invalid data that QuickBooks cannot process.
Scenario B — File and system causes
🗂️
Company File Data Damage
Internal corruption in the .QBW file — from an improper shutdown, power outage, or storage hardware issue — causes QuickBooks to crash when encountering the damaged data. Verify Data will detect this and Rebuild Data repairs it.
⚙️
Corrupted Windows Registry
The Windows registry entries that QuickBooks relies on for its operations have become corrupted, invalid, or outdated — often following an incomplete QuickBooks installation or failed update.
📦
Damaged .NET Framework
A missing or corrupted .NET Framework component — which QuickBooks depends on for certain operations — can trigger C=387 errors that appear across multiple functions with no consistent template-related pattern.
💿
Corrupted Installation
An incomplete or damaged QuickBooks installation — from a failed update, an interrupted setup, or antivirus interference during installation — leaves program components in a broken state that surfaces as C=387.
🦠
Malware Damage
Malware or virus infections that have damaged QuickBooks program files or the .ND and .TLG support files. Run a full malware scan before troubleshooting if the error appeared suddenly with no other changes.
💾
Damaged .ND or .TLG Files
The Network Data and Transaction Log files alongside the company file have become corrupted or mismatched — causing QuickBooks to crash when it reads them during file operations.
Identify Your Scenario — Which One Are You Dealing With?
Scenario A signals — template
▸
Error only appears when creating or opening a specific type of transaction — invoices, estimates, purchase orders — but QuickBooks otherwise works
▸
You can run reports, open the company file, and perform other functions without error
▸
The error appeared after you customised a form template or after a QuickBooks update changed template compatibility
Scenario B signals — file/system
▸
C=387 appears across multiple different functions — not tied to one type of form or transaction
▸
QuickBooks crashes on startup, when opening the company file, or randomly with no consistent trigger
▸
Verify Data shows data integrity issues, or the error appeared immediately after a power outage, system crash, or failed update
How to Fix QuickBooks Error C=387 — Step by Step
If your error matches Scenario A — start at Method 1. It resolves most cases in under 5 minutes. If Scenario B — start at Method 3.
SCENARIO A
Template Fixes — Error tied to a specific form type
METHOD 1
Create and Delete a Test Transaction to Clear Template Damage
2 minutes — resolves most Scenario A cases
Creating a fresh transaction and immediately deleting it forces QuickBooks to refresh the template connection without using the corrupted one. This clears the C=387 error in the majority of template-related cases immediately — no tools, no reinstalls.
1
Go to Customers → Create Invoice (or whichever form type is triggering the error — Estimates, Purchase Orders, Sales Receipts, etc.).
2
Select any customer from the dropdown. Add any item and any amount — the specifics do not matter. Click Save.
3
Immediately click Delete on the saved transaction and click OK to confirm. This test transaction is discarded — it will not affect any records.
4
Close and reopen QuickBooks. Attempt the action that was previously causing C=387. In most template-related cases the error clears immediately.
QuickFix tip: If this clears the error but it returns next time you create the same type of form, the template itself is corrupted and needs to be recreated or replaced. Move to Method 2 to permanently fix the underlying template.
METHOD 2
Identify and Recreate the Damaged Template
Permanent fix for Scenario A
If Method 1 only provides temporary relief, the damaged template needs to be identified and either repaired or recreated from scratch. QuickBooks always has a default template for each form type — switching to it immediately resolves the error while you recreate your custom version.
1
Go to Lists → Templates. You will see all form templates in the list. To identify the damaged one, look for any template that corresponds to the form type that triggers C=387.
2
Double-click each template one by one and attempt to open it. The one that causes QuickBooks to freeze, crash, or show C=387 is the damaged template. Note its name.
3
Select the damaged template in the list. Click Templates → Make Template Inactive (or right-click → Make Inactive). This hides it without deleting it.
4
Create a new template for that form type: Lists → Templates → Templates dropdown → New. Rebuild your customisations on the fresh template. Test that C=387 no longer appears when creating the form.
SCENARIO B
File and System Fixes — Error not tied to one specific template
METHOD 3
Rename .ND and .TLG Files and Update QuickBooks
First Scenario B step
Before reaching for any heavy tools, two quick actions often clear Scenario B cases: renaming the support files to force recreation, and updating QuickBooks — since Intuit regularly patches known C-series error triggers in routine releases.
1
Navigate to the folder containing your company file. Find the .ND and .TLG files with the same name as your .QBW file. Right-click each → Rename → add .OLD to the end. QuickBooks will recreate them automatically.
2
Open QuickBooks → Help → Update QuickBooks Desktop → Update Now. Tick Reset Update and click Get Updates. Let all updates download and install fully. Restart QuickBooks.
3
Test QuickBooks after the update. If C=387 no longer appears — a known bug in your previous version was the cause and the update patched it.
METHOD 4
Run Verify Data then Rebuild Data
For company file data damage
If the company file has internal data damage, Verify Data detects it and Rebuild Data repairs it. Always run Verify first to confirm data damage is present before running the repair — and always back up before rebuilding.
Back up first: Go to File → Back Up Company → Create Local Backup before running any data repair. This protects your records if anything goes wrong during the rebuild process.
1
Go to File → Utilities → Verify Data. Let it run. If it says "Your data has lost integrity", proceed to step 2. If data is clean, skip to Method 5.
2
Go to File → Utilities → Rebuild Data. QuickBooks will ask you to create a backup again — do it. Wait for the rebuild to complete fully. Do not interrupt it.
3
Run Verify Data again to confirm issues were resolved. Then test the action that was previously triggering C=387.
QuickFix tip: If Verify Data comes back clean but you are still getting C=387, the problem is not in the company file data — it is in the QuickBooks installation or Windows components. Skip ahead to Method 5 or 6 rather than running Rebuild Data on a file that Verify has confirmed is healthy.
METHOD 5
Repair the QuickBooks Installation
For corrupted program components
If the file is healthy but C=387 persists, the QuickBooks installation itself has corrupted components. A repair install replaces all damaged program files without affecting your company data or settings.
1
Open QuickBooks Tool Hub → Installation Issues → QuickBooks Install Diagnostic Tool. Run it and allow it to complete — up to 20 minutes. Restart your computer when done.
2
If the diagnostic tool does not resolve it — press Windows + R, type appwiz.cpl and press Enter. Find QuickBooks in the list, click it and select Uninstall/Change → Repair. Follow the prompts to completion.
3
Restart your computer after the repair and test QuickBooks again.
METHOD 6
Repair or Reinstall .NET Framework
If all above methods fail
A damaged or missing .NET Framework is a surprisingly common cause of persistent C=387 errors that do not respond to QuickBooks-specific fixes — because .NET is a Windows component that QuickBooks depends on for certain operations outside of its own installation.
1
Press Windows + R, type optionalfeatures and press Enter. In Windows Features, find .NET Framework 3.5 and .NET Framework 4.8 (or latest). Untick them, click OK, restart, then re-enable them. This cycles .NET through a repair.
2
If the toggle cycle does not help, download the latest .NET Framework versions directly from Microsoft's official website and install them fresh. Restart after each installation.
3
After reinstalling .NET, open QuickBooks and test. If C=387 still appears, the issue is at a level requiring professional diagnosis — contact QuickFix Bookkeeping for hands-on support.
Quick Reference — Which Fix For Your Situation?
| Your situation |
Scenario |
Start with |
| Error only when creating invoices or a specific form |
A |
Method 1 — test transaction |
| Test transaction clears error but it keeps coming back |
A |
Method 2 — recreate template |
| Error across multiple functions, appeared after power cut |
B |
Method 3 then 4 |
| Verify Data shows no issues but error persists |
B |
Method 5 — repair install |
| All methods tried — nothing has worked |
B |
Method 6 then call us |
Frequently Asked Questions About Error C=387
Is my financial data at risk when C=387 appears?
In the vast majority of cases — no. Template-related C=387 errors (Scenario A) have no interaction with your financial data whatsoever. File damage scenarios (Scenario B) may indicate some internal data corruption, but your records are rarely lost — the QuickBooks Rebuild Data tool repairs the damage in most cases. Always back up before running any repair, which is standard practice at QuickFix Bookkeeping regardless of the error type.
Why does the error only happen with invoices and not other transactions?
Because the invoice template is damaged — specifically your invoice template, not the form type in general. QuickBooks applies a template to each form type when it renders. If the template assigned to invoices is corrupted, every invoice attempt triggers C=387, while estimates, sales receipts, and reports — which use different templates — work perfectly. The fix is identifying and inactivating that specific template (Method 2), not repairing the entire installation.
How is C=387 different from other C-series errors like C=272 or C=184?
All C-series errors are unexpected crash errors in QuickBooks — they share the same error message format but point to different crash zones. C=272 is specifically related to company file data corruption and the Verify/Rebuild cycle. C=184 has the notable leap year trigger and file location issues. C=387 is distinctive in that it most commonly originates from form template damage — something the other C-series errors do not share. The template fix in Method 1 is unique to C=387 and would not help with C=272 or C=184.
How do I prevent C=387 from recurring?
For template-related C=387, the best prevention is to avoid heavily customising a single template to the point where it becomes the only usable version — always keep a backup of custom templates or maintain the default QuickBooks template as a fallback. Keep QuickBooks updated, as Intuit patches known C-series triggers regularly. For file damage scenarios, the prevention is consistent daily backups and proper shutdown procedure — never force-close QuickBooks mid-transaction. At QuickFix Bookkeeping we build automated daily backup routines into every client's QuickBooks setup so a single error never becomes a data crisis.
Related QuickBooks C-Series Errors
C=387 Still Appearing After Six Methods?
Let a Certified ProAdvisor
Diagnose and Fix It in One Session.
Certified Intuit ProAdvisors · QuickBooks Desktop Specialists
When C=387 persists beyond the standard methods, it almost always points to a Windows registry or .NET issue that needs hands-on system-level diagnosis. At QuickFix Bookkeeping, our certified ProAdvisors resolve C-series errors daily — identifying the exact cause, applying the right fix, and protecting your company data throughout. Most cases resolved in a single session.
Book a Free 30-Minute Consultation
No obligation. Same-day response. QuickBooks working again today.
