Операция изменения программного обеспечения вернула код ошибки 0x87d00669 2016410007

RRS feed

  • Remove From My Forums
  • Общие обсуждения

  • При попытке установить обновления из Software Update Centre получаю ошибку: «Операция изменения программного обеспечения вернула код ошибки 0x87D00669(-2016410007).» На всех серверах. Поиск, увы, результатов не дал. Помогите
    понять. 

Все ответы

  • что такое «Software Update Centre»? Я знаю только «Центра программного обеспечения» или в англ. версии «Software Center».

    А такая ошибка может говорить о том, что клиент не может найти контент. Покажите UpdatesHandler.log

    зыж еще вариант, это тот ли язык вы выбрали при скачивании обновлений, посмотрите

    этот топик.

    • Изменено
      Anton MasyanMVP, Moderator
      27 октября 2014 г. 8:44

  • Remove From My Forums
  • Общие обсуждения

  • При попытке установить обновления из Software Update Centre получаю ошибку: «Операция изменения программного обеспечения вернула код ошибки 0x87D00669(-2016410007).» На всех серверах. Поиск, увы, результатов не дал. Помогите
    понять. 

Все ответы

  • что такое «Software Update Centre»? Я знаю только «Центра программного обеспечения» или в англ. версии «Software Center».

    А такая ошибка может говорить о том, что клиент не может найти контент. Покажите UpdatesHandler.log

    зыж еще вариант, это тот ли язык вы выбрали при скачивании обновлений, посмотрите

    этот топик.

    • Изменено
      Anton MasyanMVP, Moderator
      27 октября 2014 г. 8:44
  • Remove From My Forums
  • Question

  • 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?

    • Edited by

      Tuesday, February 6, 2018 5:51 PM

  • Remove From My Forums
  • Question

  • 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?

    • Edited by

      Tuesday, February 6, 2018 5:51 PM

  • Remove From My Forums
  • Question

  • 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?

    • Edited by

      Tuesday, February 6, 2018 5:51 PM

  • Remove From My Forums
  • Question

  • 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?

    • Edited by

      Tuesday, February 6, 2018 5:51 PM

The reason for the error could be insufficient permissions

by Srishti Sisodia

Srishti Sisodia is an electronics engineer and writer with a passion for technology. She has extensive experience exploring the latest technological advancements and sharing her insights through informative… read more


Updated on April 19, 2023

Reviewed by
Alex Serban

Alex Serban

After moving away from the corporate work-style, Alex has found rewards in a lifestyle of constant analysis, team coordination and pestering his colleagues. Holding an MCSA Windows Server… read more

  • This update error could occur if the content is missing, or boundary or boundary groups are not properly set.
  • You can check the boundaries, and boundary groups, or redistribute content to fix this issue.

XINSTALL BY CLICKING THE DOWNLOAD FILE

Easily get rid of Windows errors
Fortect is a system repair tool that can scan your complete system for damaged or missing OS files and replace them with working versions from its repository automatically.
Boost your PC performance in three easy steps:

  1. Download and Install Fortect on your PC.
  2. Launch the tool and Start scanning
  3. Right-click on Repair, and fix it within a few minutes
  • 0 readers have already downloaded Fortect so far this month

If you have encountered the 0x87D00669 (-2016410007) error while deploying updates via SCCM on a computer, this guide can help!

This error indicates that the client’s computer can’t find the update in the distribution package. We will discuss some popular fixes to resolve the issue in no time.

What causes the 0x87d00669 SCCM update error?

There are several reasons for the update error to occur; some of the common ones are listed here:

  • Content corrupted– If missing or corrupted, the content (update package & files) required for update installation may cause this SCCM update error.
  • Permission issues – The user account running the SCCM client doesn’t have appropriate permissions to install updates on the client’s machine.
  • Client communication issues – If the client machine cannot communicate with the SCCM server due to firewall settings or network issues, it could lead to an error.
  • Missing Boundaries and Boundary Groups – The apps or updates are installed after locating the distribution point and downloading the content; if the client can’t access the content, you might see this error. Check boundaries and boundary groups to ensure the network location is correctly set.

Now that you know how the error occurred, let us move on to the steps to fix the problem.

How can I fix the 0x87d00669 SCCM update error?

1. Check the boundaries

  1. Press the Windows key, type configuration manager console, and click Run as administrator to launch SCCM.
  2. Navigate to this path: AdministrationOverviewHierarchy ConfigurationBoundariesBoundaries 0x87d00669
  3. Now check the boundary set as IP range or anything appropriate.

2. Check the boundary groups

  1. Press the Windows key, type configuration manager console, and click Run as administrator to launch SCCM.
  2. Go to this path: AdministrationOverviewHierarchy ConfigurationBoundary GroupsBoundary group 0x87d00669
  3. Select a boundary group, and right-click it to choose Properties.
  4. Switch to the References tab, and click Add to add a new boundary.
  5. In the Add Boundary window, choose the type of boundary you want to add. You can select among IP subnet, Active Directory site, IPv6 prefix, or IP address range.
  6. Configure the properties of the boundary according to the selected boundary type and click OK.
  7. On the References tab, place a checkmark next to Use this boundary group for site assignment and click OK to save the changes.Use this boundary group  0x87d00669for site assignment

3. Redistribute an application to the distribution points

