Quicken Windows Help

Why do I get "File Conflict – File is already open" when backing up my Quicken data file?

This message appears when Quicken tries to back up a data file that is stored on a network drive or external storage (such as a USB flash drive). While it's okay to back up or restore files to and from external locations, running your live data file directly from a network or external drive can cause file conflicts—and may eventually corrupt the file.

Step 1: Check where your file is stored

To confirm where your file is running:

  1. Open Quicken.

  2. Select File > Show this file on my computer.

  3. Check whether the file path points to a network location or external drive.

If your file is stored anywhere other than your local hard disk, proceed to the next step.

Step 2: Move the file to your local drive

To avoid file access conflicts and protect your data:

  1. Select File > Copy or Backup File.

  2. In the Copy dialog, change only the destination location (choose a folder on your local hard drive).

  3. Click OK to create the local copy.

Once you're working from the local copy, try backing it up again.

Tip: Always run Quicken files from your local drive. Only use external drives or networks for backup and restore.

Step 3: If the issue continues, try backing up from a new file

If the problem persists:

  1. Select File > New Quicken File.

  2. Choose New Quicken File, then click OK.

  3. Name the file (for example, Test) and click Save.

  4. Quicken opens the new file automatically.

Then:

  1. Select File > Copy or Backup File.

  2. Choose Create a complete backup, then click Next.

  3. For the source, locate your original file.

  4. For the backup destination, choose a location on your local hard drive.

  5. Click OK to complete the backup.

Step 4: If you're still unable to back up

If none of the above steps resolve the issue, try validating the original data file:

  1. Select File > File Operations > Validate and Repair.

  2. Follow the prompts to complete the validation.

  3. Try backing up the file again from the local copy.