The goal of this post is to provide a comprehensive list of SCCM client install error codes along with their descriptions and solutions to assist you in resolving client installation issues on Windows devices.
As a Configuration Manager administrator, I often encounter client installation failures, and identifying the error code is essential for diagnosing the root cause. I have seen most users in the SCCM community forum report about ccmsetup errors, so this guide is designed to provide quick solutions for anyone facing client installation issues.
Many ccmsetup error codes can be confusing as they neither provide clear resolutions nor explain the root cause of the issue. However, through personal troubleshooting experience and insights from other SCCM MVPs, most solutions have been identified and resolved.
From what I know, the SCCM client error codes are classified into types: HRESULT error codes and non-HRESULT error codes. The HRESULT codes are hexadecimal error codes that provide more detailed information about what went wrong during the installation process. Whereas non-HRESULT codes are simplified error codes that typically appear in CCMSetup with numerical values.
Converting CCMsetup error codes to descriptions
SCCM Log files are crucial in finding out the actual error codes for client installation failures, especially the ccmsetup.log. In addition to that, I would also recommend reading the guide on how to translate SCCM error codes to descriptions.
SCCM Client Install Error Codes and Solutions
The table below references a Microsoft article that outlines all error codes along with their corresponding meanings and solutions. It includes HRESULT, non-HRESULT, and common ccmsetup error codes.
| Error Code | Description | Solutions |
|---|---|---|
| 2 | The system cannot find the file specified | This issue arises from missing files or the failure to locate essential files required for client installation. |
| 5 | Access denied | This occurs because the ccmsetup process does not have the required administrative permissions to complete its actions. |
| 7 | Reboot Required | The ccmsetup needs a reboot to complete the installation. |
| 8 | Setup Already Running | This error is seen when another instance of ccmsetup is already running on a device. |
| 9 | Prerequisite evaluation failure | Ensure all prerequisites for SCCM client installation are properly configured. |
| 10 | Setup manifest hash validation failure | The ccmsetup files appear to be corrupted. Please retrieve fresh client installation files from the site server. |
| 52 | You were not connected because a duplicate name exists on the network. | The issue is likely related to DNS, as the client has duplicate entries in the DNS records. |
| 53 | Unable to locate or cannot connect to admin$ or Computer Browser not started. | To fix this issue, enable File and Print Sharing in the Firewall’s Exceptions list and ensure File and Print Sharing is activated within the firewall settings. |
| 58 | The specified server cannot perform the requested operation. | The required network share is inaccessible during client deployment, often due to a lack of administrative privileges or network connectivity issues. |
| 64 | The specified network name is no longer available. | This suggests an issue with network connectivity or access to a shared resource, potentially occurring during the installation of the Configuration Manager client. |
| 67 | Network name cannot be found | This issue usually arises from DNS or name resolution problems, disabled network services such as Remote Registry, or the absence of File and Printer Sharing for Microsoft Networks on the client machine. |
| 86 | Network configuration problem | Either the network password is incorrect, or SCCM is unable to resolve the client name. |
| 112 | Not enough disk space | The SCCM client requires about 100 MB to 500 MB of disk space for the core installation and associated components. |
| 1003 | Cannot complete this function | This error occurs due to a misconfigured management point, a corrupted WMI repository, or improper boundary group settings. |
| 1053 | The service did not respond to the start or control request in a timely fashion | A Windows service did not start within the expected timeframe, potentially caused by service dependencies, inadequate permissions, or incorrect registry configurations. |
| 1068 | The dependency service or group failed to start | A service essential for the CCMSETUP process failed to start, likely due to a dependent service being stopped or incorrectly configured. |
| 1130 | Not enough server storage is available to process this command. | Ensure the target client machine has enough free disk space, especially in the temp directory. |
| 1203 | The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator. | Either the network path doesn’t exist, or the network provider is unavailable. |
| 1208 | An extended error has occurred | This error may occur due to network connectivity issues, insufficient permissions, corrupted files, insufficient disk space, or issues with the WMI. |
| 1396 | Logon Failure: The target account name is incorrect. | The issue is likely related to DNS, as the client has duplicate entries in the DNS records. |
| 1450 | Insufficient system resources exist to complete the requested service. | A generic error that mostly indicates the disk space issues or less memory on the client computer. Review the ccmsetup requirements. |
| 1603 | CCMExec could not be stopped | The ccmsetup installer is being interrupted by another component. Exit code 1603 is resolved here. |
| 0000052e | NetUseAdd failed: 1326: dwParamError = 0 | Solution to ccmsetup error 0000052e. |
| 00000005 | Trying each entry in the SMS Client Remote Installation account list | Refer to the guide on resolving ccmsetup error code 00000005. |
| 800706BA | Unable to connect to WMI on remote machine | Read the guide to fix SCCM Client Push Error 0x800706ba. |
| 80200010 | A recoverable error has occurred. A retry attempt will be made. | Refer to the guide on ccmsetup error 80200010. |
| 80200014 | BITS job creation failed with 80200014. | This operating system does not contain the correct version of BITS. BITS 2.5 or later is required. Read this Solution. |
| 80041001 | Setup was unable to create the WMI namespace CCM. | Repair WMI on the problematic client computer. |
| 80041002 | Setup was unable to register the CCM_Service_HostingConfiguration endpoint. | Read the solution to ccmsetup error code 80041002. |
| 8004100e | Failed to revoke client upgrade local policy. | Solution |
| 8004103B | Unable to create the WMI Namespace | Occurs when the workstation is low on disk space. Clear the temp files and reboot the computer to continue with installation. |
| 80041010 | Failed to revoke client upgrade local policy. | Fix for ccmsetup error 80041010. |
| 80070070 | Setup failed due to unexpected circumstances. | Occurs due to disk space issues. Solution. |
| 80070005 | Unable to connect to WMI on remote machine “Computer”, error = 0x80070005. | Ensure that SCCM has administrative access to each workstation where the client installation is required. |
| 80080005 | Server execution failed | Solution |
| 80004004 | Operation aborted | Restart the computer and try the ccmsetup installation. |
| 87D0029E | CCMSetup Failed | Solution |
| 87d00227 | Failed to get assigned site from AD. No valid source or MP locations. | Solution |
| 2147023174 | The RPC server is unavailable | Ensure the firewall or antivirus isn’t blocking the client installation. |
| 2147024891 | Access is denied | Make sure SCCM has admin account on every workstation where it wants to install client. |
| 2147749889 | Generic WMI failure (Broken WMI) | Repairing the WMI resolves this issue. |
| 2147749890 | Not found – Source: Windows Management (WMI) | Repairing the WMI resolves this issue. |
| 2147749904 | Invalid class – Source: Windows Management (WMI) | Repairing the WMI resolves this issue. |
| 2147749908 | Initialization failure – Source: Windows Management (WMI) | Repairing the WMI resolves this issue. |
| 2147942405 | Access is Denied | Create a new firewall rule allowing the client installation. Ensure McAfee-HIPS is configured to allow ccmsetup installation. |
| 2147944122 | The RPC server is unavailable | This error arises due to incorrect security configuration in DCOM. |
| 2148007941 | Server Execution Failed | This suggests a potential component-related problem on the SCCM site server or a network connectivity issue. |
Note: If the table above does not include a specific ccmsetup error code or client installation error code, feel free to mention it in the comments section. I will update the table accordingly, which will also assist other readers.
