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

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

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

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

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