QuickBooks Company File Error · 6000 Series
How to Fix QuickBooks Error 6000, 95
QuickBooks displays: "An error occurred when QuickBooks tried to access the company file. Please try again. (-6000, -95)"
Error 6000, 95 means Windows denied QuickBooks permission to read or access the company file — most commonly when the file is stored on external media (USB, flash drive, network drive) that QB cannot get OS-level read access to. At QuickFix Bookkeeping, the definitive diagnostic is simple: copy the file to the local C: drive and open it. If it opens — permissions on the original location was the entire problem.
The QuickFix Bookkeeping Distinction — What the -95 Sub-Code Means
The number after the comma in a 6000-series error tells you the type of failure. -95 is a permissions and access error — different from the other 6000 sub-codes.
-6000, -95 — this page
Windows OS denied QB read/write access. File on external storage, permissions wrong, or QBWUSER.INI corrupted.
-6000, -82
Single-user lock conflict or stale .lock file. Fix: delete .QBW.lock file.
-6000, -77
Network connectivity issue. QB can't reach the file over the network.
-6000, -83
File path wrong or file data damaged. QB can find the location but can't read the content.
The definitive diagnostic for -95 — the local drive test: Copy the company file (.QBW) from its current location to your local C: drive (e.g. Desktop). Open it from there. If it opens without error — the problem is 100% the original location's permissions or access rights. The file itself is fine. Fix the location, not the file. If it fails on the local drive too — the problem is the QB installation or QBWUSER.INI. This test takes 30 seconds and tells you exactly which fix to apply.
What Causes QuickBooks Error 6000, 95?
Company File on External Storage or Network Drive
Primary cause — restoring or opening a company file directly from a USB drive, flash drive, external hard drive, or network share. Windows grants these devices restricted read permissions by default, and QB's database service often lacks the OS-level access needed. QB reports -95 (permission denied) rather than opening the file.
Insufficient Folder or File Permissions
The Windows user account or the QuickBooks service account (QBDataServiceUser) does not have Full Control over the folder containing the company file. Without Full Control, QB cannot open, read, or modify the .QBW file — producing the -95 access denied response.
Corrupted QBWUSER.INI File
QBWUSER.INI is QB's user configuration file — it stores the list of recently opened company files and their paths. When this file becomes corrupted, QB cannot properly load the user profile context needed to access the company file, triggering -95 even when the file and permissions are otherwise fine.
Multiple Machines Hosting the Company File
When more than one computer on the network has "Host Multi-User Access" enabled, access conflicts arise — multiple hosting processes compete for the file and Windows denies access to the secondary requestor with a -95 code. Only the designated server should host.
Firewall Blocking QB's File Access
Windows Firewall or antivirus can intercept QB's file access request and deny it at the OS level — which QB interprets as a -95 permissions error. The file exists and is readable, but the security software blocked QB's access attempt before it reached the file system.
Damaged QB Installation
A corrupted or incomplete QB installation leaves components in an inconsistent state — QB's internal file access routines may fail and report -95 even when the OS has granted appropriate permissions. The Install Diagnostic Tool resolves this variant.
How to Fix QuickBooks Error 6000, 95
Run the local drive test first — it tells you in 30 seconds whether the issue is location-based or installation-based, and points you to the right method.
METHOD 1
Copy File to Local C: Drive — The Diagnostic Test + Immediate Fix
Do this first — 30 seconds
1
Open Windows File Explorer. Navigate to the current location of your company file (.QBW) — whether on a USB drive, network share, or other location. Copy (not move) the .QBW file to your Desktop or a folder on the local C: drive.
2
Open QuickBooks → File → Open or Restore Company → Open a Company File → browse to the Desktop copy → Open. If the file opens without error — the original location's permissions are the problem. Move the company file permanently to a local folder such as C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\ and work from there. If it still fails on the local drive — proceed to Method 3 (QBWUSER.INI or installation issue).
METHOD 2
Set Full Control Permissions on the Company File Folder
Insufficient folder permissions
1
Right-click the folder containing your company file → Properties → Security tab → click Edit.
2
Check the list of users/groups. Find QBDataServiceUser[XX] (XX = your QB version year) and your current Windows user account. For each: ensure Full Control is checked in the Allow column. If they are not listed — click Add → type the account name → check Full Control → OK.
3
Also check that the company file itself (.QBW) is not marked Read-Only: right-click the .QBW file → Properties → General tab → confirm Read-only is NOT checked. Apply → OK. Retry opening in QuickBooks.
METHOD 3
Rename QBWUSER.INI and EntitlementDataStore.ecml
File fails to open even from local drive
1
Navigate to: C:\Users\[Username]\AppData\Local\Intuit\QuickBooks [Year]\ (AppData is a hidden folder — show hidden files in File Explorer first). Find QBWUSER.INI → right-click → Rename → add .OLD to the end: QBWUSER.INI.OLD.
2
Also navigate to: C:\ProgramData\Intuit\Entitlement Client\v8\. Find EntitlementDataStore.ecml → rename to .OLD. Open QuickBooks — it regenerates both files fresh on first launch. This resolves -95 caused by a corrupted user configuration.
METHOD 4
Fix Hosting + Run QBDSM Scan
Multi-user hosting conflict
1
On each workstation: QuickBooks → File → Utilities. If "Stop Hosting Multi-User Access" shows → click it to disable. Only the designated server should host. On the server: confirm "Stop Hosting Multi-User Access" shows (hosting ON). Then open QuickBooks Database Server Manager on the server → Scan Folders → add company file folder → Start Scan. After scan, retry opening from workstations.
METHOD 5
Run QuickBooks File Doctor + Install Diagnostic Tool
All above tried — installation or file damage
1
File Doctor: Tool Hub → Company File Issues → Run QuickBooks File Doctor. Select your company file → Check your file and network → admin password → let it run (up to 15 minutes). Install Diagnostic Tool: Tool Hub → Installation Issues → QuickBooks Install Diagnostic Tool → run (up to 20 minutes) → restart. This repairs corrupted QB installation components that may be causing internal -95 access failures. Also run as administrator: right-click QB icon → Run as administrator → retry opening the file.
Quick Reference
| Your situation |
Likely cause |
Start with |
| File on USB drive or network share |
External storage permissions denied |
Method 1 — copy to local C: drive |
| File is local but opens on admin account, not standard |
Folder permissions insufficient |
Method 2 — set Full Control permissions |
| File fails even from Desktop / local C: |
Corrupted QBWUSER.INI |
Method 3 — rename QBWUSER.INI |
| All of above tried — still getting -95 |
Damaged QB installation |
Method 5 — File Doctor + Install Diagnostic |
Frequently Asked Questions
Can I open or restore a QuickBooks file directly from a USB drive?
Not reliably. QuickBooks Desktop requires stable, uninterrupted read/write access to the company file throughout your entire session. USB drives use removable media permissions that Windows manages separately from local drives — and QB's database service frequently encounters the -95 access denial when working with files on USB. The correct approach is to always copy the file from the USB to a local drive first, work from the local copy, and then copy back to the USB when done. This applies to both opening .QBW files and restoring .QBB backup files.
What is QBWUSER.INI and why does renaming it help?
QBWUSER.INI is QuickBooks' user configuration file — it stores the list of recently opened company files, their last-known paths, and user preferences for the current Windows profile. When this file becomes corrupted (usually from an interrupted QB session or a Windows crash), QB loads an invalid configuration on startup and cannot properly establish the file access context it needs — producing a -95 error even when the file and folder permissions are correct. Renaming it to .OLD forces QB to create a fresh, uncorrupted version on next launch. You will need to re-browse to your company file on first open since QB's recently-used list was in the renamed file, but all your company data remains intact.
Is the company file data at risk when Error 6000, 95 appears?
In the vast majority of -95 cases, no. Error 6000, 95 is a permissions/access failure — QuickBooks was denied entry to the file before it could read or modify any data. The file itself remains intact and unchanged. The error happens at the OS access control layer, before QB's database engine engages with the file content. However, if you are restoring a backup and encounter -95, do not attempt to restore to a location where you do not have Full Control — the restoration process may fail partially and leave an incomplete .QBW file. Always restore to a local folder where your Windows account has Full Control.
Related QuickBooks Company File Errors
Error 6000, 95 Persisting After Permissions Fix and QBWUSER.INI Rename?
Let QuickFix Bookkeeping Restore Your File Access.
Certified Intuit ProAdvisors — Company File Specialists
Persistent -95 after all standard fixes usually indicates a deeper Windows permissions conflict, a domain policy restricting access, or a damaged QB installation requiring specialist diagnosis. Our ProAdvisors restore company file access in a single session.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Company file access restored fast.
