Fix The Software Change Returned Error Code 0x87D00669

While deploying the software updates using SCCM, the software change returned error code 0x87D00669 was reported. Let’s look at how to fix the error code 0x87D00669.

Troubleshooting Configuration Manager issues is a vast topic, and it is always interesting because an error code may have alternative solutions. Most of these errors are reported in Intune SCCM forums, and we try to resolve them.

When you deploy updates using SCCM, you may encounter several errors. One such error is “the software change returned error code 0x87D00669” that appears in software center on the client computer.

Another common error that I see is SCCM Application Installation Error 0x87D00607. If you have set up things correctly, you should not encounter these common issues.

I got an email over the weekend asking me the solution for SCCM error code 0x87D00669 during updates deployment. The Office updates were deployed using ConfigMgr but on some computers the updates failed to install with error code 0x87D00669.

Fix The software change returned error code 0x87D00669

First let’s look at the error details for the software change returned error code 0x87D00669. We see the error 0x87D00669 appears in software center with title unable to download the software.

Error code 0x87D00669 = Client unable to get software updates content locations at this time. This means the client can’t find the update on the distribution point servers. The solution is to check if the package is distributed to distribution points and boundaries are set up correctly.

The most common reason why you encounter the error 0x87D00669 in software center is due to two reasons.

1. Content Not Present on DP – The content is not distributed to distribution points. This results in software center showing downloads stuck at 0% and eventually error 0x87D00669. In such situations, refer my guide on how to fix SCCM Application Download Stuck at 0% in Software Center.
2. Missing Boundaries and Boundary Groups – The applications or updates install only when they first locate the distribution point and download the content. If the clients don’t know from where the content has to be downloaded, they sit on downloading state for some time and eventually fail. So, you must first check the boundaries and boundary groups. The Boundaries in Configuration Manager define network locations on your intranet. These locations include devices or clients that you want to manage.