The Software Change Returned Error Code 0x87d00607, Causes and Fixes

The Software Change Returned Error Code 0x87d00607 issue is addressed here, get rid of the frustration caused by error code 0x87d00607 during software changes with the help of this article.

by Srinithi | Updated Jun 08, 2023

The Software Change Returned Error Code 0x87d00607, Causes and Fixes

The Software Change Returned Error Code 0x87d00607

The error code 0x87D00607, also known as "The Software Change Returned Error Code 0x87D00607," refers to a specific issue encountered during software installation or deployment using Microsoft System Center Configuration Manager (SCCM). This error code indicates that the content required for the installation or deployment process cannot be found.

When this error occurs, it typically means that SCCM or the client computer is unable to locate the necessary files or resources needed to complete the software change. The exact cause of this error can vary, but it is often related to configuration issues, such as incorrect boundary or boundary group settings, problems with pre-staged content, or restrictions imposed by firewalls.

Resolving this error requires troubleshooting the specific configuration and environment to identify and address the underlying cause.

Common Causes For Error

Improper configuration of boundaries or boundary groups:

One possible cause of the error code 0x87D00607 is the incorrect configuration of boundaries or boundary groups in SCCM. Boundaries and boundary groups define the network locations where clients can be found. If these configurations are not set up correctly, SCCM may fail to locate the content required for software installation or deployment, resulting in the error.

 Pre-staged content:

Another potential cause is related to pre-staged content. Pre-staging involves copying content to distribution points in advance, which can improve deployment performance. However, if the pre-staged content is not properly synchronized or updated, SCCM may encounter difficulties in finding the necessary content during installation, leading to the error 0x87D00607.

 Blockage from the firewall:

Firewalls play a crucial role in network security by filtering and controlling incoming and outgoing traffic. In some instances, the firewall settings may block or restrict the communication between the SCCM client and the necessary content sources. This can prevent the client from accessing the required files, resulting in the error code 0x87D00607.

Resolving the error code 0x87D00607 typically involves addressing these potential causes. It may require verifying and adjusting boundary and boundary group configurations, ensuring the synchronization and availability of pre-staged content, and reviewing firewall settings to ensure proper communication between the SCCM client and content sources.

How to Fix the Software Change Returned Error Code 0x87d00607

