Issues with Windows SQL update that my hardware provider can't seem to figure out

Question

Issues with Windows SQL update that my hardware provider can't seem to figure out

IRVC Staff 0

Hello, I am a Mac user in my personal life (mostly) and when it comes to the set up of the computers for my veterinary clinic, it all mostly goes over my head.

The host server was recently "repaired," and what that means is a memory refresh setting wasn't properly configured so they reconfigured it in BIOS and then shipped it back, to which it was discovered the external drive from 2008 (yes, you heard that right) was corrupting the entire computer. So that's all been taken care of and now the server computer doesn't seem to have any other issues aside from unable to update what was once one and now two separate security updates for SQL Server 2022 RTM CU (KB5072936 and KB5073031).

From some digging, it appears that there's some sort of missing installer file as it throws this error: Install error - 0x84b20003" and I am just in over my head with how to fix it. The company that provided our hardware as well as the software we use is all but useless, since the last two times I've been on the phone with them their solution was to just "try and install it again." And surprise surprise, it never works and always throws a similar error.

I finally was able to run the troubleshooter for Windows Update through Command Prompt which reached an error and was unable to finish.

I downloaded the SQL 2022 and tried to attempt a repair through the software, but I don't believe I even did that right, as the repair function just said everything was fine. I do not believe I had the right file selected. Again, I am no Windows expert at all.
I also ran something else through command prompt that was supposed to locate and "fix" corrupted files, and it did locate some and allegedly repair them, but upon restart the computer did not boot back up. Instead, I had to manually turn it off with the front power button.The only reason I'm even concerned with this update is I need to update the software we use for the actual practice of booking appointments, charging clients, etc.

I guess my overall question is: do I need to be concerned that these updates keep failing and if so, does anyone have any idea how to go about solving it? Or do I just let them sit there and not worry about it.

Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-26T21:43:26.76+00:00

Do I understand it that you SQL Server instance is up and running, the only problem is these two security fixes?

Can you connect to your SQL Server instance and run this query "SELECT @@version"?

I don't know how your SQL Server machine looks like, but I think you should be able to do this by opening a command-line window and run SQLCMD fro which you then can run the query.
IRVC Staff 0 Reputation points

2026-02-26T23:00:53.2+00:00

So I think I've done this right? It is still a bit over my head, as I've said I am not used to Windows, let alone an SQL. I ran "sqlcmd -?" in command prompt and got
"Microsoft (R) SQL Server Command Line Tool

Version 16.0.4212.1 NT"
If that was the right thing to do. But yes, the computer itself is running fine, just the two updates won't install and keep throwing the "0x84b20003" error.

Please let me know if this is the information you need, I will be heading out of the office soon but I will be back tomorrow.
Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-27T10:43:31.8966667+00:00
That gives you the version of SQLCMD. Run this to get the version of SQL Server:

SQLCMD -Q"SELECT @@version"

Note: Under some circumstances this command will fail, but if so, let's take that later.
Lakshmi Narayana Garikapati 920 Reputation points Microsoft External Staff Moderator

2026-03-03T10:17:03.8466667+00:00

Hi IRVC Staff,

Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further

Thanks,

Lakshmi.
Lakshmi Narayana Garikapati 920 Reputation points Microsoft External Staff Moderator

2026-03-10T09:06:59.78+00:00

Hi IRVC Staff,

Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further

Thanks,

Lakshmi.

1 answer

Your answer

Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-26T21:43:26.76+00:00

Do I understand it that you SQL Server instance is up and running, the only problem is these two security fixes?

Can you connect to your SQL Server instance and run this query "SELECT @@version"?

I don't know how your SQL Server machine looks like, but I think you should be able to do this by opening a command-line window and run SQLCMD fro which you then can run the query.
IRVC Staff 0 Reputation points

2026-02-26T23:00:53.2+00:00

So I think I've done this right? It is still a bit over my head, as I've said I am not used to Windows, let alone an SQL. I ran "sqlcmd -?" in command prompt and got
"Microsoft (R) SQL Server Command Line Tool

Version 16.0.4212.1 NT"
If that was the right thing to do. But yes, the computer itself is running fine, just the two updates won't install and keep throwing the "0x84b20003" error.

Please let me know if this is the information you need, I will be heading out of the office soon but I will be back tomorrow.
Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-27T10:43:31.8966667+00:00

That gives you the version of SQLCMD. Run this to get the version of SQL Server:

