QuickBooks Error 1305: Setup Cannot Read a Required File

QuickBooks Desktop error 1305 stops installation when setup cannot read a required file; this guide covers the causes and the steps to finish the install.

Error 1305 stops a QuickBooks Desktop installation partway through. Setup tries to copy a required file, the read fails, and the install stops behind a Windows Installer message. Our engineers treat it as a source problem: somewhere between the media, the download, and the local cache, a file the installer needs has become unreadable.

The exact message

The installer halts and a dialog appears close to this:

Error 1305. Error reading from file: [name and location of the file]. Verify that the file exists and that you can access it.

Wording can shift slightly between releases. The named file also varies: it might be the main setup executable, an internal component, or a data file inside the package. Setup names whichever file it was copying when the read failed, and that file is not always the one at fault.

What does error 1305 mean?

Error 1305 is a Windows Installer code, not one specific to QuickBooks. Desktop setup wraps a standard MSI installation, and 1305 is the code MSI returns when a read from the install source fails. That source can be a downloaded setup file, a disc in an optical drive, or the local folder where setup stages its components. A failed read at any of those points produces the same number.

Why does setup fail to read the file?

Most cases come down to one of five triggers:

  • A damaged or incomplete download. An interrupted transfer leaves a truncated file, and setup reads the same bad bytes on every retry.
  • A corrupted cached component. Setup reuses files staged by an earlier attempt, so one damaged file poisons each new run.
  • A scratched or dirty disc, or a failing optical drive, on versions that shipped on physical media.
  • Bad sectors or low free space on the destination drive. Setup unpacks files into a temporary folder before copying them, and it needs working space.
  • Security software that locks or scans a file while the installer is copying it.

How do you fix error 1305?

Work through the scenarios in order. In our experience the first one clears most cases on its own.

Start with a fresh, verified download

  1. Cancel setup and restart the computer, so no half-open file handles survive into the next attempt.
  2. Delete the old setup file. Rerunning the same truncated download cannot help, because the missing bytes are still missing.
  3. Clear the cached component folder under ProgramData before any retry, since setup otherwise reuses the damaged file.
  4. Download the complete installer again on a stable connection and let it finish.
  5. Right-click the saved file and run it as an administrator.

Installing from a disc

  1. Clean the disc with a soft cloth, wiping from the center outward.
  2. Copy the entire contents of the disc into a new folder on the desktop, then run setup from there. A local copy sidesteps read errors from the drive mid-install.
  3. If the copy itself fails partway, the disc or the drive is at fault. Test the disc in a different drive before replacing either.

Disk and temp trouble

  1. Close other programs and clear temporary files: hold the Windows key and press R, type %temp%, and delete what the folder allows.
  2. Check the destination drive for errors with a disk check, and free up space. Setup needs room to unpack its payload.
  3. Retry the installation once the check has finished.

Security software locking files

  1. Pause real-time scanning in your antivirus for the duration of the install, or exclude the folder that holds the setup file.
  2. Restore full protection as soon as the installation completes.

If the next attempt fails with a different number, the unreadable source is fixed and a separate problem remains. Note the new code, because it points at a different layer, such as system components or permissions.

How can you prevent error 1305 from returning?

  • Keep a known-good copy of the full installer for your version in a safe folder. With connected services for older desktop versions winding down, a saved installer is worth archiving.
  • Confirm a download finished before running it. Compare the final file size against the size reported when the download started.
  • Install from a local folder rather than from a disc, a mapped drive, or a network share.
  • Give setup a clean run each time: close other programs, keep free space on the system drive, and pause real-time scans only while installing.

Most 1305 failures come down to the source file. A verified local copy of the installer removes that single point of failure from the whole process.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.