0x80070643 is a generic fatal Windows Installer error, not a diagnosis. The correct fix depends on what failed: SQL Server Management Studio (SSMS), the SQL Server engine, an update, or a repair operation. Identify that package first, then use the matching recovery path below.
For a common SSMS failure, uninstall Microsoft ODBC Driver 17 for SQL Server, restart if Windows requests it, and run the latest SSMS installer again. Engine setup failures usually require fresh SQL Server media copied to a local drive. Messages about a missing MSI or MSP usually require restoring the Windows Installer cache from matching SQL Server media before retrying repair.
As an Amazon Associate I earn from qualifying purchases.
What 0x80070643 means during SQL Server installation
Windows Installer uses 0x80070643 for a fatal installation failure. In a SQL Server workflow, the code can appear while installing SSMS, the database engine, an ODBC component, a cumulative update, or a repair package. Because several different packages can produce the same hexadecimal value, the code alone cannot identify the root cause.
Treat the installer dialog as the starting clue, not the complete explanation. The product name shown in the dialog and the setup log determine which procedure is appropriate. Repeating the same installer without identifying the failed component often reproduces the same failure and can leave a partial installation behind.
#1 Best Overall
Identify the failing component before changing anything
Use the wording in the error dialog and the available logs to place the failure in one of these categories:
| Where the failure appears | Evidence to collect | First recovery path | Source required |
|---|---|---|---|
| SSMS installation | SSMS installer message, often mentioning fatal error during installation (0x80070643) | Remove Microsoft ODBC Driver 17 for SQL Server, then rerun the latest SSMS installer | Latest SSMS installer |
| SQL Server engine setup | SQL Server Setup failure and entries in Summary.txt or related setup logs |
Use fresh media extracted or copied locally; inspect the logs for the underlying error | Fresh SQL Server installation media |
| Update, repair, or uninstall | A message naming a missing MSI or MSP package, or a failure to find a cached installer file | Repair from original media; if necessary, restore missing cache files with FixMissingMSI | Matching RTM, service-pack, or cumulative-update media |
Do not delete files from %windir%Installer while troubleshooting. SQL Server and Windows Installer may need those cached MSI and MSP packages for later updates, repairs, and uninstalls.
Prepare safely for a retry
- Close related applications. Exit SSMS, Visual Studio, SQL Server Profiler, and any other SQL Server or installer windows. A file in use can prevent an uninstall or setup operation from completing.
- Record what failed. Note whether the dialog names SSMS, SQL Server, an ODBC driver, an update, or a repair. Preserve the exact text, including any package name or missing-file reference.
- Use an administrator account or elevation when requested. Repairing SQL Server components and restoring installer-cache files can require an administrative Command Prompt or PowerShell session.
- Do not clean the installer cache. Manual deletion or “cleanup” of
%windir%Installercan create a missing-MSI/MSP problem even if the original installation was healthy. - Keep the original or matching media available. A repair or cache restoration needs media that matches the installed SQL Server release, service pack, or cumulative update.
Fix the common SSMS 0x80070643 failure
Microsoft’s SSMS troubleshooting guidance identifies a common case in which Microsoft ODBC Driver 17 for SQL Server blocks the SSMS installation. Follow these steps when the failing product is SSMS or the setup message points to that ODBC package.
Free tools Windows power users keep installed
One-click scans. No signup required.
1. Close SQL-related programs
Save your work and close SSMS, Visual Studio, SQL Server Profiler, and other related applications. Check the taskbar and running windows before continuing.
2. Open Programs and Features
Open Control Panel > Programs and Features. This is the classic Windows interface that lists installed desktop packages and their uninstall actions.
3. Uninstall Microsoft ODBC Driver 17 for SQL Server
Find Microsoft ODBC Driver 17 for SQL Server in the installed-program list, select it, and choose the uninstall action. Follow the removal wizard. Do not remove an unrelated SQL Server component simply because its name contains “Microsoft” or “SQL.”
4. Restart if requested
If Windows asks for a restart, restart before trying SSMS again. Restarting allows the ODBC package removal and any pending Windows Installer changes to finish.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors5. Run the latest SSMS installer
Start the latest SSMS installation again after Windows returns to the desktop. If setup completes, launch SSMS and confirm that it opens normally. If the same code returns, preserve the new installer log and verify that the dialog still identifies SSMS rather than a different package.
Rank #3
Repair a SQL Server engine setup failure
When the SQL Server engine setup fails, do not assume that 0x80070643 itself is the cause. SQL Server Setup writes a more useful explanation in its summary and related log files.
Use fresh local installation media
- Obtain the SQL Server installation media for the release you intend to install.
- Download it again if the existing download may be incomplete or damaged.
- Extract or copy the media to a local folder on the computer. Avoid running Setup directly from a network location while diagnosing this failure.
- Start SQL Server Setup from that local copy and repeat the installation.
Damaged installation media and corrupted installation sources are documented causes of setup failures. A clean local copy removes those variables and gives Setup stable access to every package it expects.
Read Summary.txt before repeating attempts
After the failure, open the SQL Server Setup Summary.txt file and the related setup logs. Search for error and failed. The first occurrence of 0x80070643 is often only the final Windows Installer status; the surrounding entries may identify a prerequisite, package, or source problem that needs attention.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Check release and Windows compatibility
Verify that the SQL Server release and servicing level you are installing are supported on the Windows version in use. A package that is not supported for that Windows edition or version can fail even when the media is intact. Confirm the supported combination before making another installation attempt.
Rank #4
Fix update or repair failures that name a missing MSI or MSP
SQL Server stores Windows Installer cache files under %windir%Installer. Updates, repairs, and uninstalls may need the original MSI or an MSP patch from that cache. If a cache file was deleted or is unavailable, Windows Installer can report a missing package and surface 0x80070643.
Start with SQL Server repair from the original media
- Locate the original SQL Server installation media, or media matching the installed release and servicing level.
- Start SQL Server Setup from that media.
- Choose the repair workflow for the affected instance or feature.
- Allow the repair to restore required files, then restart Windows if Setup requests it.
- Retry the update, repair, or uninstall that originally failed.
Repairing from matching media is the least invasive documented recovery path when the cached package cannot be found.
Use FixMissingMSI when cache files are still missing
Microsoft documents FixMissingMSI for scanning for missing Windows Installer cache files and recaching them from locally extracted RTM, service-pack, or cumulative-update media. Use matching media for the installed SQL Server build; mixing an unrelated release can leave the cache incomplete or mismatched.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Extract the matching RTM, service-pack, or cumulative-update media to a local folder.
- Open an administrative Command Prompt or an elevated PowerShell session.
- Run FixMissingMSI according to Microsoft’s documented procedure, pointing it to the locally extracted media when requested.
- Review the tool’s results and confirm that the named MSI or MSP was restored or recached.
- Run SQL Server repair again from the original or matching installation media.
- Retry the update or other operation that produced the missing-package message.
Do not manually invent a replacement MSI or copy an arbitrary package into the cache. The package must correspond to the SQL Server component and servicing level that Windows Installer is requesting.
Best Value
Use system-state backup as the fallback
If the documented media-based repair and FixMissingMSI process cannot restore the required packages, a system-state backup is the fallback identified in Microsoft’s recovery guidance. A system-state recovery is a broader administrative operation; use it only when you have an appropriate backup and understand the recovery implications for the computer.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Remove a partial SQL Server installation
A failed setup can leave a partial installation. If a later attempt reports that an existing feature or instance is already present, use Microsoft’s partial-installation removal guidance rather than deleting SQL Server folders manually. After the partial installation is removed, restart Windows, use fresh local media, and run Setup again.
If an existing instance is damaged rather than partially installed, choose the SQL Server repair workflow instead. Removing an intact instance when repair would have been sufficient can create unnecessary downtime and additional configuration work.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUse the logs to choose the next step
- Dialog names SSMS and ODBC Driver 17: follow the Programs and Features removal procedure, restart if requested, and rerun the latest SSMS installer.
- Setup Summary.txt points to source or media errors: download the SQL Server media again, copy it locally, and rerun Setup from that copy.
- Summary.txt identifies an unsupported release or servicing level: verify the SQL Server and Windows combination before retrying.
- Logs name a missing MSI or MSP: repair from matching media, then use FixMissingMSI if the cache is still incomplete.
- A previous attempt left a partial installation: follow the partial-installation removal guidance before starting over.
Keep the logs from the failed attempt and the retry. If the second attempt fails, the new entries may show whether the first problem was resolved and expose the next blocker.
Verify that the repair really worked
- Confirm that the installer reaches its completion state without 0x80070643 or another fatal status.
- For SSMS, launch the application and verify that it opens normally.
- For SQL Server, confirm that the relevant installed component or instance starts normally after setup or repair.
- For an update, verify that the update operation reports completion rather than leaving a pending repair state.
- Keep the final setup logs until normal operation is confirmed, especially on a production or shared computer.
Prevent the same failure from returning
- Keep a usable copy of the SQL Server installation media for the installed release and servicing level.
- Do not delete or “optimize” files under
%windir%Installer; later SQL Server maintenance may depend on them. - When an installer fails, identify the package before rerunning it. SSMS, the engine, an ODBC driver, and an update can require different remedies.
- Use local installation media when setup is sensitive to a network path or a damaged source.
- Preserve
Summary.txtand related logs when escalating the issue, because the generic code does not identify the root cause by itself.
As an optional shortcut after trying the manual procedures, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, and includes an app-crash log. It complements antivirus software rather than replacing it; results vary, and no tool repairs every crash. It runs on Windows 11, 10, 8, and 7, with a free trial by category for at least two days before a subscription is required.
When to escalate
Escalate with the exact installer dialog, the failing product name, the SQL Server release and servicing level, the Windows version, and the latest Summary.txt and related logs when the documented path does not work. Those details distinguish an SSMS dependency conflict from damaged engine media, an unsupported release, or a missing Windows Installer cache package.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
