QuickBooks Error Code C 38

Let’s Dive in to see…

How to Fix QuickBooks Error Code C=38

Schedule a call to fix QuickBooks Errors
QuickBooks Payroll Error PS060

QuickBooks C= Series Error · File Write Failure

How to Fix QuickBooks Error C=38

QuickBooks displays an unrecoverable error with code C=38 — typically when saving, recording, or backing up data.

C=38 is a file write failure — QB attempted to write data to the company file on disk and the write operation failed at the OS level. At QuickFix Bookkeeping, C=38 is fundamentally different from most other C= errors: while codes like C=47 or C=224 indicate the company file is already corrupted, C=38 means QB couldn't successfully write new data — the issue may be the disk, the permissions, or the available storage rather than existing file damage.

The QuickFix Bookkeeping Distinction — C=38 Is a Write Error, Not a Read Error

Most C= errors are read failures — QB tries to read existing data and finds it corrupted. C=38 is a write failure — the existing file may be fine, but QB can't save new data to it.

C=38 — write failure (this page)

QB attempted to write data to disk — the write failed. Cause is disk-side: full disk, disk error, permissions, or antivirus blocking. Fix targets the write environment, not the file contents.

C=9, C=47, C=224 — read failures

QB attempted to read existing data — what was read is invalid or corrupted. Cause is file-side: existing data in the .QBW is damaged. Fix targets the file contents via Rebuild or restore.

C=38 diagnostic checklist — check these before file repair: (1) Disk space: right-click the drive → Properties → check Free Space. QB needs at least 2× the company file size free to write safely. (2) Disk errors: run chkdsk /f C: in Administrator CMD on the drive hosting the file. (3) Write permissions: right-click company file folder → Properties → Security → confirm your user account has Full Control. (4) Antivirus: temporarily disable and retry the operation that triggered C=38. If it works: add QB's company file location to AV exclusions.

What Causes QuickBooks Error C=38?

Disk Full or Near-Full

Primary C=38-specific cause — when the drive hosting the company file is full or nearly full, QB can't write new data during save or backup operations and reports C=38. Check: right-click the drive → Properties → Free Space. QB needs at minimum 2× the .QBW file size free. If the file is 500MB, the drive needs at least 1GB free at all times.

Disk Bad Sectors — Write Error

Bad sectors on the disk where QB tries to write the company file data cause the write to fail. Unlike C=9 (read failure from bad sectors), C=38 indicates the write path hit a bad sector. Run chkdsk /f to mark and remap bad sectors. If chkdsk finds many bad sectors, the drive is failing and should be replaced immediately — copy the company file to a new drive.

Insufficient Write Permissions

The Windows user account running QB doesn't have write permission to the company file folder. Common after Windows updates that reset folder permissions, or when a company file is moved to a new folder without setting up permissions. QB can read the file (which is why it opens) but can't write back to it. Fix: folder Properties → Security → Full Control for QBDataServiceUser and current user.

Antivirus Blocking the Write Operation

Real-time antivirus scanning intercepts QB's write operation to the .QBW file, delays it, or blocks it entirely — QB's write times out and reports C=38. The QB company file location and QB's processes (QBW32.exe, QBDBMgrN.exe) should be in AV exclusions to prevent this. This is a common C=38 cause that disappears when AV is temporarily disabled.

Network Share Write Failure

When the company file is stored on a network share and the share connection drops or has write permission issues, QB's writes to the file fail with C=38. The file is visible (read access) but writes are blocked by the share permissions. Check the network share's write permissions and ensure the connection is stable before retrying.

File Locked by Another Process

Another application (backup software, antivirus scanner, Windows Indexing Service) has locked the .QBW file exclusively while QB tries to write. QB can't get a write lock on its own file and fails with C=38. Check Task Manager for other processes accessing the QB file. Disable Windows Indexing for the company file folder.

How to Fix QuickBooks Error C=38

Check disk space, permissions, and antivirus first — C=38 is a write environment problem, not necessarily a file corruption problem.

METHOD 1 Free Disk Space + Run chkdsk + Fix Permissions C=38-specific write environment fixes
1

Disk space: right-click the drive → Properties → confirm Free Space is at least 2× the .QBW file size. Delete temp files, empty Recycle Bin, or move data to free space. Disk errors: Administrator CMD → type chkdsk /f C: (or the appropriate drive letter) → schedule for next restart → restart. chkdsk marks bad sectors and remaps them so QB can write around them.

2

Fix permissions: right-click company file folder → Properties → Security → Edit → add your user account AND QBDataServiceUser[XX] with Full Control → Apply. Disable Windows Indexing: right-click the folder → Properties → General tab → uncheck "Allow files in this folder to have contents indexed" → Apply. Retry the operation that triggered C=38.

METHOD 2 Disable Antivirus + Check File Lock AV or another process blocking QB writes
1

Temporarily disable real-time AV → retry the operation that triggered C=38. If it succeeds: the AV was blocking the write. Re-enable AV → add QB's company file folder and QB executable folder to AV exclusions rather than leaving AV disabled. Check file lock: Task Manager → Details tab → look for any process with QBW in the file access (or use Sysinternals Process Monitor to see what has the .QBW file open). Close any non-QB applications accessing the file before retrying.

METHOD 3 Copy File to New Drive + Verify/Rebuild Disk has bad sectors or is failing
1

If chkdsk found many bad sectors or the disk is old: copy the .QBW to a different, healthy drive → set up QB to use the new location → run Verify Data on the copied file to check for any file damage that occurred before the write failure. If Verify shows C= errors in QBWin.log: run Rebuild → Verify again. Replace the failing drive before returning to normal use.

Frequently Asked Questions

If C=38 is a write failure, does it mean my existing company file data is safe?
Usually yes — C=38 fires before the write completes, meaning the new data QB was trying to save wasn't written. Your existing company file data (already on disk) is generally intact. However, if C=38 occurred repeatedly over multiple sessions where QB attempted and failed to write, there's a risk that partial writes created some internal inconsistency. After fixing the write environment (disk space, permissions, AV), always run Verify Data to check that the existing file is clean. If Verify shows any C= errors in QBWin.log after fixing C=38, those would indicate that some of the repeated failed writes did cause secondary damage that needs to be addressed with Rebuild or restore.

Related QuickBooks Errors

C=38 Recurring After Fixing Disk Space and Permissions?

Let QuickFix Bookkeeping Diagnose the Write Environment.

Recurring C=38 after fixing obvious causes typically means a failing disk with intermittent bad sectors (that chkdsk can't catch in a single scan) or a network share with intermittent write permission drops.

Book a Free 30-Minute Consultation

No obligation. Same-day response.