This content has been marked as final. Show 5 replies
Oops, last sentence should have ended with "complete Office 2007 update cycle of RTM -> SP1 -> SP2 -> SP3."
Not real certain of the question being posed here. Hopefully the following will help.
The following article should provide some insight into the reason for which Microsoft Update has offered the update:
Because SP3 is not one of the affected versions of Microsoft Office (as per Microsoft), Protect will not scan for this update on the machine in question once it has detected that the installed version is at SP3.
Thanks for the response. I was aware that this happens sometimes as mentioned in the Microsoft KB you referenced, but since I could see that it was actually changing a file, I guess I just wanted to make sure it was the expected behavior.
I have read the article referenced above. The problem I have is that we are required to use eEye Digital Security's Retina Network Security Scanner and it is detecting that this patch is missing and is listed as a Category 1 finding which our IA department requires to be corrected. After applying the Microsoft patch, the Retina Network Scanner no longer identifies this as a finding and the specific file %CommonProgramFiles%Microsoft SharedTextConvworks632.cnv is updated to the new version. It seems that if the patch wasn’t required, it would say so when it is installed.
If you are suggesting that there is an affected product installed on your target machine (to which the update in question should be considered applicable), and our scan does not indicate that the update is applicable, then this is certainly an issue which should be identified and corrected. Please contact support directly for assistance so that we can collect the necessary details and address the issue expediently.