Office 2010 Woes

Just installed Office 2010 Professional Academic and the software looks pretty great, except for this one annoyance. Any time I close either Word or Excel, it will close and then three seconds later display an error that says, "Word (or Excel, as the case may be) has stopped working..." I click cancel and it says, "Word (or excel) is trying to recover your document." Then I click cancel on that dialog and it quits.

This happens almost every time I close the program...I'd love to fix it, but it is mainly an annoyance. I followed a regedit change online to fix Word's problem, but couldn't find anything for Excel. The Word fix seems to work, until I open Excel, in which case the word problem starts again. So the root seems to be in Excel. Is there a fix?

AA

If you run installtaion again from file or disk you will have option to repair installation, try this for begining...:)

Hey mindinka. I will try re-installing the software this afternoon. The only reason I hadn't yet is because I had seen online that this registry fix would fix the problem, and that users generally reported no success with a reinstall. After I try that I will get back to y'all, though.

AA

I did not mean to reinstall, but to repair installation, that would be the first step, and then treinstall. Thx

That seems to have fixed it! :) Thanks! I repaired from the disk and that worked. But then, I've only used it for ten minutes since, so I'll let you know if the problem comes up again.

AA

Sure, hopefuly it would stay that way!

Well, the problem is back but seems to be totally sporadic. What to do?

AA

Well, after I did that and then opened/closed both Word/Excel once it doesn't seem to have come up. But it was sporadic, so we'll see if MS fixes this. By the way, my brother's copy of Office 97 did the same thing on his windows computer, so maybe it's more of a Windows problem then Office. We'll see what Big Ballmer releases for us. :)

AA

I have the same annoyance and have had it since installing the final version of MSO 2010 in June. I have not tried (and prefer not to try) any interim fixes because I am very careful about breaking something else. All else is working just fine and this is just an annoyance--not a real "problem"