Adobe Acrobat Reader DC Update 21.001.20135: Issue

[MrRobot13]

Testing the update Adobe Acrobat Reader DC Update 21.001.20135 to my pilot group today appears to have issues.
Within the console it only reported as failed on 1 machine of 4 total. The other 3 are stuck as "Unknown" for the status of this software update group which only contains PatchMyPC updates. The other updates within the SUG have installed except for Adobe Reader. It states failed locally in Software Center for those machines. If you Retry the install in Software Center it does successfully install however. Currently on ConfigMgr2010, btw.

I have not seen this sort of activity in the past.

Thank you

[Justin Chalfant (Patch My PC)]

Unknown status means the machines aren't scanning against your SUP. There are a few things that could cause this could you please check out https://patchmypc.com/troubleshooting-sccm-clients-with-unknown-update-state

For the failure, we would need some additional info. The client side update logs would be helpful https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#update-troubleshooting-client-logs via a support case here https://patchmypc.com/technical-support

Testing the update Adobe Acrobat Reader DC Update 21.001.20135 to my pilot group today appears to have issues.
Within the console it only reported as failed on 1 machine of 4 total. The other 3 are stuck as "Unknown" for the status of this software update group which only contains PatchMyPC updates. The other updates within the SUG have installed except for Adobe Reader. It states failed locally in Software Center for those machines. If you Retry the install in Software Center it does successfully install however. Currently on ConfigMgr2010, btw.

I have not seen this sort of activity in the past.

Thank you

[MrRobot13]

Thanks Justin,
I've opened up a support case as your suggested.

[Cody Mathis (Patch My PC)]

This is likely due to a new UWP app that Adobe is packaging with the software. We will be updating our commandline today but you should be able to add  INSTALLUWPAPP=NO to your command line to prevent these errors from happening.