The problem seems to me to be that where Windows Update sees that
a matching Visual Studio SKU is installed on the local machine, it
attempts to apply the update. But Crystal Reports for Visual Studio
being an -optional- component of Visual Studio, it (that is, Crystal
Reports) is not always installed.
So although Windows Update would report the update as having
been “successfully” installed, it would in short order re-prompt to
install it again. And again. And again, ad infinitum. (On 32-bit Vista
Ultimate, I have entries in WU’s ‘update history’ for one, two, three..
eight “successful” installations of this update..)
Adding Crystal Reports to the Visual Studio installation enables
Windows Update to properly apply the update and subsequently recognise
it as having been installed; incidentally, the process of actually
installing the update -seems- to happen perceptibly more quickly than
that of -not -really installing it but reporting it installed all the
same.
Finally, subsequently un-installing Crystal Reports for Visual
Studio seems also to un-install the update, whereupon Windows Update
prompts, again, to install it and one is, presumably, apt to find
oneself back in the same cycle.
--
atthefalcon
|