Facing the error message stating Update Error 15104 and unsure about what to do next? The QuickBooks Error series 15xxx has exasperated users when they have tried QuickBooks updates. One error among several of the installation errors in 15xxx series is the “QuickBooks Error Code 15104”.
This error is associated with a damaged installer and appears when the user goes to update QuickBooks Desktop. To curb this issue, we have come up with this article which contains the causes and solutions to fix QuickBooks update error 15104.
What provokes QuickBooks Error 15104?
The main factors behind this issue are:
- Using QuickBooks in the single-user mode.
- Windows registry files corrupted.
- QB installation done previously was not done to completion due to a sudden shutdown.
- Registry entries related to QuickBooks being damaged.
Various walkways to annihilate QuickBooks error 15104
This update error 15104 in QuickBooks can be dealt by sticking to the following solutions:
Solution 1: Go for a System Restore
This will discard Error 15104 is it is arising due to some recent system change. The steps are:
- Go to Start, the System Restore. Choose a recent Restore Point.
- Choose it, then go for Next and Finish tabs respectively.
- When over, reboot the PC and run QuickBooks to try out the update once again.
Solution 2: Clean Install QB in Selective Startup mode
- Go to System configuration. For this, go for Win +R, then type “msconfig”, then the Ok button.
- Go for “General” tab, then choose “Selective Startup” and “Load System Services” checkboxes.
- Then, move to Service, here, click on unhide Hide all Microsoft Services, then choose Disable all.
- Go for the Ok tab.
- Now, click on Boot tab, then choose safe mode, then Network.
- Now, restart the PC, then go to Control Panel, and then Programs and Features.
- Mark QuickBooks, then go for Uninstall/Change.
- Uninstall the program, then rename the QB folder.
- After that, go for a fresh installation.
- Activate and Register the product and run QB as admin. Now check if Error code 15104 got fixed.
