QuickBooks Error 1920 -- QuickBooks Database Manager Service Failed to Start

Error 1920 stops QuickBooks Desktop installation when the Database Manager service cannot start, but our engineers walk you through every trigger and resolution.

QuickBooks Desktop Error 1920 halts installation partway through with a message about the QuickBooks Database Manager service. The installer cannot proceed until that Windows service is running. Our engineers have resolved this error across every QuickBooks Desktop edition from older Pro installs through current Enterprise deployments, and in nearly every case the underlying cause is a Windows permissions conflict, a leftover service from a prior version, or an antivirus utility blocking the service binary.

What the error message says

The full message displayed by the installer reads:

Error 1920. Service 'QuickBooksDBxx' (QuickBooksDBxx) failed to start. Verify that you have sufficient privileges to start system services.

The xx in the service name corresponds to the QuickBooks version year — for example, QuickBooksDB33 for QuickBooks Desktop 2023 or QuickBooksDB35 for QuickBooks Desktop 2025.

What the code means

Error 1920 is a Windows Installer–level error, not a QuickBooks data error. It means the QuickBooks installation package instructed Windows to start a service as part of the setup routine, and Windows refused or failed. The QuickBooks Database Manager service is the background process that hosts company files for multi-user access. Without it running, the installer cannot complete the configuration phase and rolls back.

What triggers it

The most common triggers our engineers encounter are:

1. The same-named service already exists from a prior QuickBooks version and is disabled, stuck in a stopping state, or configured with incorrect logon credentials.
2. Insufficient Windows account privileges — the user running the installer is not a local administrator.
3. Antivirus or endpoint security software blocking the service executable (QBW32.exe or the Database Server Manager binary) from launching.
4. Corrupted .NET Framework installation that the service depends on at startup.
5. Windows service dependencies that are themselves stopped or disabled.

How to fix it

Scenario 1: A leftover service from a previous QuickBooks version (most common)

1. Press Win + R, type services.msc, and press Enter.
2. Scroll through the list and look for any service named QuickBooksDB followed by a version number. If you find more than one, or one from an older year, note each one.
3. Right-click each stale QuickBooksDBxx service and select Properties. Set Startup type to Disabled if the service is stuck.
4. Open Control Panel → Programs and Features (or Settings → Apps on Windows 10/11) and uninstall any prior QuickBooks versions you no longer need.
5. Download and run the QuickBooks Tools Hub from a trusted source, then use the QuickBooks Install Diagnostic tool under the Installation Issues tab. This tool cleans up orphaned service registrations automatically.
6. Restart the computer and re-run the QuickBooks installer.

Scenario 2: Insufficient Windows privileges

1. Confirm your Windows user account is a member of the local Administrators group. Open Settings → Accounts to verify.
2. If you are logged in as a standard user, sign out and sign back in with an administrator account.
3. Right-click the QuickBooks installer .exe and select Run as administrator.
4. If your machine is domain-joined, confirm that a domain Group Policy is not restricting service installation. A domain administrator may need to grant the Log on as a service right to your account or the QBDataServiceUserxx account the installer creates.

Scenario 3: Antivirus or endpoint security blocking the service

1. Temporarily disable your antivirus or endpoint protection suite.
2. Check whether any third-party firewall (separate from Windows Defender Firewall) is running and disable it temporarily as well.
3. Re-run the installer. If installation completes successfully, re-enable your security software immediately.
4. Add the following paths to your antivirus exclusion list to prevent recurrence:
   • C:\Program Files\Intuit\QuickBooks (and year-specific subfolders)
   • C:\Program Files\Intuit\QuickBooks Database Server Manager
   • The folder where your company file (.QBW) is stored

Scenario 4: Corrupted .NET Framework

1. Open Control Panel → Programs and Features → Turn Windows features on or off.
2. Note which .NET Framework versions are checked, then uncheck .NET Framework 3.5 and .NET Framework 4.x (the exact label varies by Windows version).
3. Restart the computer.
4. Return to the same dialog, re-check both .NET entries, and let Windows reinstall them.
5. Re-run the QuickBooks installer.

Scenario 5: Windows service dependencies are stopped

1. Open services.msc and verify that the following core Windows services are running and set to Automatic startup:
   • Remote Procedure Call (RPC)
   • Windows Management Instrumentation
   • DCOM Server Process Launcher
2. If any are stopped, right-click and select Start.
3. Re-run the installer.

How to prevent it recurring

Before installing or upgrading QuickBooks Desktop, our engineers recommend uninstalling older versions through Programs and Features rather than installing over them. Always run the installer from an administrator account, temporarily pause third-party antivirus, and run the QuickBooks Install Diagnostic tool from the Tools Hub at the first sign of trouble. For multi-machine deployments, install Database Server Manager on the host machine first, confirm the service is running in services.msc, and only then install QuickBooks on the workstations.