Here is a detailed guide on how to resolve the error code 0x87D00607 in SCCM (Microsoft System Center Configuration Manager:Reboot the Primary SCCM Server: Start by rebooting the primary SCCM server as a simple troubleshooting step. Sometimes, a restart can resolve temporary issues.

Check Date and Time:

Ensure that the date and time settings are correct on both the server and client machines. Incorrect date and time settings can cause communication problems and lead to the error. Additionally, make sure all updates and hotfixes for SCCM are applied to your machine.

Verify User Presence in SourceContentLib Directory:

Check if the affected users are present in the SourceContentLib directory. If they are missing, add the users to the directory and check if the issue is resolved.

Use Official Installer/Uninstaller: If you are deploying a package or application that has an official installer or uninstaller (such as Adobe CC Uninstaller), try using that official installer/uninstaller instead. Sometimes, using the recommended installation method can help resolve the error.

Check Dependencies:

Verify if the package or application has any dependencies. If there are dependencies, ensure that they are included in the source files of the package or application. Missing dependencies can cause installation failures.

Uninstall Older Version: 

If you are trying to install an updated version of an application that is already installed on the client machine, try uninstalling the older version first. Removing the older version may allow the installation of the newer version without encountering the error.

Change Default Browser of the Client Machine:

Set the default browser of the client machine to either Internet Explorer or Microsoft Edge, as some applications may have dependencies on these browsers in a corporate networking environment. Ensure that the default browser is set correctly and reboot the client machine.

Add SMS_DP Path in IIS Settings:

On the Distribution Point (DP) server, configure the IIS settings by adding the SMS_DP path in the ISAPI and CGI Restrictions. This step ensures that the DP functions properly and resolves any issues related to content distribution.

Use HTTP for Client Connections:

If the client connections are configured to use HTTPS protocol, try changing them to use HTTP protocol instead. Improper configuration of client connections can cause communication problems, and switching to HTTP may resolve the issue.

Unblock Source Files:

If the operating system doesn't trust some of the source files, they may be blocked from execution, resulting in the error. Navigate to the source files directory, right-click on each file, and check if there is an option to unblock them. Unblock all the source files and check if the error is resolved.

Change Deployment Options:

Ensure that the Deployment Options of the package or application are configured to download content from the distribution point and run locally. Modify the Deployment Options settings accordingly and apply the changes.

Disable Pre-staged Content on Distribution Point:

If pre-staged content is enabled on the distribution point, try disabling it. Disabling pre-staged content can help resolve issues related to content availability.

Enable Fallback Location for Content: Enable the fallback location for content on the distribution point. This allows clients to fetch the content from an alternative source if the preferred distribution point is inaccessible.

Allow Clients to Use Distribution Points:

Ensure that clients' machines are allowed to use distribution points from the default site boundary group. This setting enables clients to access the necessary content for installation.

Edit Boundaries and Boundary Group:

Verify and edit the boundaries and boundary group configurations in SCCM. Ensure that the IP addresses of client machines are correctly added to the boundaries and boundary groups.

Allow SCCM Required Ports in Firewall:

Check if the SCCM's required ports are blocked by the firewall on

Unable to Download Software Change Returned Error Code 0x87D00669

The error code 0x87D00669 (-2016410007) typically occurs when there is an issue with downloading software from SCCM (System Center Configuration Manager) during an application installation. Here are some steps you can take to troubleshoot and resolve the issue:

Check network connectivity: Verify that the client machine has a stable network connection. Ensure that there are no network interruptions or firewall restrictions that could be blocking the download.

Restart the SCCM client services: Restart the SCCM client services on the affected machine. You can do this by opening the "Services" console (services.msc), locating the SCCM-related services (such as "SMS Agent Host" or "ConfigMgr Client") and restarting them. After the services restart, try the application installation again.

Verify content availability:

Ensure that the content for the application is available on the distribution point. Check if the distribution point has the necessary files and that they are accessible. You can do this by navigating to the distribution point location and verifying the presence of the required files.

Check distribution point health:

Validate the health of the distribution point by reviewing the SCCM console. Ensure that the distribution point status is healthy and that there are no errors or warnings related to the distribution point configuration.

Review boundary and boundary group settings:

Confirm that the client machine is within the appropriate boundary and boundary group in SCCM. Boundaries and boundary groups control the assignment of distribution points to clients. If the client is not within the correct boundary or boundary group, it may not be able to download the content.

Clear the SCCM client cache:

The SCCM client cache stores temporary files related to software installations. Clearing the cache may help resolve download issues. To clear the cache, stop the SCCM client services, navigate to the client cache folder (typically located at C:Windowsccmcache), and delete all the files and folders within it. Then restart the SCCM client services and retry the application installation.

Monitor the ContentTransferManager.log:

The ContentTransferManager.log file on the client machine provides detailed information about the download process. Review this log file for any specific error messages or warnings that could provide insight into the issue. The log file is located in the SCCM client logs folder (typically found at C:WindowsCCMLogs).

Review SCCM client settings:

Check the SCCM client settings to ensure they are configured correctly. Make sure that the client is set to receive content from theappropriate distribution points and that the required bandwidth settings are properly configured.

Check client machine storage space:

Verify that the client machine has sufficient free disk space to download and install the application. Insufficient disk space can cause download failures. Check the available storage on the client machine and free up space if necessary.

Review SCCM client installation logs:

The SCCM client installation logs may contain valuable information about the client's connectivity and configuration. Review the relevant logs, such as ccmsetup.log and ClientIDManagerStartup.log, located in the SCCM client logs folder, for any errors or warnings that could be related to the issue.

Test with a different application/package:

Attempt to install a different application or package through SCCM to determine if the issue is specific to the problematic application. If other installations work fine, it may indicate an issue with the specific software package itself.

If the above steps do not resolve the issue, it is recommended to involve your helpdesk or IT support team for further assistance. Provide them with the error code and any relevant log files to help in the troubleshooting process

Disclaimer: The above information is for general informational purposes only. All information on the Site is provided in good faith, however we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability or completeness of any information on the Site.

The Software Change Returned Error Code 0x87d00607-FAQ

1.  What does the error code 0x87D00669 mean?

 The error code 0x87D00669 indicates a problem with downloading software from SCCM (System Center Configuration Manager) during an application installation.

2. What should I do if I encounter this error code?

You can try the following steps to troubleshoot and resolve the issue:

Check network connectivity.

Restart the SCCM client services.

Verify content availability on the distribution point.

Check the health of the distribution point

3.  How can I check network connectivity?

Verify that the client machine has a stable network connection and ensure there are no network interruptions or firewall restrictions that could be blocking the download.

4. How do I restart the SCCM client services?

Open the "Services" console (services.msc), locate the SCCM-related services (such as "SMS Agent Host" or "ConfigMgr Client"), and restart them.

5. What should I do if the distribution point is not healthy?

Review the SCCM console for any errors or warnings related to the distribution point configuration. Address any issues found to ensure the distribution point is healthy.

Recent Articles Protection Status