Mapped Network Drive Not Showing in QuickBooks? Fix It

Author : Mark John | Published On : 22 Sep 2026

A mapped network drive that shows fine in File Explorer but doesn't appear inside QuickBooks usually comes down to how QuickBooks was opened. If QuickBooks is running as administrator while the drive was mapped under a regular user session, or if the drive was mapped after QuickBooks was already open, QuickBooks simply won't see it. Persistent mapping settings, drive letter conflicts and stale login sessions cause the same problem. The steps below walk through each cause, starting with the one that explains most cases.

Why this happens more with QuickBooks than other programs

Windows keeps network drive mappings tied to the specific user session and privilege level that created them. QuickBooks often needs to run with administrator rights for certain features, and a drive mapped under a standard user session isn't visible to a program running elevated, even though both are technically the same Windows login. This mismatch is the single most common reason a drive appears in File Explorer but not inside QuickBooks's file browser.

Signs this is a mapping visibility issue

What you see What it usually means
The drive shows in File Explorer but not in QuickBooks's Open dialog QuickBooks is running at a different privilege level than the mapping
The drive appears after restarting QuickBooks, then disappears again later The mapping isn't set to reconnect automatically at sign-in
It works for one Windows user but not another on the same PC The mapping is specific to that user's session
The drive letter shows as available but empty when opened A different drive was previously using that letter
It worked before a restart, and now the drive letter doesn't appear anywhere The mapping wasn't set to persist across sessions

Step-by-step fixes

Fix 1: Check whether QuickBooks is running as administrator

This is the most common cause, so check it first.

  1. Close QuickBooks completely.
  2. Right-click the QuickBooks Desktop icon and check whether Run as administrator is enabled under Properties → Compatibility, or whether you've been launching it that way manually.
  3. Open QuickBooks normally, without administrator rights, and check whether the mapped drive now appears in File → Open or Restore Company.

If the drive appears without administrator rights, that confirms the cause. Either stop running QuickBooks as administrator if it isn't required for your setup, or remap the drive while running as administrator so both sessions see it (Fix 2).

Fix 2: Remap the drive while running as administrator

If QuickBooks genuinely needs administrator rights, the mapped drive needs to be created under that same elevated session.

  1. Right-click Command Prompt or PowerShell and choose Run as administrator.
  2. Type net use Z: ComputerNameSharedFolder /persistent:yes, replacing the drive letter, computer name and folder name with your actual details.
  3. Press Enter, then open QuickBooks (also as administrator) and check the Open dialog again.

Fix 3: Make the mapping persistent

A mapped drive that isn't set to reconnect automatically can disappear after a restart or sign-out.

  1. Open File Explorer and go to This PC.
  2. Right-click the mapped drive and check its properties, or remap it via Map network drive from the ribbon.
  3. When mapping, make sure Reconnect at sign-in is checked.
  4. Restart the computer and confirm the drive reappears automatically, then check QuickBooks.

Fix 4: Remove and recreate the mapping cleanly

Conflicting or outdated mapping information can cause a drive to behave inconsistently.

  1. Open Command Prompt and type net use to see all current mappings.
  2. Remove the problematic one with net use Z: /delete, replacing Z: with the correct letter.
  3. Remap it fresh using net use Z: ComputerNameSharedFolder /persistent:yes, or through File Explorer's Map network drive option.
  4. Restart QuickBooks and check again.

Fix 5: Use the full network path instead of a drive letter

Rather than troubleshooting the mapping itself, you can bypass it.

  1. In QuickBooks, go to File → Open or Restore Company.
  2. Choose Open a company file and click Next.
  3. In the file name field, type the full network path directly, such as ComputerNameSharedFolderCompanyFile.qbw, instead of browsing through a drive letter.
  4. Click Open.

This works even when the mapped letter isn't visible, since it bypasses the drive mapping entirely and goes straight to the shared folder.

Fix 6: Check for a drive letter conflict

  1. Open File Explorer and check which letters are currently in use under This PC.
  2. Confirm the letter you're mapping to isn't already assigned to something else, such as a USB drive or virtual drive that connects intermittently.
  3. If there's a conflict, remap to an unused letter.

Fix 7: Sign out and back in, or restart

Session-related mapping issues often clear with a fresh login.

  1. Sign out of Windows completely, then sign back in.
  2. If that doesn't help, restart the computer fully.
  3. Open QuickBooks and check the Open dialog again.

Fix 8: Confirm the host and Database Server Manager see the folder

If the mapping issue is really a symptom of a hosting problem rather than the drive itself, check the host side.

  1. On the host computer, open QuickBooks Database Server Manager.
  2. Go to Scan Folders and confirm the shared folder is listed and scanned correctly.
  3. If it's missing, add it and click Scan.

If workstations still can't reach the file after this, the issue may be broader network access rather than just the drive mapping. Our guide on QuickBooks Company File Not Found on mapped drive covers that wider scenario.

Quick decision guide

  • Drive shows in File Explorer, not in QuickBooks: almost always a privilege-level mismatch. Start with Fix 1.
  • Drive doesn't show anywhere after a restart: the mapping isn't persistent. Go to Fix 3.
  • Drive shows but is empty or wrong: a letter conflict. Go to Fix 6.
  • None of the above fixes it: bypass the mapping entirely with the full network path (Fix 5), which works regardless of the underlying cause.

A more reliable long-term setup

Mapped drive letters are convenient but fragile, since Windows can reassign them, mappings can fail to persist, and privilege mismatches are a recurring source of exactly this problem. Where practical, point QuickBooks at the full network path (ComputerNameFolderName) instead of a drive letter for the company file. It sidesteps this entire category of issue.

When to get professional help

Consider getting help if the drive still won't appear after remapping it correctly, the issue affects multiple workstations, or you're not sure whether QuickBooks needs to run as administrator in your setup. A QuickBooks professional or IT support can check the network configuration and QuickBooks settings together. You can reach BizBooksAdvice at +1-866-408-0444.

Frequently asked questions

Why does my mapped drive show in File Explorer but not in QuickBooks?
This almost always means QuickBooks is running at a different privilege level, usually as administrator, than the session that created the drive mapping. Remap the drive under the same elevated session, or stop running QuickBooks as administrator.

Does QuickBooks need to run as administrator?
Not always. Some setups need it for specific features, but many don't. If you don't have a specific reason to run it elevated, running it normally avoids this mapping mismatch entirely.

What does "persistent" mean when mapping a network drive?
It means Windows will reconnect the drive automatically every time you sign in, rather than only for the current session. Without it, the mapping can disappear after a restart.

Is it safer to use a network path instead of a mapped drive?
For QuickBooks specifically, yes. A full network path (ComputerNameFolderName) avoids drive letter conflicts, privilege mismatches and mappings that don't persist, all of which can affect a mapped letter.

Why does the drive letter sometimes point to the wrong folder?
This happens when a previously used drive letter is reassigned to a different device or share, and Windows doesn't always warn you when this happens.