Word 2007 crashes and acts funny

[Stevebri]

I just upgraded to Vista from XP
I then upgraded from Office 2003 to 2007

I launch Word 2007 and either open a file or type text.

I cannot at this point select text or right mouse click on anything.

I exit Word and get the error that Word has stopped working and it restarts
Word. (This happens even if I type nothing in word but just close it)

Also odd that if I click on the Office button and click Word Options I can
change anything in the Popular "tab" but I cannot select any other items in
this list.

I thought at first it was a corrupt Normal.DOT but I deleted them all and it
still is not working properly

Now for the weird part. If I switch to a different user on the same machine
Word works fine on their installation. (Same install right?)

S

 

[Herb Tyson [MVP]]

Word 2007 uses Normal.dotm (it will use normal.dot if .dotm isn't present
when you open Word, but creates Normal.dotm automatically). Given that you
upgraded, you probably had/have both. So, deleting the .dot file wouldn't
have helped if the .dotm file is present.

Another possibility is that there are corrupted registry entries. Still
another is that there is a corrupted user profile.

I would begin by renaming or deleting BOTH normal.dotm and normal.dot (if
both are present).

If that doesn't work, I would look at renaming or deleting the Data key
(described here, but updating the name to reflect that this is word 12.0:
http://word.mvps.org/FAQs/AppErrors/MissingMenusEtc.htm).

If that doesn't work, then it might be that you'll have to resort to
adopting a new user profile. I've had to do that several times in the past.
It's not fun, but it's sometimes the quickest way around such problems.

 

[Stevebri]

Interesting. When I used the winword.exe /a run command everything worked
fine. But the next time I launched word normally it was still broken. I
then modified the reg key and it works great now. THANKS SO MUCH!!

Steven

 

[Herb Tyson [MVP]]

Winword.exe /a should be viewed as a diagnostic, not a cure. When you run
normally, the problem would still exist--as you discovered. If winword.exe
/a runs okay, then it points the finger of suspicion at several
possibilities, while at the same time exonerating several others. Had /a not
done the job, then we'd suspect a larger problem, possibly corrupted
installation files or a damaged user profile.

Glad to see that things are fixed now!

--
Herb Tyson MS MVP
Author of the Word 2007 Bible
Blog: http://word2007bible.herbtyson.com
Web: http://www.herbtyson.com

 

[Kburke]

I had corrupted registry entries. I followed the instructions on the link
given below and fixed the issue. Thank you!