QuickBooks Error 1304: Install or Repair Fails on an Unavailable Drive

Error 1304 halts a QuickBooks Desktop install or repair when the drive it writes to disappears; here is how to clear it and complete the setup.

Error 1304 stops a QuickBooks Desktop installation or repair while files are being written. Behind it is almost always a drive problem: the installer cannot write to a path because the drive it points to is missing or unreadable. Our engineers see it most often on installs run from mapped network folders and USB media. This page explains what the code means and walks through the fix for each trigger.

What does the error message say?

In most releases the dialog reads:

Error 1304. Error writing to file: [file name]. Verify that you have access to that directory.

The file name varies. It names whichever component the installer was writing at the moment the drive dropped out, often with its full path. The same message can appear during a fresh install, during a repair, or while an update applies itself. Retrying on its own rarely helps, because the drive condition that caused the failure is usually still present.

What does the code mean?

Code 1304 comes from the Windows Installer engine, not from the accounting logic inside QuickBooks. The installer reports it when a write to disk fails. Two conditions produce that: the target path sits on a drive Windows can no longer see, or the account running setup lacks permission to write where it must. QuickBooks surfaces the failure and stops. The actual cause lives in the drive layout, the install source, or the Windows account.

What triggers error 1304?

• A mapped network drive disconnects while setup runs from it. A brief network outage or an offline share is enough; the drive letter stops resolving.
• Removable media vanishes mid-install: a USB stick or external drive unplugged, or a disc pulled from the tray.
• The downloaded installer sits on a disconnected drive, so setup cannot read its own payload.
• A repair reaches for the original install source path, and that path lived on media or a share that no longer exists.
• The install runs under a Windows account without administrator rights, so writes into protected folders fail.

How do you fix it?

The first two scenarios account for most of the cases our engineers handle.

Scenario: the mapped drive disappeared during setup.

1. Cancel the installer and note the drive letter shown in the message.
2. Open File Explorer and remap the network drive with the same letter, or confirm the share is back online.
3. Copy the entire installer folder from the share to a new folder on the internal hard drive.
4. Run the setup file from that local copy with Run as administrator.

Local is the reliable pattern. The mapped path only needs to work long enough to copy the files once.

Scenario: the removable media dropped out.

1. Reconnect the USB device or reinsert the disc, then wait for Windows to mount it.
2. Copy the full contents to a folder on the internal hard drive.
3. Run setup from that folder with administrator rights.
4. If the media will not read cleanly, download the complete installer again and use the download instead.

Scenario: a repair points at a source path that is gone.

1. Uninstall the damaged copy through Control Panel, Programs and Features (or Settings, Apps).
2. Download the full installer for your edition and release.
3. Install fresh from a local folder as administrator. Repair reuses the remembered source path; a clean install does not depend on it.

Scenario: the account lacks write rights.

1. Sign in to Windows with an administrator account.
2. Right-click the setup file and choose Run as administrator.
3. If the message persists, pause third-party antivirus or file sync tools, which can lock files mid-write, and run setup again.

When the installation finishes, run one verification pass. Open the Install Diagnostic Tool in Intuit's free Tool Hub, restart Windows, then open QuickBooks and confirm the version number.

How do you stop it coming back?

Copy every installer to a folder on the internal hard drive before running it, and never launch setup directly from a network share or a stick. Keep that local copy afterward. Windows Installer remembers where setup files came from, so a permanent folder lets future repairs and updates find their source.

Install and repair only under a Windows administrator account. If you must install from a share, host the folder on a machine that stays on, and map the drive to reconnect at sign-in so the letter stays stable. Give a USB device a fixed drive letter in Disk Management if you reuse it for setup files.

With the installer on local disk and an administrator account at the controls, error 1304 has nothing left to trip over. The same pattern holds for new installs and for repairs of existing ones.