3.1 Use the Software Library

  1. Press the Windows key, type configuration manager console, and click Run as administrator to launch SCCM.
  2. Navigate to this path: Software LibraryApplication ManagementApplicationsApps 0x87d00669
  3. Select the application from the available options: Package, Software Update, Applications, Boot Image, Operating system images, and more.
  4. From the Home tab, click Properties.
  5. In the Properties wizard, on the Content Locations page, select the distribution points or distribution points groups and click Redistribute.
  6. Click OK on the following prompt.
Read more about this topic

  • Fix: FileType Selected Not Supported by This App
  • 0x8007274d Mail Sync Error: How to Fix it

3.2 Use the Administration workspace

  1. On the SCCM console, go to this path: AdministrationOverviewDistribution PointsDP 0x87d00669
  2. Select the distribution point to which you want to redistribute the content.
  3. From the Home tab, select Properties.
  4. Go to the Content tab, select the content, and click the Redistribute button.
  5. Click OK.
  6. Go to this path and check if the application content is copied successfully: MonitoringOverviewDistribution StatusContent Status
  7. Right-click on the content and select View Status.
  8. If there is an issue, right-click the Distribution point and select Redistribute again.Redistribute 0x87d00669

In case you’re looking to upgrade your Windows 7 computer to Windows 10 using SCCM, make sure to check out our article.

So, these are the steps you need to follow to fix the 0x87d00669 SCCM update error. If you have any questions or suggestions, please feel free to mention them in the comments section below.

Still experiencing issues?

SPONSORED

If the above suggestions have not solved your problem, your computer may experience more severe Windows troubles. We suggest choosing an all-in-one solution like Fortect to fix problems efficiently. After installation, just click the View&Fix button and then press Start Repair.

newsletter icon

Let’s understand how you can FIX SCCM Unable to Download Software Change Returned Error Code 0x87D00669. The error 0x87D00669 (-2016410007) prompts when you attempt to install an application or update from SCCM software center.

First of all, you will need to understand the meaning of the error code 0x87D00669. You can use the method to translate SCCM Error Codes To Error Messages.

The error code 0x87D00669 translates to Not able to get software updates content locations at this time. This means the client can’t find the update in the DP’s. You need to make sure your package is distributed and boundaries set up.

Fix Unable to Download Software Change Returned Error Code 0x87D00669

Fix Unable to Download Software Change Returned Error Code 0x87D00669

You might also be experienced the error 0x87D00607 while installing the applications from the software center. That also indicates a similar issue there was a problem downloading the software from SCCM. 

Patch My PC

Here you can check details for major components involved in SCCM application model troubleshooting. This post will help get more information about why the installation failed and learn the Deep Dive SCCM Application Model Troubleshooting.

  • Fix Scan failed with error 0x80244022 Service is Temporarily Overloaded Issue SCCM
  • FIX: SCCM Application Installation Failed 0x87D00607
  • Fix the SCCM Software Center cannot be loaded Issue with ConfigMgr

Issue Descriptions – SCCM Unable to Download Software Change Returned Error Code 0x87D00669

The error application installation failed 0x87D00669 (-2016410007) was received while installing an application from Software Center.

It indicates there was a problem downloading the software from SCCM. You can try starting the installation again, or if the problem continues, the information shown in the section below can assist your helpdesk in troubleshooting.

The software change returned error code 0x87D00669, Unable to download the software with Status Failed.

Adaptiva

SCCM Unable to Download Software Change Returned Error Code 0x87D00669

SCCM Unable to Download Software Change Returned Error Code 0x87D00669

Let’s analyze the ConfigMgr logs before proceeding to the next step, CAS.log, ContentTransferManager.log, and LocationServices.log.

Possible Reasons

Let’s check the possible solutions to FIX SCCM Software Change Returned Error Code 0x87D00669. It could be different based on the details you get into logs –

The first step is to validate whether the deployed package content is successfully distributed to applicable distribution points or groups. If the content is not distributed to the SCCM distribution point, the clients would go to the DP and find no content to download.

To avoid issues with the content distribution of SCCM packages. Let’s check how to Redistribute package or application content to Distribution Point. I had seen in many scenarios If we are facing the content download issue in all sites locations. In this scenario, Try to remove the content from distribution points, and package redistribution will work.

The next step is to validate Is the boundary that the client is in added to a boundary group associated with the DP that has the content.

If you start looking at the LocationServices logs, it shows “calling back with empty location” which means the boundaries were not set for this location. Adding site to DP, start the content downloading properly.

It’s always best to 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.

The error can also occur when an update requires another update to be installed, but the location to download is not found. Check UpdateHandler.log to see if it’s your case. 

Author

About Author – JiteshMicrosoft MVP, has over five years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus is Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.

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.

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 software change returned error code 0x87D00669

The software change returned error code 0x87D00669

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.

Photo of Prajwal Desai

Prajwal Desai is a Microsoft MVP in Enterprise Mobility. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.


Back to top button

  • Операция изменения программного обеспечения вернула код ошибки 0x87d00324 2016410844
  • Операция изменения программного обеспечения вернула код ошибки 0x643 1603
  • Операция гроза или ошибка сталина
  • Операция банк сверка итогов закончилась ошибкой
  • Операция print fiscal receipt ошибка 200