Nice work-around oh great darkest one!
...JohnBick
Categories: Patches and Upgrades
Have you seen this error,

one work around I have found is to simply click OK and try it again. I have found that for me within four or five rapid trys it will install.... (My impression is the more rapid you do this the more likely it is to install). Hope this helps. Works for Power Pack 1 and the April update, MS12418999ENG.exe foir me.
JohnBick, Thank you. (I'll take that at it's face value having been baned by your group, without so much as a word of explanation, or reason.) Can you verify that this trick works for you? I've tried installing and removing this way, and it **appears** that after a sequence of installed/uninstalled that the next install doesn't create the error.... I haven't tried this enough to be sure, yet.
Cannot verify personally as it has not occurred for me. I did, however, pass a link to this on to someone else (not on either MSS board) and she tried it. I believe that was what worked for her -- I did get a response that it was fixed.
...JohnBick
Regarding error 1618. First of all what does it mean? Second I have just rebooted my server after McAfee was not able to update and displayed an error regarding the cab. I have this same software installed on my client machines and rebooting takes care of this problem on them. Hence the reboot on the server. It worked, and Mcafee updated correctly. However looking in my event log I now have a warning: "Failed to open package handle (with the name of an addin I have installed) and 1618 following that. This happens for each of my installed addins (I have removed all the uninstalled addins). after listing them once it keeps going through this cycle continuously. This started after I rebooted the server. All of my addins seem to function correctly. When I tried to collect a log to send to Microsoft I couldn't obtain a cab number through WHS Toolkit. It came back with the message "talq did not return" Any suggestions?
Barry Heath