[josh]

Doug,

I have removed KB973904 which you requested and still having the issue. I
cannot open a 97-2003 file in my office 2007. I can though go file, open and
choose recover text from any file and it will open but adds a bunch of
characters. I even tried open office which someone requested might work but
it didn't. I did not have the registry entry.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion

\Applets\Wordpad

I did create it and changed it from 0 to 1 and it would open but with alot
of characters added to make it really non readable. I even tried winword /r
and still no luck. Has there been a fix for this????????????????

"Doug Robbins - Word MVP" wrote:

Remove the security update (MS09-073) that caused the problem.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP, originally posted via msnews.microsoft.com

"InfinitiDC" wrote in message
...
Thanks for the advice.
However, I did not have wordpad in the subdirectory-any other
suggestions?

"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? 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. ;-)

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

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup
so
all may benefit.


.

[Flip[_2_]]

Hello Josh,
Did you try simply going back to a system restore point?
This worked fine for us.
Flip


"Josh" schreef in bericht
...
Doug,

I have removed KB973904 which you requested and still having the issue. I
cannot open a 97-2003 file in my office 2007. I can though go file, open
and
choose recover text from any file and it will open but adds a bunch of
characters. I even tried open office which someone requested might work
but
it didn't. I did not have the registry entry.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion

\Applets\Wordpad

I did create it and changed it from 0 to 1 and it would open but with alot
of characters added to make it really non readable. I even tried winword
/r
and still no luck. Has there been a fix for this????????????????

"Doug Robbins - Word MVP" wrote:

Remove the security update (MS09-073) that caused the problem.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP, originally posted via msnews.microsoft.com

"InfinitiDC" wrote in message
...
Thanks for the advice.
However, I did not have wordpad in the subdirectory-any other
suggestions?

"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?
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. ;-)

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

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the
newsgroup
so
all may benefit.


.

[josh]

"Flip" wrote:

Hello Josh,
Did you try simply going back to a system restore point?
This worked fine for us.
Flip


FLIP,

We cant do a system restore on our domain as its blocked by group policy so
there is no way for us to try that. There must be another way though to get
this working but it seems i have tried everything.

Josh