View Single Post
  #8   Report Post  
Posted to microsoft.public.word.newusers
Sesquipedalian Sam Sesquipedalian Sam is offline
external usenet poster
 
Posts: 126
Default Word cannot start the converter mswrd632.wpc

On Mon, 14 Dec 2009 11:47:36 -0500, "Jay Freedman"
wrote:

Sesquipedalian Sam wrote:
On Mon, 14 Dec 2009 09:53:10 -0000, "Terry Farrell"
wrote:

See
http://blogs.technet.com/wordonenote...6-0-files.aspx


This article asks me to make a Registry change. I'd really rather not
do that. Is there any other fix?

This article says it may be caused by a security update. I suggest
MSFT needs to send out another update to fix the update. And then
actually do a little testing BEFORE they ship the updates. This is the
second time in a year or so that an update broke something that I know
of.

The error only seems to happen when I open a .doc document. I'm
running Office 2007.


Sam, did you read the KnowledgeBase article linked from that page?


Nope.

This
isn't an error, it's deliberate; Microsoft wants to prevent you from using
the old WordPad converter because it isn't secure. The registry change is
intended for administrators who consider using the converter more important
than closing the security hole, at least temporarily. Also, because it's a
deliberate change, there is never going to be "another fix" for the security
update.

But your problem is a bit different from what the articles describe. You're
trying to open a .doc file in Word 2007, which should have nothing to do
with WordPad or the old converter. What's happened is that Windows has
associated the .doc extension with WordPad instead of Word. If the security
patch hadn't been applied, the document would have opened in WordPad (which
can also read the .doc format), and you would have been complaining about
that instead. ;-)


I pretty sure the .doc extension is associated with Word. If I
double-click a .doc file, it opens in Word, always has. I just tested
it again.

Run the winword /r command as described in
http://www.word.mvps.org/FAQs/AppErr...gisterWord.htm and see if that
fixes the problem.


Do I need to close Word (all open docs) first?

Do you still think I need to do this even though .doc files are
already associated with Word?