QuickBooks Company File Error Guide · 6xxx Series
How to Fix QuickBooks Error 6000 82
QuickBooks could not open the company file and displayed: "An error occurred when QuickBooks tried to access the company file. Error codes: (-6000, -82)"
The -82 sub-code is the diagnostic key — it specifically means a single-user mode conflict. Either another user has the file open exclusively, or a stale lock file is blocking access. At QuickFix Bookkeeping, the lock file check takes 30 seconds and resolves the majority of 6000-82 cases immediately.
The QuickFix Bookkeeping Distinction
The sub-code after 6000 tells you exactly what kind of failure occurred. -82 is not the same as -83, -77, or -106 — and they need different first fixes.
-6000, -82
This page — file locked
Single-user mode conflict or stale lock file. Check for .lock file first.
-6000, -83
Damaged file / wrong path
File data is damaged or path is incorrect. Start with path verification.
-6000, -77
Network permission
QB cannot access the file over the network. QBDSM scan first.
-6000, -106
Cannot read file
Same as -1006. File data unreadable. File Doctor first.
What -82 specifically means: When QuickBooks opens a company file, it creates a lock file (YourCompanyFile.QBW.lock) to signal to other users that the file is in use. When the session ends normally, QB deletes the lock file. If QB crashed, the computer was powered off, or the session ended abnormally — the lock file remains on disk. The next time anyone tries to open the file, QB finds the lock file, assumes someone still has it open in single-user mode, and returns -6000, -82. Deleting the stale lock file removes the false signal and resolves the error immediately.
What Is QuickBooks Error 6000 82?
Error code
6000, -82
6xxx Series · Company File
Related: -6000 -83 · -6000 -77 · -6150
What it means
Error 6000-82 means QuickBooks attempted to open the company file and found it is either currently open in single-user mode by another user, or a stale lock file exists from a previous session that ended abnormally. The error can also appear when there is a hosting conflict on the network — a workstation has "Host Multi-User Access" enabled when it should not — causing QB to lose track of where the authoritative copy of the file is.
Your data is almost certainly safe. 6000-82 is a file access conflict error — the file itself is not damaged in the vast majority of cases. Once the lock or hosting conflict is resolved, the file opens normally.
What Causes QuickBooks Error 6000 82?
🔒
Stale Lock File
Most common cause — a previous QB session ended abnormally (crash, power failure, force-quit) and left a .QBW.lock file in the company file folder. QB reads this as "file is in use" and refuses to open it. Deleting the lock file resolves this in 30 seconds.
👤
File Open in Single-User Mode
Another user genuinely has the company file open in single-user mode on another computer. QB cannot allow a second user to open a file that is already open exclusively. The user must switch to multi-user mode or close the file before others can access it.
🖥️
Workstation Hosting Conflict
A workstation has "Host Multi-User Access" enabled, creating a conflict with the server. The conflicting host intercepts the file open request and cannot complete it, returning -82. Turn off hosting on all workstations — only the server should host.
📝
Extra Space in Filename
A space between the company file name and the .QBW extension (e.g. "MyCompany .QBW" instead of "MyCompany.QBW") causes QB to fail the file open with -82. This is confirmed in Intuit's own documentation — remove any trailing spaces from the filename.
📄
Damaged .TLG or .ND File
A corrupted Transaction Log (.TLG) or Network Descriptor (.ND) file can cause QB to misread the file state and return -82. Renaming these files forces QB to recreate them from scratch and often clears the error.
💾
Damaged Company File Data
In a minority of 6000-82 cases, the company file itself has internal data damage that prevents QB from opening it. This is less common with -82 than with -83 or -106 — but if all lock/hosting fixes fail, run File Doctor and Verify/Rebuild to check for file damage.
How to Fix QuickBooks Error 6000 82 — Step by Step
Start with Method 1 — the lock file check takes 30 seconds and resolves the majority of 6000-82 errors immediately.
METHOD 1
Check for and Delete the Stale Lock File
30-second fix — do this first
A stale lock file is the most common cause of 6000-82. Before doing anything else, check the company file folder for a lock file. If one exists from a session that ended abnormally, deleting it resolves the error immediately — no repair tools needed.
1
Navigate to the folder containing your company file. This is usually C:\Users\Public\Documents\Intuit\QuickBooks\Company Files unless you moved it.
2
Look for a file named YourCompanyFile.QBW.lock (same name as your company file but with .lock added). If it exists — right-click → Delete.
3
Try opening the company file in QuickBooks. If it opens — the stale lock file was the entire problem. No further steps needed.
QuickFix tip: Before deleting the lock file, confirm that QuickBooks is completely closed on ALL computers on the network — not just the one showing the error. If even one computer still has the file open, deleting the lock file and then opening on another computer will corrupt the data. Open Task Manager on each computer and end any QBW32.exe processes before proceeding.
METHOD 2
End All QuickBooks Processes and Reopen
If no lock file found — QB still thinks file is in use
If no lock file exists but 6000-82 persists, a QuickBooks process is still running in memory on one of the computers — holding the file open invisibly. End all QB processes across all networked computers.
1
On each computer on the network: right-click taskbar → Task Manager → Details tab. Find and End Task on each of these processes: QBW32.exe, QBDBMgrN.exe, QBCFMonitorService.exe, QBUpdate.exe.
2
After all processes are ended on all computers, wait 30 seconds, then reopen QuickBooks on the server computer first. Try to open the company file.
METHOD 3
Fix Hosting — Turn Off on All Workstations
If error appears in multi-user environment
A workstation with hosting enabled creates a conflict that produces 6000-82. Only the server should have "Host Multi-User Access" turned on. Check every computer on the network.
1
On each workstation (not the server): open QuickBooks without opening the company file → File → Utilities. If you see "Stop Hosting Multi-User Access" — click it to disable. If you see "Host Multi-User Access" — leave it, this workstation is correctly configured.
2
On the server: File → Utilities → confirm "Stop Hosting Multi-User Access" is shown (meaning hosting is ON). If "Host Multi-User Access" shows instead — click it to enable hosting on the server.
METHOD 4
Remove Extra Spaces from the Company File Name
Confirmed cause in Intuit documentation
A trailing space in the company file name — between the file name and the .QBW extension — is a documented cause of -6000, -82 that Intuit's own support confirms. Easy to miss because the space is invisible.
1
Log out of QuickBooks on all computers. Navigate to the company file folder. Right-click the .QBW file → Rename.
2
In the filename, place your cursor just before .QBW and press Backspace to remove any spaces. The name should read CompanyName.QBW with no spaces anywhere. Press Enter to save.
3
Try opening the file. If QB was showing 6000-82 specifically because of the space, it will open normally after the rename.
METHOD 5
Rename .ND and .TLG Files, Run QBDSM Scan
If previous methods haven't resolved it
Corrupted .ND or .TLG files can cause QB to misread the file state and produce -82. Renaming them forces QB to recreate both from scratch. The QBDSM scan regenerates the .ND with the correct current server path.
1
In the company file folder, find YourCompanyFile.QBW.ND and YourCompanyFile.QBW.TLG. Right-click each → Rename → add .old to both names.
2
Open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager → Start Scan on the company file folder. This regenerates a fresh .ND file. Then retry opening the company file.
METHOD 6
Run QuickBooks File Doctor
If file damage is suspected
If all previous methods have not resolved 6000-82, the company file itself may have minor internal damage causing QB to return -82 on open. File Doctor handles both network and file-level diagnostics.
1
Open QuickBooks Tool Hub → Company File Issues → Run QuickBooks File Doctor. Select your company file → Check your file and network → enter admin password → Next.
2
Allow up to 15 minutes for the scan. After completion, try opening the company file. If it opens — run File → Utilities → Verify Data immediately to confirm data integrity before continuing work.
Quick Reference — Match Your Clue to the Fix
| Your situation |
Most likely cause |
Start with |
| Error appeared after QB crashed or power failure |
Stale lock file left behind |
Method 1 — delete lock file |
| No lock file found, QB process may still be running |
Zombie QB process holding file |
Method 2 — end all QB processes |
| Multi-user environment, multiple computers affected |
Workstation has hosting enabled |
Method 3 — fix hosting settings |
| File was recently renamed or copied from another location |
Space in filename |
Method 4 — remove filename spaces |
| All above tried — still 6000-82 |
Damaged .ND/.TLG or file data |
Methods 5–6 or call us |
Frequently Asked Questions
Is it safe to delete the .QBW.lock file?
Yes — but only after confirming QuickBooks is completely closed on every computer that has access to the company file. The .lock file is not your data. It is purely a signal file that QB creates to say "I have this file open" and deletes when it closes normally. Deleting a stale lock file removes a false signal — it does not affect your company data in any way. The risk is deleting a legitimate lock file while someone genuinely has the file open. Always check Task Manager on all networked computers and end all QBW32.exe processes before deleting the lock file.
How is Error 6000-82 different from Error 6000-83?
The sub-code identifies the specific failure type. -82 means a single-user mode conflict — the file is locked, either genuinely by another user or by a stale lock file. The file data itself is typically intact. -83 means the file path is wrong or the file data is damaged — QB found the file but cannot read it correctly. The fixes are completely different: -82 starts with the lock file and hosting settings. -83 starts with verifying the file path and running File Doctor. If you apply -83 fixes to a -82 error (or vice versa), you will waste significant time without resolving the issue.
Why does QuickBooks keep producing stale lock files?
Stale lock files occur when a QuickBooks session ends abnormally rather than through a proper File → Close Company sequence. Common triggers include forced computer restarts during Windows Updates (particularly overnight updates when QB was left open), power failures, QuickBooks crashes, or users closing QB by pressing the X button while the company file is still performing background operations. The long-term fix is to configure Windows Update to only install updates at a scheduled time when users are logged out, and to train users to always use File → Close Company before shutting down rather than clicking the X on the QuickBooks window.
Related QuickBooks Company File Errors
Company File Won't Open? Team Locked Out?
Error 6000-82 Persisting After All Six Methods?
Let's Get Your File Open Today.
Certified Intuit ProAdvisors · QuickBooks Data Recovery Specialists
A persistent 6000-82 after lock file and hosting fixes usually means the company file has internal damage that needs specialist attention. At QuickFix Bookkeeping, our certified ProAdvisors diagnose and repair company file errors and get your team back in QuickBooks in a single session.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Company file access restored fast.
