The software change returned error code 0x87D00669(-2016410007).

Question

_{Tuesday, February 6, 2018 5:50 PM}

I recently consolidated our monthly 2017 ADR SUGS into one baseline 2017 SUG.  When I did that, a few updates popped up in Software Center for our workstations/servers, stating that they were available.  When trying to install them, they return the following error:

The software change returned error code 0x87D00669(-2016410007).

I think part of the problem is that the 2017 monthly ADR's were saving all files to the 2017 package.  Well, when I consolidated all my SUGS, I deleted the 2017 package and recreated it using a fresh baseline for the year.  I think the updates in the November/December ADR's, for example, may of had their files stored in the old 2017 package, and now they don't exist, even though the status for all these updates shows "Downloaded" when exploring all updates within the new 2017 SUG I created.

How do I go about troubleshooting this?

All replies (1)

_{Tuesday, February 6, 2018 7:22 PM}

0x87D00669 = "Not able to get software updates content locations at this time"

That seems to fit your hypothesis, but it could also be that the package simply hasn't updated on all of your DPs so check that first.

Next, if an update is deployed but not downloaded, it will show up with a red X icon next to it in the software update group. Thus, you can simply show the members of the update group and see if this is the case -- there is also a "Downloaded" column that you can add or filter by. If this is the case, simply right-click on them and download them to your new package.

Finally, this cleanup garbage is one of the multiple reasons that I don't use or recommend using monthly update groups.

Jason | https://home.configmgrftw.com | @jasonsandys