QuickBooks Error 15105 - Damaged Digital Signature Certificate
QuickBooks Desktop stops installing an update with error 15105 when its digital signature certificate fails; our engineers show you how to repair it.
Error 15105 stops a QuickBooks Desktop update before it can finish. Windows cannot verify the digital certificate that signs the update file, so the installer refuses to continue. Your company file is not affected and no data is lost, but the program stays on its old release until the certificate problem is cleared.
What does the error message say?
The dialog normally reads: "Error 15105: There was an error when installing an update." Some releases add a line asking you to try again or restart the computer. The wording varies slightly between versions, so treat the number, not the sentence, as the reliable identifier.
The meaning behind the code
Every QuickBooks Desktop update is signed with a digital certificate. The signature proves two things: the file really came from the publisher, and it was not altered on the way to your computer. Before an update installs, Windows checks that certificate against the certificate store on your machine.
Error 15105 means the check failed. The certificate file on your computer is damaged, has been blocked or quarantined by security software, or is older than the signature on the update you are trying to install. QuickBooks treats an unverifiable update as unsafe and stops rather than risk installing something tampered with.
What triggers error 15105?
Our engineers see the same small set of causes across most cases:
- An earlier update was interrupted, leaving a partial or damaged download.
- Antivirus or anti-malware software quarantined the updater or its certificate.
- The Windows clock is wrong, so a perfectly valid certificate looks expired.
- A recent Windows repair, reset, or move to a new PC left the publisher's certificate out of the store.
- The update ran under a Windows account without administrator rights.
How do you fix error 15105?
Work through the scenarios below in order. Most cases clear at the first one.
The certificate is missing or damaged
- Sign in to Windows as an administrator.
- Open File Explorer and go to the QuickBooks program folder, usually C:\Program Files\Intuit\QuickBooks (year).
- Find qbupdate.exe, right-click it, and choose Properties.
- Open the Digital Signatures tab and select the publisher's signature in the list.
- Choose Details, then View Certificate, then Install Certificate.
- Place the certificate in the Trusted Publishers store, finish the wizard, and close the windows.
- Reopen QuickBooks, go to the Help menu, choose Update QuickBooks, then Update Now.
The clock made the certificate look out of date
- Open Windows Settings and go to Time & Language.
- Turn on Set time automatically, then sync the clock.
- Check that the year, date, and time zone are correct.
- Retry the update. A certificate can appear expired when the computer believes the wrong year.
Security software blocked or quarantined the file
- Open your antivirus or anti-malware console and check the quarantine list.
- If qbupdate.exe or a related certificate file is listed, restore it.
- Add an exclusion for the QuickBooks program folder so the file is not swept into quarantine again.
- Temporarily pause real-time protection, run the update, and turn protection back on when it finishes.
The download itself is damaged
- Close QuickBooks completely and restart the computer.
- Sign in as an administrator and reopen QuickBooks.
- Go to Help, Update QuickBooks, and choose Update Now. A clean retry replaces the damaged file with a fresh copy.
Keeping the error from coming back
- Let every update run to the end. Interrupting an install is the fastest way to damage a download.
- Keep the Windows clock set to update automatically.
- Add the QuickBooks program folder to your security software's exclusion list.
- Run QuickBooks as an administrator when you install updates, not only when you notice a failure.
- Keep Windows current. Routine Windows updates refresh the certificate store that these checks depend on.
If 15105 returns after all four scenarios, the Windows certificate store itself is usually damaged. That needs a deeper repair than an update retry, and it is the point where our engineers normally take over.