QuickBooks Terminal Server Errors (RDS / RDP)

Let’s Dive in to see…

How to Fix QuickBooks Terminal Server Errors
(RDS / RDP)

Schedule a call to fix QuickBooks Errors
QuickBooks Payroll Error PS060

Setting up QB on RDS for the first time?

See our installation guide

QuickBooks Desktop · Remote Desktop / Terminal Server

How to Fix QuickBooks Terminal Server Errors (RDS / RDP)

Common errors when running QuickBooks on Windows Remote Desktop Services (RDS): "The selected path is not on a local drive", repeated Windows admin credential prompts, multi-user access failing after upgrade, or QB crashing mid-session on the RDS server.

Only QuickBooks Enterprise Solutions is officially designed and supported for RDS/Terminal Server environments. At QuickFix Bookkeeping, the most commonly missed step is the change user /install command before installing QB on the RDS server — without it, QB installs in user-specific mode and breaks for all other RDS users.

The QuickFix Bookkeeping Distinction — Only QB Enterprise Is Officially RDS-Supported

This is the single most important fact for Terminal Server deployments — and the one that causes most installation failures.

QB Enterprise — supported

Officially designed for RDS. Can be installed for all users on a Terminal Server using the correct installation mode. All versions from Enterprise 12.0 onward support RDS.

QB Pro / Premier — NOT supported

Intuit's EULA prohibits using QB Pro or Premier on Terminal Server. These versions are not designed for multi-session environments and will produce errors and instability on RDS.

QB 2024 (64-bit) vs 2021 (32-bit)

QB Enterprise 2024 is 64-bit — behaviour on RDS differs from 2021 (32-bit). Windows Server 2012 is not supported by QB 2024; minimum is Windows Server 2016.

The change user /install requirement — why it matters: Windows Terminal Server tracks application installations per-user or per-machine. If QB is installed while in normal mode, Windows stores QB's settings (registry, file paths) only for the installing user — all other RDS users can't run it correctly. Before installing QB on any RDS server, run change user /install in an Administrator CMD to put the server into install mode. After QB setup completes, run change user /execute to return to normal mode. This applies to every QB installation or update on RDS.

Common QuickBooks Terminal Server Errors and Their Causes

"Selected path is not on a local drive"

QBDSM gives this error when the company file path is a UNC network path (\\server\share\...) rather than a local drive letter. QBDSM only scans local paths. Fix: map the network share to a drive letter (e.g., Z:) → use the drive letter path in QBDSM. Or store the company file on a local drive on the RDS server itself.

Admin Credential Prompt Loop

QB pops up requesting Windows Administrator credentials every time users open it on the RDS server — or intermittently every week. Most common cause: the QB shortcut has a UNC path (\\computername\c$\...) instead of a local path (C:\...) — Windows changed it when the shortcut was copied from another machine. Fix: right-click shortcut → Properties → Target → change to the local path C:\Program Files\Intuit\...

QB Installed Without change user /install

QB was installed without putting the server in install mode first. Only the installing admin user can run QB — all other RDS users get errors or can't open company files. Fix: uninstall QB → run change user /install → reinstall QB → run change user /execute. Then reinstall for all users.

Multi-User Access Fails After Upgrade

After upgrading QB Enterprise on the RDS server, multi-user access stops working intermittently. Common cause: the QB 2024 (64-bit) Database Server Manager needs to be reinstalled separately on Server 2016+. Also: QuickBooksDB34 (or the appropriate service for the version) must run as Local System — changing it to another service account breaks QB 2024 on RDS.

Previous Session Lock (User Forgot to Log Out)

A user logged into QB via RDS and disconnected (closed the RDP window) without logging out of QB. QB still shows that user as logged in — other users get "company file is in use" errors. Fix: Company → Users → View Users → find the session → have the user sign out, or as admin end their RDS session via Task Manager → Users tab → Log Off.

Windows Server 2012 Not Supported (QB 2024)

QB Enterprise 2024 requires Windows Server 2016 or later. Upgrading from QB 2021 (which ran on Server 2012) to QB 2024 without upgrading the server OS produces compatibility errors on RDS. Solution: upgrade the server to Windows Server 2016 or 2019 before upgrading QB Enterprise to 2024.

How to Set Up and Fix QuickBooks on Terminal Server / RDS

If starting fresh: the correct RDS installation sequence. If fixing an existing broken setup: targeted fixes below.

METHOD 1 Correct RDS Installation (Fresh Setup or Reinstall) The right way — do this for any new QB install on RDS
1

