The software change returned error code 0x87D01281 (-2016406911)

Asked By 20 points N/A Posted on -
qa-featured

Hello,

This came about to me when I was trying to work on ConfigMgr 2012 RC2 installing an App-V package.

When I was trying to use an App-V package to a user, it shows this following error message.

Software Center

Software Center

Unable to make changes to your software
 
There was a problem applying changes to the software. You
can try again. Or, if the problem continues, the information
that is shown in the following section can assist your help
desk in troubleshooting.
 
Click OK to return to Software Center.
 
More information
 
The software change returned error code 0x7001281
(-2016406911).
 
              OK

Please give me a solution.

Thanks.

SHARE
Best Answer by Carl Jack
Best Answer
Best Answer
Answered By 0 points N/A #139837

The software change returned error code 0x87D01281 (-2016406911)

qa-featured

Hello Gloria,

For the following is a workaround that will help you solve that problem:

  • You will need to eject your flash drive into the Win 7 computer, and you will have to copy the ISO you already have to a place on your hard disk, for instance My Documents.
  • You will also need to copy any backups you have on the flash drive for what you are doing is turning it into a startup disk and that will for sure wipe all existing data off it.
  • Once you have done the above, you will then need to download and then run UNetBootin on Windows 7.
  • Last but not least you will point UNetBootin to the ISO you saved, as well as to your flash drive letter, and then you will click OK to create the disk.
UNetBootin on Windows 7

Regards,

Carl

Answered By 15 points N/A #196174

The software change returned error code 0x87D01281 (-2016406911)

qa-featured

One important factor to consider that might be the cause of this problem is the version of the App-V client that you installed in the client machine. Maybe you are using an incompatible or lower version. App-V 4.6 with Service Pack 1 is the one supported by Configuration Manager 2012 RC2. Try to reinstall it using the compatible version and check if the problem is resolved.

Login/Register to Answer

Related Questions