Home › Microsoft Configuration Manager › 0x80070643

Microsoft Configuration Manager · 0x80070643 · Windows 11 23H2

SCCM Error 0x80070643 MSI Install Failure Windows 11 23H2

MSI-based application deployment failed due to corrupt file or missing prerequisites; fix by verifying content hash and ensuring all dependencies are met.

Error Details

FactValueSourceNote
Exact error stringERROR_INSTALL_FAILURE (0x80070643)AppEnforce.log->
Affected OS build rangeWindows 11 23H2
Registry key for MSI loggingHKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer MsiLogging = v!Registry Editor->
Relevant servicemsiserver
Log line signature0x80070643|ExitCode = 1603AppEnforce.log->

Log Files to Check

What This Error Actually Means

The error code 0x80070643, also known as ERROR_INSTALL_FAILURE, is a critical failure message raised by the Windows Installer (msiexec.exe) component when an MSI-based application deployment fails during its execution phase. Specifically, this error indicates that the installation process could not complete successfully due to issues such as corrupt files, missing prerequisites, or conflicts with other running applications/services on the client machine. In the context of Microsoft Configuration Manager (SCCM/ConfigMgr), this error typically appears in the C:\Windows\CCM\Logs\AppEnforce.log file and is logged whenever an application deployment attempt fails.

Affected Versions and Scope

This specific issue affects Windows 11 operating systems with build number 23H2. It's important to note that while the error can occur on other versions of Windows, this guide focuses specifically on addressing it within the context of Windows 11 23H2. The problem is particularly relevant for organizations using Microsoft Configuration Manager (SCCM/ConfigMgr) for application deployment and management.

Where To Look First: Logs and Event IDs

To diagnose an error with code 0x80070643, start by examining the C:\Windows\CCM\Logs\AppEnforce.log file on the affected client machine. This log contains detailed information about application enforcement actions performed by Configuration Manager. Look for lines containing '0x80070643' or 'ExitCode = 1603', which are direct indicators of an installation failure. Additionally, check the C:\Windows\CCM\Logs\CAS.log file to review content availability checks and ensure that all required files have been successfully downloaded from distribution points. Another important log is the Windows Installer log located in the temporary directory (%TEMP%\MSI*.LOG). This can be enabled by setting the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer\MsiLogging = v!. Reviewing these logs will provide crucial insights into what went wrong during the installation process. Event IDs 11708 and 1033 from source MsiInstaller in the Application log of Event Viewer are also relevant for this issue. These events indicate that an MSI install failed, providing additional context about the nature of the failure.

Root Causes

Corrupt or Missing Content Files

One common cause is a corrupt or missing content file on the distribution point. This can be identified by examining the C:\Windows\CCM\Logs\CAS.log and verifying that all necessary files are present and correctly hashed in Configuration Manager's console under Monitoring > Distribution Status > Content Status.

Missing Prerequisites

The installation might fail due to missing prerequisites such as Visual C++ Redistributable or .NET Framework versions required by the MSI package. Check the verbose Windows Installer log for 'Requires:' entries indicating what is needed but not installed on the client machine.

Conflicting Applications/Services

A conflicting application running during installation or a stopped service like msiserver can also cause this error. Use PowerShell to check the status of the Windows Installer service with Get-Service msiserver | Select-Object Status.

Fix Procedure

  1. Enable Verbose MSI Logging: Set the registry key for verbose logging: Set-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer -Name MsiLogging -Value 'v!' -Type String. Retry the deployment and review the generated log in %TEMP%\MSI*.LOG.
  2. Check Content Hash: In Configuration Manager, go to Software Library > Application Management > Applications > > Deployment Types > Properties > Content. Compare the hash value here with that of the file on the client machine using PowerShell: Get-FileHash 'C:\Windows\ccmcache\\setup.msi'.
  3. Verify Windows Installer Service: Check if the service is running: Get-Service msiserver | Select-Object Status. If it's stopped, start it with Start-Service msiserver.
  4. Clear CCM Cache and Retry Deployment:
    Use Software Center on the client to delete files or use PowerShell: Get-WmiObject -Namespace root\ccm\SoftMgmtAgent -Class CacheConfig | ForEach-Object { $_.Location }. Then, trigger a machine policy evaluation with Invoke-WmiMethod -Namespace root\ccm -Class SMS_Client -Name TriggerSchedule -ArgumentList '{00000000-0000-0000-0000-000000000021}'. Verify in AppEnforce.log that the deployment retries.
  5. Run MSI Installation Manually:
    On a test machine, execute msiexec.exe /i C:\test\setup.msi /L*V C:\install_verbose.log /qn. Review install_verbose.log for specific errors and address them.
  6. Redistribute Content: In the ConfigMgr console, right-click the deployment type package > Redistribute to Distribution Point. Verify status in Monitoring > Distribution Status > Content Status.

Error Code Variants

Error CodeDescription
0x80070643 (ERROR_INSTALL_FAILURE)Indicates a failure during the installation process.
0x80070652 (ERROR_INSTALL_SUSPEND)Installation was suspended due to user action or system requirements not met.
0x80070641 (ERROR_INSTALL_TEMP_UNWRITABLE)The temporary folder is unwritable, preventing the installation from proceeding.

Verification

To verify that the fix has been successful, review C:\Windows\CCM\Logs\AppEnforce.log for lines indicating a successful deployment without any error codes. Additionally, check Event Viewer > Applications and Services Logs for event ID 11708 (MSI install failed) to ensure it no longer appears.

Prevention

To prevent recurrence of this issue, implement policies that enforce the installation of necessary prerequisites before attempting MSI deployments. Use Configuration Manager's application deployment rules to specify dependencies and ensure they are met on client machines. Additionally, regularly audit distribution points for content integrity using PowerShell scripts or scheduled tasks. By following these steps and maintaining a proactive approach to managing your environment, you can minimize the occurrence of 0x80070643 errors in Microsoft Configuration Manager deployments.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.