On Mon, 14 Dec 2009 14:37:49 -0500, "Jay Freedman"
wrote:

Sesquipedalian Sam wrote:
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.


OK, maybe I'm wrong about the association -- but if so, I don't understand
how the WordPad converter could get involved in the process. I still think
reregistering Word is worth a try; it's quick, and at worst it won't have
any effect.

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?


Yes, close all open documents and shut down Word. Then run the command from
the Start Run box or from a command prompt window.

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

It can't hurt, and it might help.

PS: We have two PCs in the office connected by a P2P LAN. I have a
laptop and my admin has a workstation. They have identical software
installed and run the same auto-update facility installed and
maintained by the company that procides tech support.

I just copied one of the documents that fails on my PC to the
workstation and opened it in Word there. No error.