Some error codes I’ve come across using SCCM (mostly shown on clients during software installation, task sequence execution or update installation):
|0x00000032 (OSD task sequence)||Wrong OS active.||Can occur when a task sequence tries to install applications while WinPE is still active. Add a task sequence step “reboot” and make sure it boots the installed OS instead of WinPE.|
|0x4005 (16389) (Software installation, OSD task sequence)||Extraction fails / Data missing||Can happen with some packages (e.g. .NET Framework 4.6.2), the extraction process fails. Activate “Run installation and uninstall program as 32-bit process on 64-bit clients.” within the application.|
In task sequences (OSD/BaC) make sure the data is accessible on a DP (redeployment may help) and within the boundary. For BaC task sequences, make sure there is a fitting IP subnet based boundary (NOT through AD sites and services!).
|0x643(1603) / 0x80070643|
|Installation requirement missing||An installation requirement (e.g. VC++ or .NET) is missing. Run the installer non-silent to see what exactly is missing. Also occurs when trying to install the Microsoft Monitoring Agent on systems which have other Operations Manager components installed. In VMware Horizon View installations this may happen due to a not well-formed hosts file.|
|0x80004004 (Update deployment)||ADR operation aborted||Make sure the schedules of the automatic deployment role (ADR) and the WSUS sync do not overlap.|
|0x80070002 (OSD task sequence)||Network/DNS issue||Can have multiple reasons, usually connected with network issues. Check smsts.log and make sure the network configuration (especially DNS) is correct.|
|0x80070005 (OSD task sequence)||Failed to join domain||Delete existing computer objects with same name in Active Directory, make sure the account used to join the domain has sufficient permissions.|
|0x80070032 (OSD task sequence)||Incompatible boot image.||Make sure the version (x86/x64) of the boot image fits the version (x86/x64) of the OS image you are trying to apply.|
|0x80070057 (OSD task sequence)||Wrong/missing partition||Check “Destination:”-setting in the “Apply Operating System” task sequence step.|
|0x80070070 (Software installation)||Not enough free disk space.||Expand the disk or delete expendable files.|
|0x80070103 (Software installation)||Failing driver insertion||Occurs when a software tries to install a driver which is already installed (in same or newer version). Remove existing drivers of use newer version of the software.|
Also occurs then using a wrong licence key during MS Office installation.
|0x80070490 ([BAC] task sequence)||Faulty sysprep configuration/faulty disk config||Might occur during the “Preparing OS” stage and often relates to faulty sysprep or disk settings. Check sysprep configuration and make sure the disk is available. Try the steps below from http://blog.tofte-it.dk/sccm-task-sequence-error-0x80070490/|
Press “F8“ -> Run “diskpart.exe“ -> “select disk 0“ -> “clean“ -> “create partition primary“ -> “active“ -> “format fs=ntfs quick“ -> “assign letter=C:“ -> “Exit“ -> Reboot and run the task sequence again.
|0x80070656 (Software installation)||Log file cannot be written||Stands for: ERROR_INSTALL_LOG_FAILURE |
Make sure the path to write the log file is correct and available.
|0x8008013 (Software Installation)||A dependency was not properly run||Stands for: E_FAIL_DEPENDENCY_NOT_RUN|
Check which dependency could not be run and troubleshoot it or work around this issue by putting the applications into a task sequence.
|0x80091007 (Software installation)||Hash mismatch||Occurs when the downloaded package on a client has a different hash than the one on the server because …|
a) Files within the package contain illegal characters. => Use FindBadFiles.vbs from
b) Files on a distribution point are corrupted. => Redistribute contenct to distribution points.
c) The memory is corrupted. => Check/repair memory.
|0x80240009 (Update installation)||Another conflicting operation was in progress||The update cannot be installed because some other installation was in progress or a reboot was pending. Reboot the system and try again.|
|0x8024000B (Update installation)||Pending reboot / Update manifest missing||The update cannot be installed because there is a reboot pending due to a software or update installation. Reboot the system. Can also happen when SCCM detects an software that has already been uninstalled (e.g. by remaining files or reg keys). Cleanly uninstall the software.|
|0x80240037 (Update installation)||Processor too new to be supported.||The “Kaby-Lake”-Problem in Windows 8.1. Install a newer OS or use the zeffy wufuc (https://github.com/zeffy/wufuc).|
|0x80244022 (Update installation)||IIS application pool not running||Go to IIS management console on WSUS server, right-click the Application Pool “WsusPool” and click “start”. See https://blog.ctglobalservices.com/configuration-manager-sccm/kea/house-of-cardsthe-configmgr-software-update-point-and-WSUS/ for information on cleanup procedures and create a rule in SCOM that automatically starts the pool if it is stopped.|
|0x87d00269 (BAC task sequence)||Cannot contact management point||Happens mostly when a computer is not joined to the domain (e.g. during build and capture). Join the computer to the domain in an earlier task sequence step or add “SMSMP=<mySCCMserver.mydomain.com>” to the installation properties of the SCCM client.|
|0x87d00324 (Software installation)||Software not detected after installation||Make sure the detection method is configured properly; run software from a script and add an applicable timeout inside the script.|
|0x87d00607 (Software installation)||Cannot get content||Make sure the client has a distribution point that can supply it with the required files. Check if the client has an active boundary assigned and that the boundary has a content location assigned.|
Can also occur when the client cannot determine its location due to a not-running IIS on the SCCM server. Make sure IIS is running and the service “World Wide Web Publishing Service” is running.
|0x87D00664 (Update Installation)|| |
Maximum run time exceeded
Edit the causing software update: right-click -> properties -> Tab “Maximum Run Time” -> increase the value.
Reboot of the client might also help. (Same as 0x87d0070c)
|0x87d0070c (Update installation)||Maximum run time exceeded||Edit the causing software update: right-click -> properties -> Tab “Maximum Run Time” -> increase the value.|
Reboot of the client might also help.
|0x87d00667 (Software installation)||No applicable maintenance window||Add the client to a collection with a maintenance window long enough to install the software or reduce the expected execution time within the application.|
Still not enough? See the list of SCCM client installation error codes at https://www.systemcenterdudes.com/sccm-client-installation-error-codes/