Verify prerequisites: Confirm QB Enterprise (not Pro/Premier). Confirm Windows Server 2016+ for QB 2024. Log into the RDS server as a local Administrator (not a domain user with local admin rights — a true local admin).

2

Enable install mode: open Administrator CMD → type change user /install → press Enter. CMD confirms "User session is ready to install applications." This puts Terminal Server in per-machine installation mode.

3

Install QB Enterprise: run the QB installer → when prompted for installation type → choose "I'll be using QuickBooks on this computer AND I'll be storing our company file here" → complete installation. Set up Database Server Manager.

4

Return to execute mode: Administrator CMD → type change user /execute → press Enter. CMD confirms "User session is ready to execute applications." RDS returns to normal mode. Test by logging in as an RDS user (not admin) and opening QB.

METHOD 2 Fix Admin Credential Prompt Loop — Check Shortcut Path UNC path in shortcut causing repeated prompts
1

Right-click the QB shortcut users click → Properties → Target field. If Target shows a UNC path starting with \\computername\ → change it to the local path: C:\Program Files\Intuit\QuickBooks Enterprise Solutions XX.0\QBW32Enterprise.exe (or the correct local path for your QB version). Also confirm that the QuickBooksDB service (Services.msc) is set to run as Local System — changing to a named service account is a common cause of the recurring prompt.

METHOD 3 Fix QBDSM "Not a Local Drive" Error — Map Drive or Move File Company file on UNC network path
1

Option A — Map to drive letter: on the RDS server, map the network share to a persistent drive letter (File Explorer → This PC → Map network drive → choose a letter → check "Reconnect at sign-in"). Add that drive letter path to QBDSM (not the UNC path). Option B — Move to local drive: copy the company file to a local folder on the RDS server (e.g., C:\QB\CompanyFiles\) → add that local path to QBDSM → scan → update all users' QB to open from the local path.

METHOD 4 Fix Session Lock — Orphaned User Logged Into QB User disconnected RDP without logging out of QB
1

As RDS admin: open Task Manager → Users tab → find the disconnected user's session → right-click → Log Off. Then in QB as admin: Company → Users → View Users → confirm the user no longer appears as logged in. Going forward: set an RDS Group Policy to log off disconnected sessions after a timeout (GPO: Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Session Time Limits → Set time limit for disconnected sessions → 1 hour).

METHOD 5 Fix Intermittent Multi-User Failure — Restart QB Services QB 2024 multi-user drops after several hours
1

Services.msc → find QuickBooksDB34 (or the version-appropriate service) → confirm Startup Type: Automatic → right-click → Restart. Also restart QBCFMonitorService. If this recurs daily: set up a scheduled task to restart these services nightly during off-hours. For QB 2024, ensure the service runs as Local System (not a custom service account — this is a documented QB 2024 on RDS issue). Run QBDSM → Scan Folders after restarting services.

Frequently Asked Questions

Can I run QuickBooks Pro or Premier on a Terminal Server?
No — Intuit's EULA prohibits using QB Pro or Premier on Terminal Server/Remote Desktop Services. Only QuickBooks Enterprise Solutions is officially designed and licensed for RDS environments. Running Pro or Premier on RDS is a licensing violation and will produce technical problems: the software isn't designed for multiple simultaneous user sessions and will fail in unpredictable ways. If your business needs multi-user RDS access to QB, you must use QB Enterprise, which includes the per-user licensing model and the application architecture needed for stable RDS operation.
Why does QB 2024 Enterprise behave differently on RDS compared to QB 2021?
QB Enterprise 2024 is a 64-bit application; QB 2021 was 32-bit. This architectural change means QB 2024 uses different Windows registry paths, different service names (QuickBooksDB34 vs QuickBooksDB31), and has different Windows Server version requirements (Server 2016 minimum vs Server 2012 for 2021). The Database Server Manager was also rebuilt for 64-bit, which is why companies that upgraded from 2021 to 2024 on Server 2012 hit compatibility errors — the 64-bit QBDSM won't run on Server 2012. Additionally, the QuickBooksDB service behaviour changed: in 2024, it must run as Local System on RDS for correct multi-user operation, whereas 2021 was more tolerant of custom service accounts.

Related QuickBooks Errors

QuickBooks Enterprise on Terminal Server — Persistent Errors?

Let QuickFix Bookkeeping Configure Your RDS Environment.

RDS QuickBooks deployments involve server OS compatibility, 32-vs-64-bit service differences, QBDSM configuration, and multi-user licensing — we diagnose and fix the specific combination causing your errors.

Book a Free 30-Minute Consultation

No obligation. Same-day response.