QuickBooks Company File Error Guide · 6xxx Series
How to Fix QuickBooks Error 6150
QuickBooks could not open your company file and displayed: "We're sorry. QuickBooks couldn't open your company file. Error codes: -6150, -1006"
The sub-code -1006 is the critical detail — it means "file cannot be read." Before any repair attempt, you must confirm the file has not been encrypted by ransomware. At QuickFix Bookkeeping, the first 60 seconds of any 6150 investigation is a CryptoWall check — because attempting data recovery on an encrypted file is wasted effort.
⚠ Do This Before Any Repair Attempt — CryptoWall Check
Error 6150 -1006 is one of the specific errors triggered by CryptoWall ransomware and similar malware. If your company file has been encrypted, Verify/Rebuild, File Doctor, and Auto Data Recovery will all fail — because the file's contents are scrambled by the encryption. Do this check first:
Check your QuickBooks folder for these files:
Open File Explorer → navigate to your QuickBooks company file folder (usually C:\Users\Public\Documents\Intuit\QuickBooks). Look for files named DECRYPT_INSTRUCTIONS, HOW_TO_DECRYPT, or similar .txt or .html files with "decrypt" or "instructions" in the name.
What these files mean:
Found decrypt/instructions files: Your company file is encrypted by ransomware. Stop immediately. Do not attempt repair — contact your antivirus provider and a data recovery specialist. Intuit Data Services cannot repair encrypted files.
No such files found: Ransomware is not the cause. Proceed with the methods below.
The QuickFix Bookkeeping Distinction
The sub-code after 6150 tells you exactly what type of file access failure occurred. They need different fixes.
-6150, -1006
This page — cannot read file
File data is unreadable — corruption, encryption, or wrong file type. Fix: File Doctor → Verify/Rebuild → ADR → restore backup.
-6150, -816
File in use / locked
Another process has the file locked. Fix: end all QB processes, check for lingering QB sessions on the network.
-6150, -1005
Wrong file type
Attempting to open a Mac .qbw file in Windows QB, or a backup .qbb file as if it were a .qbw. Fix: correct the file or restore from proper backup.
What Is QuickBooks Error 6150?
Error code
6150, -1006
6xxx Series · Company File
Related: 6000-series · C=47 · Unrecoverable Error
What it means
Error 6150 means QuickBooks attempted to create, open, or access a company file — and failed at the file read level. The -1006 sub-code specifically means the file data itself cannot be read, which points to either file damage, ransomware encryption, an incorrect file type (e.g. opening a Mac .qbw in Windows), or a corrupted transaction log. Unlike network errors (H-series) or installation errors (1xxx), this error always traces back to the company file itself.
⚠
Do not attempt to run Verify/Rebuild before confirming no ransomware is present and taking a full backup. If the file is partially damaged, running Rebuild without a backup could cause irreversible data loss.
What Causes QuickBooks Error 6150?
💾
Corrupted or Damaged Company File
Primary cause — the .QBW company file has internal corruption. This can be caused by a system crash, power failure, or disk error during a file write operation — leaving the file partially written and internally inconsistent. QuickBooks cannot read past the corrupted data and fails with 6150 -1006.
🔒
Ransomware Encryption (CryptoWall)
CryptoWall and similar ransomware specifically target QuickBooks files — they encrypt the .QBW file and leave decrypt instructions in the folder. QuickBooks cannot read the encrypted content and reports -6150, -1006. This requires antivirus removal before any data recovery is attempted.
📋
Wrong File Type or Extension
Opening a QuickBooks for Mac company file (.qbw) in QuickBooks Desktop for Windows, or trying to open a backup file (.qbb) as if it were a working company file (.qbw), triggers 6150 because the internal file format does not match what Windows QuickBooks expects.
📄
Corrupted Transaction Log (.TLG)
The .TLG transaction log file stores recent uncommitted transactions. If this file is corrupted, QuickBooks cannot validate the company file on open and reports 6150. The fix is renaming the .TLG to force QuickBooks to create a new one — though recently uncommitted transactions may be lost.
📁
Problematic File Location
Company files stored on unreliable network shares, external drives, or cloud sync folders (OneDrive, Dropbox) can produce 6150 when the sync client locks the file during a write operation or the network path is intermittently unavailable. Moving the file to a local folder resolves this variant.
🔧
Corrupted QuickBooks Installation
A damaged QuickBooks installation can produce 6150 when the file read components within the program itself are damaged. Testing with a sample company file (which opens successfully on a healthy installation) confirms whether the problem is the installation or the company file.
How to Fix QuickBooks Error 6150 — Step by Step
Confirm no ransomware is present (see the warning box above), then work through these methods in order.
METHOD 1
Run QuickBooks File Doctor
Automated diagnosis and repair — start here
QuickBooks File Doctor runs simultaneous checks on both the company file's integrity and the network connection — automatically repairing what it can find. It is Intuit's own first-response tool for 6150 errors and resolves many cases without manual intervention.
1
Open QuickBooks Tool Hub → Company File Issues → Run QuickBooks File Doctor.
2
Select your company file from the dropdown (or click Browse to find it). Select Check your file and network. Enter your QuickBooks admin password. Click Next and wait — up to 15 minutes for large files.
3
Try opening the company file after the scan regardless of the tool's result — File Doctor often resolves the error even when it reports it could not fix the file.
QuickFix tip: Run File Doctor from the computer where the company file is stored (the server or the local machine), not from a workstation. File Doctor needs direct file system access to diagnose and repair the internal file structure — running it from a workstation gives it less access through the network path.
METHOD 2
Rename the .TLG File and Try Opening
If TLG corruption is blocking file open
The .TLG (Transaction Log) file stores uncommitted transactions. If it is corrupted, QuickBooks refuses to open the company file. Renaming it to .old forces QuickBooks to create a fresh .TLG and bypass the corrupted log — usually allowing the company file to open.
Note on data loss: Renaming the .TLG discards any transactions that were recorded in the log but not yet committed to the .QBW file. This is typically zero to a few transactions from the last session. Back up the .TLG before renaming it so those transactions can potentially be re-entered if needed.
1
Navigate to the folder containing your company file. Find YourCompanyFile.QBW.TLG. Right-click → Rename → change to YourCompanyFile.QBW.TLG.old.
2
Open QuickBooks and try to open the company file. If it opens — run File → Utilities → Verify Data immediately to check for underlying file damage before continuing work.
METHOD 3
Move Company File to a Local Folder and Retest
If file is on a network share or cloud sync folder
Company files stored on network shares, external drives, OneDrive, or Dropbox can produce 6150 due to file locking by sync clients or intermittent network access. Moving the file to a standard local path for testing confirms or eliminates the location as the cause.
1
Create a new folder directly on the C: drive — for example C:\QBTest. Copy (do not move) the .QBW file and its .TLG file into this folder.
2
In QuickBooks, go to File → Open or Restore Company → Open a company file. Navigate to C:\QBTest and open the file from there.
3
If it opens from C:\QBTest — the original storage location is the problem (network share, sync conflict, or permissions). Move the working file to a stable local or server location and update your QuickBooks file path. If it still fails from C:\QBTest — the file itself is damaged, proceed to Method 4.
METHOD 4
Verify and Rebuild Company File Data
If file opens but data is damaged internally
If File Doctor opened the file or the TLG rename allowed you in, run Verify/Rebuild to identify and repair internal data corruption. Always take a backup first — Rebuild modifies the file and you need a restore point if something goes wrong.
1
Backup first: File → Back Up Company → Create Local Backup. Save to a location outside the QBTest folder.
2
Verify Data: File → Utilities → Verify Data. If it reports no issues — the file is clean. If it reports damage — proceed to Rebuild.
3
Rebuild Data: File → Utilities → Rebuild Data. Allow the Rebuild to complete fully — do not interrupt it. Run Verify again after Rebuild to confirm the file is clean. If Verify still reports issues after two Rebuild passes, the damage is beyond what Rebuild can repair — proceed to Method 5.
METHOD 5
Use QuickBooks Auto Data Recovery (ADR)
Recovers data from QB's built-in emergency backup
QuickBooks automatically maintains an Auto Data Recovery copy of your company file — a recent backup stored in a hidden folder alongside your company file. This is separate from your manual backups and may be more recent. ADR is the recovery method to try when the main company file is too damaged to open directly.
1
Create a new folder: C:\QBTest. In the company file folder, find the hidden QuickBooksAutoDataRecovery folder (enable hidden files in File Explorer → View → Hidden items).
2
Copy the .QBW.adr file from the QuickBooksAutoDataRecovery folder into C:\QBTest. Also copy the current .QBW.TLG file (from the original company file folder) into C:\QBTest.
3
In C:\QBTest, rename the .QBW.adr file by removing the .adr extension — so it becomes YourCompanyFile.QBW. Open QuickBooks and open this file from C:\QBTest.
4
Run File → Utilities → Verify Data on the recovered file. If clean — copy this file back to your regular company file location to replace the damaged version.
QuickFix tip: Use the current .TLG from the original folder (not the .TLG.adr from the ADR folder). The current .TLG contains the most recent transaction log and pairing it with the ADR company file gives you the best chance of recovering the most recent data before the file was damaged.
METHOD 6
Restore from a Manual Backup
When ADR and File Doctor cannot repair the damage
If File Doctor, TLG rename, and ADR have not resolved 6150 — the company file damage is beyond what QuickBooks' built-in tools can repair. Restoring from a manual backup is the cleanest resolution, with the only cost being re-entering transactions created after the backup date.
1
Go to File → Open or Restore Company → Restore a backup copy → Local Backup → Next. Find your most recent .QBB backup file and restore it to a new file name (e.g. CompanyFile_Restored.QBW) to preserve the original damaged file.
2
Test the restored file — run Verify Data to confirm it is clean. Then compare the backup date against the damaged file's last-save date to understand which transactions need to be re-entered.
Quick Reference — Which Fix For Your Situation?
| Your situation |
Most likely cause |
Start with |
| 6150 -1006 on any company file open attempt |
Unknown — let File Doctor diagnose |
Method 1 — run File Doctor |
| Decrypt/instructions files found in QB folder |
Ransomware encryption |
Stop — call antivirus provider first |
| Error appeared after power failure or system crash |
Corrupted TLG |
Method 2 — rename .TLG |
| File stored on OneDrive, Dropbox, or network share |
Storage location issue |
Method 3 — move to local folder |
| File opens but has data errors inside |
Internal file corruption |
Method 4 — Verify/Rebuild |
| File won't open at all — all fixes failed |
Severe file damage |
Methods 5–6 or call us |
Frequently Asked Questions About Error 6150
What does the -1006 sub-code mean and why does it matter?
The number after the comma in a 6xxx error tells you what type of failure occurred at the file level. -1006 specifically means "file cannot be read" — the file exists but its contents are not valid QuickBooks data. This distinguishes it from -816 (file is locked by another process) or -1005 (wrong file type). Knowing the sub-code lets you skip irrelevant fixes — if you have -1006, the problem is in the file contents, not in who has the file open or whether the file extension is correct.
Can I store my QuickBooks company file on OneDrive or Dropbox?
Intuit officially does not support storing or opening QuickBooks company files directly from OneDrive, Dropbox, Google Drive, or similar cloud sync folders. The sync client continuously monitors and uploads file changes — during a QuickBooks write operation, the sync client can lock the file mid-write, leaving it in a corrupted state and producing error 6150. The correct approach is to store the company file on a local drive or a dedicated file server, and back it up to cloud storage separately (as a .QBB backup file) rather than syncing the live .QBW file.
My company file was damaged 78% according to Intuit support. Can it be recovered?
Intuit's damage percentage estimate is a rough indicator of how much of the file's internal data structure can be read. At 78% damage, QuickBooks' built-in tools (File Doctor, Rebuild) may not be able to fully repair the file. However, professional data recovery specialists and Intuit Data Services have more advanced tools that can sometimes recover data from severely damaged files that QuickBooks' own utilities cannot. At QuickFix Bookkeeping, our certified ProAdvisors have recovered data from files with significant damage levels — the first step is getting a direct assessment of what is recoverable before assuming all data is lost.
How do I prevent Error 6150 from recurring?
Five practices prevent most 6150 recurrences. Keep automatic backups enabled in QuickBooks (Edit → Preferences → Backup) so there is always a recent recovery point. Store the company file on a reliable local drive or server — never on a cloud sync folder, external drive, or USB stick used as the live working location. Run Verify Data monthly as a maintenance check — catching corruption early when it is minor is far easier than recovering from severe damage. Keep antivirus software current and add the QuickBooks company file folder to exclusions to prevent real-time scanning from locking the file during writes. And replace aging hard drives proactively — disk hardware failures are one of the leading causes of sudden company file corruption.
Related QuickBooks File and Data Errors
Company File Damaged? Data at Risk?
6150 Error Persisting After File Doctor and ADR?
Let's Recover Your Company File Today.
Certified Intuit ProAdvisors · QuickBooks Data Recovery Specialists
Severely damaged company files — beyond what File Doctor and Rebuild can repair — need professional data recovery. At QuickFix Bookkeeping, our certified ProAdvisors assess the QBWin.log, identify the exact damage scope, and recover the maximum possible data — without the multi-day Intuit Data Services wait and without risking further data loss.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Maximum data recovery.
