Quick answer
QuickBooks error 1310 means the Windows Installer could not write to a file during an install, update, or repair — usually because of folder permissions, a read-only file, antivirus, a temp-folder problem, or a stalled Windows Installer service. Write down the exact path in the message, close every QuickBooks process, and work through the permission, temp-folder, and UAC fixes below before you reinstall.
What QuickBooks error 1310 means
Error 1310 is a Windows Installer error, not a QuickBooks data error. The installer got partway through copying or replacing a file and Windows refused the write. QuickBooks displays that Windows message with the full path attached, and the path is the most useful part of the error. You will see one of these:
- Error writing to file C:\Program Files\Intuit\QuickBooks 20xx\BusinessObjectProvider.dll
- Error "1310: Error writing to file: C:\Config.Msi..."
Each path points at a different fix. A file inside the QuickBooks program folder means the installer lacks permission or the file itself is read-only. A path inside C:\Config.Msi means Windows Installer could not write to its own staging and rollback folder. A path inside %TEMP% means the temp folder is full, missing, or redirected somewhere the installer cannot use. The error only touches program files, so your transactions are safe — but take a backup before changing permissions or running a repair.
Symptoms that come with error 1310
- The installer stops partway through and the dialog names a file or folder with "Error writing to file".
- The failure repeats at the same file on every attempt, even after a clean restart.
- A repair started from Programs and Features fails at the same point as the original installation.
Common causes, ranked by how often they appear
- Missing permissions on the target folder. The account running setup cannot modify the QuickBooks program folder or
C:\Config.Msi, so the installer is denied write access. - A read-only file left behind. Restore tools and copied backups can set the read-only attribute on a
.dllor.exe, and the installer cannot replace it. - Antivirus or Controlled folder access. Real-time scanning and Windows Security's ransomware protection often block installers from writing to protected locations.
- Temp folder problems. A full, deleted, or redirected
TEMPfolder leaves Windows Installer with nowhere to stage its working copies. - A stalled or unregistered Windows Installer service. The service is stopped or its registration is damaged after a failed update.
- Disk errors or a standard user account. Windows cannot write what it cannot store, and an unelevated install is denied access to
Program Filesby design.
Before you begin
- Back up the company file. If QuickBooks opens, use File → Back Up Company → Create Local Backup; if it does not, copy the folder that contains the
.QBWfile to an external drive. - Sign in with a Windows administrator account and have your license and product number ready.
- Note the exact file path from the error message and which release you are installing. Every step below uses that path.
- Allow 20 to 40 minutes. The Install Diagnostic Tool alone can run for up to 20 minutes.
How to fix QuickBooks error 1310
Back up and write down the exact path from the error
Create a fresh backup of the company file, or copy the whole company-file folder if QuickBooks will not open. Then write down the full path shown in the 1310 dialog — for example C:\Program Files\Intuit\QuickBooks 20xx\BusinessObjectProvider.dll or C:\Config.Msi. That path tells you where to apply the fixes below.
Close every QuickBooks process and run the installer as administrator
Press Ctrl + Shift + Esc to open Task Manager, switch to the Details tab, and end any instance of QBW32.exe, QBDBMgr.exe, QBDBMgrN.exe, QBCFMonitorService.exe, QBUpdate.exe, and msiexec.exe.
Right-click the downloaded installer (usually QuickBooks.exe) and select Run as administrator. If the file sits in a OneDrive, Dropbox, or mapped-network folder, move it to a local folder such as C:\Temp first — sync clients and network paths regularly interfere with setup.
Clear the read-only attribute on the file named in the error
Open File Explorer, browse to the path from the error, right-click the file, select Properties, and clear the Read-only checkbox. To do the same from a command line, open Command Prompt as administrator and run attrib -r "C:\Program Files\Intuit\QuickBooks 20xx\BusinessObjectProvider.dll", using your own path. A read-only flag set by a backup or file-copy tool can survive reboots and silently block every install attempt.
Clear the temp folder and verify TEMP and TMP
Press Windows + R, type %temp%, and press Enter. Select all the files and delete them, skipping anything Windows says is in use. Then confirm the variables point to a real folder: type echo %TEMP% and echo %TMP% in Command Prompt. Both should return a local path such as C:\Users\yourname\AppData\Local\Temp. If a path does not exist, recreate the folder or correct the variable under System Properties → Advanced → Environment Variables.
Run the QuickBooks Install Diagnostic Tool
Download the current QuickBooks Tool Hub from Intuit, install it, and open it. Select Installation Issues, then QuickBooks Install Diagnostic Tool, and let it run — it repairs the Microsoft .NET, MSXML, and C++ components that QuickBooks setup depends on, and can take up to 20 minutes. Restart Windows when it finishes, then try the install again. This is the best first fix because it repairs the installer environment without touching your company data.
Re-register and restart the Windows Installer service
Open Command Prompt as administrator. Type msiexec /unreg, press Enter, then type msiexec /regserver and press Enter to rebuild the installer registration QuickBooks setup relies on.
Press Windows + R, type services.msc, and press Enter. Find Windows Installer, confirm its Startup type is Manual, and select Start if stopped or Restart if running. Retry the QuickBooks install afterward. If later errors continue, the same Tool Hub is where you return for error 1603.
Change permissions only at the path from the error. Do not take ownership of C:\, C:\Windows, or a whole drive. Grant rights only to the exact file or folder named in the 1310 message, and use the Administrators group rather than your personal account. On a company-managed PC, ask IT before changing ownership.
Take ownership and grant permissions at the exact path
If step 3 did not resolve the write failure, take ownership of the folder named in the error. Open Command Prompt as administrator and run these commands, replacing the example path with the folder from your own message — Intuit uses C:\Config.Msi in its documentation, and the same pattern works for the QuickBooks program folder:
takeown /f "C:\Config.Msi" /r /d y
icacls "C:\Config.Msi" /T /C /grant administrators:F
The first command makes Administrators the owner; the second grants full control and continues past files it cannot read. As a GUI alternative, right-click the folder, open Properties → Security → Advanced, change the owner to Administrators, and grant Full control. Apply the same rights to the QuickBooks program folder if the error names a file inside it, then retry.
Lowering UAC reduces Windows protection. Move the slider only long enough to run the installer, and put it back to its original position immediately afterward. Never leave User Account Control at the lowest level on a computer that connects to the internet.
Lower User Account Control temporarily and retry
Open Control Panel → User Accounts → Change User Account Control settings. Note the current slider position, move it down one or two notches, and select OK. Restart if Windows asks, run the installer as administrator, then return the slider to its original height.
Rule out antivirus and disk problems, then retry
Open Windows Security → Virus & threat protection → Manage settings and switch Real-time protection off only for the length of the install, then turn it back on. If Ransomware protection is active, open Manage ransomware protection and switch Controlled folder access off briefly — it blocks installers from writing to protected folders. Add the QuickBooks program folder as an exclusion afterward. On a managed PC, ask IT instead of disabling corporate antivirus.
Finally, check the drive: open File Explorer → This PC, right-click the drive that holds the QuickBooks folder, and run Properties → Tools → Error checking. From an administrator Command Prompt you can instead run chkdsk C: /f; if Windows cannot lock the drive, accept the option to run it at the next restart.
Verify the installer completed correctly
- Open QuickBooks as a standard user, not as administrator, and open your company file. If it loads without an error, the write problem is solved.
- Press F2 or Ctrl + 1 to open Product Information and confirm the version and release number are the ones you expected.
- Run File → Utilities → Verify Data and confirm QuickBooks reports no problems with your data.
- Open Event Viewer → Windows Logs → Application and check that the most recent QuickBooks-related
MsiInstallerentry is informational, not another 1310 error. - Create a fresh backup and store it off the machine.
If error 1310 comes back
Reinstalling is not the first answer, but it is the reliable one when the existing installation is damaged. Run Quick Fix my Program from the Tool Hub's Program Problems tab, then use Programs and Features → QuickBooks → Uninstall/Change → Repair. If the repair hits the same 1310, delete the old installer and download a fresh copy from Intuit's Downloads & Updates page.
If the PC is governed by Group Policy, the write may be blocked by policy rather than a damaged file. If chkdsk reports uncorrectable errors or write failures appear in other programs, stop installing until the drive is repaired or replaced. When the installer environment itself is suspect, the steps used for error 1328 and a clean reinstall are the next escalation.
Prevention
- Install and update from an administrator account, using an installer saved to a local disk — never a synced or mapped folder.
- Keep several gigabytes free on the system drive; installers stage large temp files before copying them into place.
- Finish Windows updates and restart before installing QuickBooks, so queued file operations are cleared first.
- Back up the company file before every update, and verify the release number with F2 afterward.
Frequently asked questions
Does error 1310 mean I have to reinstall QuickBooks?
No. Reinstalling is the last option. Most 1310 errors come from permissions, a read-only file, antivirus, or the temp folder — all fixable without removing QuickBooks.
Is it safe to give Administrators full control of C:\Config.Msi?
Yes, when the error names that folder. C:\Config.Msi is Windows Installer's own staging folder, and Administrators normally has access anyway. Grant rights to that path only, and never apply the same commands to C:\Windows or a whole drive.
Why does error 1310 name a .dll file?
The installer was replacing that file when Windows denied the write. The name does not mean the .dll is corrupt; it means the folder or the file's attributes are blocking the replacement. Fix access at that path and the install continues.
Will lowering UAC or disabling antivirus break my computer?
Not if the change is temporary. Lower UAC and turn off real-time protection only while the installer runs, then restore both settings immediately. Treat these as short troubleshooting switches, not fixes.
Can a full or failing disk cause error 1310?
Yes. If the drive has little free space or bad sectors, Windows cannot store the files the installer writes, and the failure may name a different file each time. Run Error checking and free up space before retrying.