In regards to Q981716/MS10-044, it may well have been the case that the update did not correctly apply. It can often be the case with Microsoft updates that once the update is seen as installed by the operating system (i.e. is enumerated as an installed update), the update installer will not execute. In cases such as this, the solution is often to manually remove the update and then re-install (as it appears that you discovered).
In regards to Q2535812/MS11-036, Q2687323/MS12-060, and Q2687483/MS12-064, these updates must be handled uniquely due to the fact that there are two potential methods of installation (i.e. the client installation and the full file installation). In order to handle this architecture, it is necessary that we have two uniquely named files for the updates. In some cases, both files may be identical, differing only by name. In other circumstances, the two files may indeed be unique.
The following detail on the subject (taken from our administration guide, and also available via the 'Help>Index' menu of the Protect GUI) may prove helpful:
"For many Office patches, Microsoft provides two different patch files. A full-file patch contains entire copies of updated files, while binary or client patches contain only the differences between the original file and the updated file. The full-file patches are generally much larger files than the binary patches. The full-file patches, however, are less likely to require access to the original media. VMware vCenter Protect allows you to choose which type of patch to deploy when both types are available.
Note: Only full-file patches are supported by VMware vCenter Protect Agent. Binary Office patches cannot be deployed by VMware vCenter Protect Agent."
We would certainly encourage you to submit ideas you may have using our Feature Request submission form. If you are still unable to resolve any issues which you are having, we would urge you to contact Support directly for immediate assistance.
Thanks a lot for the detail answer.
For the FullFile/Client, in those case, the definition file only permit the use of the client file which is the contrary of the note you mentionned:
"Note: Only full-file patches are supported by VMware vCenter Protect Agent. Binary Office patches cannot be deployed by VMware vCenter Protect Agent."
I may have to precise that we use the agentless method which differ from the agent method.