Windows Update Error 0x80070653 — Installation Failed Fix

What Does This Error Mean?

Windows Update error 0x80070653 means the Windows Installer (MSI) component reported a fatal error during update installation. This specific code translates to 'Fatal error during installation' in MSI error language. It usually means the installer encountered a conflict with an existing installed program, a corrupted system file, or a locked file it needed to replace. This is one of the more frustrating update errors because it points to a conflict rather than a simple network problem.

Affected Models

Windows 10
Windows 11
Windows 8.1

Common Causes

An existing installed program is conflicting with the update — particularly older Microsoft products like Office, Visual C++ Redistributables, or .NET Framework
A required file is locked by a running application and cannot be replaced during installation
The Windows Installer service itself is corrupted or in a broken state
Registry entries for a previously installed program are damaged, confusing the installer
Insufficient disk space on the system drive to complete the installation process

How to Fix It

Run the Windows Update Troubleshooter first. Go to Settings > System > Troubleshoot > Other troubleshooters and click Run next to Windows Update. The troubleshooter can detect and fix Windows Installer registration issues.

This is worth doing before the more involved steps below — it fixes a significant portion of 0x80070653 errors automatically.
Repair or update Visual C++ Redistributables and .NET Framework. Go to Control Panel > Programs and Features. Look for multiple entries of Microsoft Visual C++ Redistributable. Right-click each and select Repair. Also check for .NET Framework entries and repair or update those.

Many Windows updates install or update these shared libraries. If the existing version is already corrupted, the installation fails with a fatal MSI error.
Run DISM and SFC. In Administrator Command Prompt: DISM /Online /Cleanup-Image /RestoreHealth — wait to complete, then: sfc /scannow — restart and try the update again.

Corrupted Windows Installer system files are a common cause of fatal MSI errors during updates.
Perform a clean boot to eliminate software conflicts. Search 'msconfig' in Start and open it. Go to the Services tab, check 'Hide all Microsoft services', then click Disable all. Go to the Startup tab and click Open Task Manager, then disable all startup items. Restart and try the update.

If the update installs successfully after a clean boot, re-enable services and startup items in groups to find which one was conflicting.
Check available disk space on C: drive. Open File Explorer and check. If you have less than 10 GB free, run Disk Cleanup (search 'Disk Cleanup' in Start) and check the option to clean up Windows Update files, previous Windows installations, and temporary files.

MSI installers need working space to extract and prepare files during installation. Very low disk space causes fatal failures.

When to Call a Professional

If the DISM repair and clean boot do not identify the conflicting software, a technician can review the Windows Installer log files to find the exact file or registry key causing the failure. Installer logs are detailed and can pinpoint the problem precisely.

Frequently Asked Questions

What is the Windows Installer (MSI)?

The Windows Installer is the component Windows uses to install, update, and remove software. MSI files (Microsoft Installer packages) contain all the instructions and files needed to install a program. Windows Update uses the Windows Installer to apply many types of updates — especially updates to Microsoft products like .NET, Visual C++, and Office. When the installer fails with a fatal error (code 1603 internally, shown as 0x80070653 in Windows Update), it means something interrupted or blocked the installation process.

What is a clean boot and is it safe?

A clean boot starts Windows with only the minimum required Microsoft services and drivers. All third-party software — antivirus, hardware utilities, printer software, etc. — is temporarily disabled. This lets you test whether a conflict with third-party software is causing the update failure. A clean boot is completely safe and temporary. After you are done testing, re-enable everything in msconfig and your startup will return to normal.

Will this error damage my PC if I leave it unfixed?

It will not damage your PC immediately, but leaving it unfixed means missing security and feature updates. Over time, a system that cannot install updates accumulates unpatched security vulnerabilities. The fix steps above are safe to follow at any time. The most common resolution is repairing Visual C++ Redistributables and running DISM, which takes about 15-30 minutes.