QuickBooks Error 15226: Payroll Update Fails the Subscription Check
Error 15226 appears when a payroll or tax table update stops part way, and our engineers can normally get those updates installing cleanly again.
Error 15226 sits in the 15xxx family of QuickBooks Desktop update errors. It appears when a payroll or tax table update stops part way through, usually while QuickBooks is checking your subscription or the connection to the update service. The company file is not damaged, and no data has been lost. In our experience the cause sits on the connection or Windows side, not in the books themselves.
The message you will see
The update window reports error 15226 and then closes without installing anything. The wording around the number varies a little between releases. Most versions mention that QuickBooks could not complete the update, or could not verify a signature, or could not confirm the payroll subscription.
Tax table updates fail with the same code as payroll updates. Both travel through the same update component, so a fix that works for one works for the other.
What does the code mean?
The 15xxx series covers every failure that happens while QuickBooks Desktop downloads or installs an update. Within that family, 15226 points to the verification step. Before it installs anything, QuickBooks checks that the downloaded files carry a valid digital signature and that your payroll subscription is current. When that check cannot complete, the installer stops and raises 15226. The update never touches the company file, so there is nothing to repair in your data afterwards.
Why does the verification fail?
We see the same handful of triggers across cases, in roughly this order:
- Security software or a firewall starts blocking the connection to the verification service, often after the security product updates its own rules.
- The QuickBooks release is several versions behind, and the old update component can no longer validate the newest files.
- QuickBooks Desktop reads its connection settings from Internet Explorer, so a quiet change there affects updates even when you browse with something else.
- A damaged Microsoft component, chiefly .NET Framework, breaks the signature check.
- QuickBooks is running without administrator rights, so the installer cannot write the files it has verified.
How do you fix error 15226?
Work through the scenarios below in that same order. Each set of steps targets one trigger.
Connection or security software is blocking the check
- Close QuickBooks and restart the computer. A stale session can leave the update service in a bad state.
- Right-click the QuickBooks Desktop icon and choose Run as administrator.
- Open the Help menu, choose Update QuickBooks Desktop, and click Update Now.
- If the code returns, check your firewall or antivirus settings and allow QuickBooks to reach the update servers. Products that refreshed their rules recently are the usual offenders.
- Run the update once more.
The release is too far behind
- Press F2 with a company file open and note the release shown on the Product Information screen.
- Install the latest maintenance release for your version first, with the company file closed.
- Restart the computer, then run the payroll or tax table update again from the Help menu.
A Microsoft component is damaged
- Close QuickBooks.
- In the Windows search box, type "Turn Windows features on or off" and open that panel.
- Clear the tick beside .NET Framework 4.8 Advanced Services, restart, then return to the same panel and tick it again.
- Restart once more and run the update.
QuickBooks files are not registered properly
- Close QuickBooks.
- In File Explorer, open the QuickBooks installation folder inside Program Files; its name includes the year of your version.
- Find reboot.bat, right-click it, and choose Run as administrator.
- Command windows will open and close while the script re-registers QuickBooks components. Let it run to the end without interrupting.
- Restart the computer and run the update again.
If 15226 still appears after all four scenarios, a repair install of QuickBooks Desktop from the Windows Programs and Features list is the next step. The repair replaces the update components and leaves the company file alone.
How do you stop it coming back?
Keep releases current. Open the Help menu, choose Update QuickBooks Desktop, select the Options tab, and switch automatic updates on. A machine that is never more than one release behind rarely meets this error.
When your antivirus or firewall changes, run one update straight afterwards as a test. New security rules are the most common way this error creeps back.
If a computer has been offline for months, update in stages: maintenance release first, payroll table second. That keeps the update component and the verification service in step.