SQLCMD -Q"SELECT @@version"

Note: Under some circumstances this command will fail, but if so, let's take that later.
Lakshmi Narayana Garikapati 920 Reputation points Microsoft External Staff Moderator

2026-03-03T10:17:03.8466667+00:00

Hi IRVC Staff,

Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further

Thanks,

Lakshmi.
Lakshmi Narayana Garikapati 920 Reputation points Microsoft External Staff Moderator

2026-03-10T09:06:59.78+00:00

Hi IRVC Staff,

Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further

Thanks,

Lakshmi.

Answer 1

The failed SQL Server 2022 security CUs and error 0x84B20003 should be addressed, because they likely indicate a broken SQL Server servicing/installer state. Leaving them unpatched can block future updates (including the practice‑management software update) and may leave the instance without current security fixes.

Based on the error and symptoms described, the most likely cause is missing or damaged Windows Installer (MSI/MSP) cache files for SQL Server 2022. SQL Server setup and CUs depend on those cached files; if they are missing, updates repeatedly fail with generic setup errors.

A practical remediation path, aligned with the documented guidance, is:

Confirm the failure is in SQL Server servicing
- In %ProgramFiles%\Microsoft SQL Server\nnn\Setup Bootstrap\Log, open Summary.txt for the most recent CU attempt and confirm that the failing feature is the Database Engine or other SQL feature, not Windows Update itself.
Check for missing Windows Installer cache files
The documented behavior is that SQL Server CUs and SPs fail when MSI/MSP files in C:\Windows\Installer are missing or corrupted. The guidance is to restore or repair those files rather than repeatedly re‑running the CU:
- Use one of the supported methods from the “Restore the missing Windows Installer cache files” guidance:
  - Repair the SQL Server installation.
  - Use the FixMissingMSI tool.
  - Use the FindSQLInstalls.vbs script.
  - Manually restore the missing MSI/MSP files or restore them from a system‑state backup.
- These steps are specifically recommended when updates fail because the installer cache is incomplete.
Run a proper repair of the existing SQL Server instance
- Run SQL Server 2022 setup from the full media (not the CU) and choose Repair for the existing instance.
- This is one of the documented first‑line methods to restore missing installer cache files and fix servicing issues before re‑applying CUs.
Re‑apply the latest SQL Server 2022 CU/security update
- After the repair or cache‑file restoration, run the latest SQL Server 2022 CU/security update again.
- If it fails, follow the general troubleshooting methodology:
  1. On the setup failure screen, select Details.
  2. In the Setup Bootstrap\Log folder, open Summary.txt and identify which feature failed.
  3. Open the corresponding feature log (for example, sql_engine_core_inst_Cpu64_1.log) and the SQLServer_ERRORLOG_date_time.txt around the failure time.
  4. Search Details.txt for the keyword Failed to pinpoint the exact cause.
If errors 912/3417 or “Wait on Database Engine recovery handle failed” appear
- These indicate that the T‑SQL upgrade scripts did not complete and that master may not have recovered.
- In that case, use the dedicated guidance in “Troubleshoot upgrade script failures when applying an update” (linked from the CU troubleshooting article) to resolve script‑level upgrade failures before retrying the CU.
If Windows Update itself is also failing
- Because the Windows Update troubleshooter did not complete, treat Windows Update as a separate layer:
  - Run sfc /scannow and DISM again only under guidance from an administrator, as system‑file repair can affect boot behavior.
  - Use the Windows Update troubleshooter from Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run and follow the documented steps for common error codes (for example, clearing C:\Windows\SoftwareDistribution after stopping the Windows Update service).
When to worry vs. ignore
- If the practice‑management software requires a specific SQL Server CU or security level, the failed CUs must be fixed; otherwise the application upgrade may fail or remain unsupported.
- Even if the application appears to run, repeatedly failing SQL CUs and missing installer cache files are a servicing problem that should be corrected rather than ignored, especially on a production clinic server.

Given the complexity (BIOS changes, prior corruption, boot issues after system‑file repair), this is an appropriate point to involve a Windows/SQL Server specialist who can:

Use the official “Restore missing Windows Installer cache files” methods.
Review SQL setup logs and SQL error logs.
Ensure the instance is fully patched to the latest supported CU.

References:

Share via

Issues with Windows SQL update that my hardware provider can't seem to figure out

1 answer

Your answer