Windows Update KB952142 Corrupts Outlook 2007

[Chris Rowlatt]

Hi,

I recently installed Office 2007 and once I had activated it I did a
complete update for office (14 updates in total) and I found that Outlook no
longer opened - I got an error to do with one of the dlls and a method known
as _invoke_watson.

After several uninstalls and reinstalls I found a reference on here about
Acer eDataSecurity which I duely uninstalled however this did not fix the
problem so I begun narrowing down the updates to see which one caused the
crash. I found it to be the KB952142 update (Update for Microsoft Office
Outlook 2007); all other office programs work fine with update (as its an
update for outlook)... it's a bit frustrating as windows installs the update
on its own and then restarts the damn comp on its own and so I have to keep
restoring windows to get it to work!

I am lookin into stopping the automatic update and restart feature but i'm
not sure if vista will allow me to do so.

Any help would be greatly appreciated,

Thanks in advance,
Chris

 

[neo [mvp outlook]]

Hmm... not sure what to suggestion other than make sure that you have
installed Office 2007 SP1 before installing this update (or avoid this one
and install
http://support.microsoft.com/default.aspx?scid=kb;en-us;950219&sd=RMVP)

Other than that, I'm not seeing this issue under Windows XP SP2/SP3 (don't
have/use Vista)

/neo

PS - I don't have any 3rd party Outlook addins. Could also be a weird
incompatibility problem between update and 3rd party program that integrates
with Outlook.

 

[Chris Rowlatt]

Thanks for your response Neo; I have got SP1 installed and I tried that link
you gave me but I got the same error... You may be right that I've got some
3rd party software installed that is conflicting with outlook but I went
through my programs and I can't see how any of them can be as they've got
nothing to do with Calendars or E-mail or encryption.

I am going to fish around my comp though and try different things nad also
check theregister to see if they've got any solutions.

Thanks though for your reply and the link you sent me; hopefully i'll find
out the reason why soon

Cheers,
Chris