Managing and deploying updates via Configuration Manager
0x87D00664 (-2016410012) is not defined in the provided material, but the documented next step for Configuration Manager app install failures is to use the client and installation logs to determine why the install stopped.
For this scenario, the most relevant checks are:
- Review the client-side install logs around the failure time:
-
PolicyAgent.log -
AppDiscovery.log -
AppEnforce.log
-
- Check whether the content actually finished downloading to the client. A long download followed by failure can happen when:
- the local SCCM cache is full
- the software could not be downloaded completely before the installation deadline expired
- On the affected client, clear the Configuration Manager cache and retry:
- Open Control Panel
- Open Configuration Manager
- Select the Cache tab
- If needed, select Configure Settings and provide admin approval
- Select Delete Files
- Retry the installation
- Review Windows event logs for events at the same time as the failure:
- Run
eventvwr.msc - Compare the timestamps with the app deployment failure
- Run
- If installer logs exist, enable or review Windows Installer logging and look for
Return value 3near the failure point. - If the deployment has a maintenance window, verify whether it is delaying or interrupting the install. One accepted resolution in a similar SCCM case was to check Client Settings > Computer Agent > Additional software manages the deployment of applications and software updates.
If the package is a Visual Studio-related update, also verify whether another setup process or Visual Studio itself was running on the client, because documented Visual Studio update failures include these conditions:
-
1001: Visual Studio Installer or related setup process is running -
1003: Visual Studio is in use -
8006: VS-related process is running -
1004: no internet detected -
8007070: not enough disk space
If this is an administrator update workflow, check %temp% for dd_updatedriver, dd_bootstrapper, dd_client, and dd_setup logs and confirm whether they end with success code 0.
References: