A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Word » New Users
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Word cannot start the converter mswrd632.wpc



 
 
Thread Tools Display Modes
  #21  
Old December 16th, 2009, 09:47 AM posted to microsoft.public.word.newusers
Graham Mayor
external usenet poster
 
Posts: 18,297
Default Word cannot start the converter mswrd632.wpc

You could add it and then create the described entry.
Have you tried simply uninstalling the 973904 update? This will also put
back the older mswrd632.wpc file that the update replaced.

--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org



"Derek" / wrote in message
...
I tried to edit the registry as described under 973904 but there is not a
\wordpad directory under applets.

---
frmsrcurl:
http://msgroups.net/microsoft.public...r-mswrd632.wpc



  #22  
Old December 16th, 2009, 11:23 AM posted to microsoft.public.word.newusers
Doug Robbins - Word MVP
external usenet poster
 
Posts: 8,239
Default Word cannot start the converter mswrd632.wpc

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.


.

  #23  
Old December 16th, 2009, 01:29 PM posted to microsoft.public.word.newusers
Terry Farrell
external usenet poster
 
Posts: 3,004
Default Word cannot start the converter mswrd632.wpc

That was the very first help I sent them too. So surely they have followed
and uninstalled it already?

Terry

"Doug Robbins - Word MVP" wrote in message
...
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.


.

  #24  
Old December 16th, 2009, 03:15 PM posted to microsoft.public.word.newusers
Derek[_9_]
external usenet poster
 
Posts: 3
Default Word cannot start the converter mswrd632.wpc

Thanks, Graham. I added the wordpad directory as you suggested and the entry as described in 973904. I can now mailmerge correctly from Outlook.

---
frmsrcurl: http://msgroups.net/microsoft.public...r-mswrd632.wpc
  #25  
Old December 16th, 2009, 04:46 PM posted to microsoft.public.word.newusers
Josh
external usenet poster
 
Posts: 236
Default Word cannot start the converter mswrd632.wpc

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.


.

  #26  
Old December 16th, 2009, 05:14 PM posted to microsoft.public.word.newusers
Josh
external usenet poster
 
Posts: 236
Default Word cannot start the converter mswrd632.wpc



"Danny" wrote:

Thanks for the link - I'm having the same problem. I tried to make the registry change described in the article, but did not have Wordpad at HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion
\Applets\Wordpad

Have you seen anything else that helped with this problem?

---
frmsrcurl: http://msgroups.net/microsoft.public...r-mswrd632.wpc
.



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????????????????

  #27  
Old December 16th, 2009, 06:21 PM posted to microsoft.public.word.newusers
M McAllister
external usenet poster
 
Posts: 1
Default Word cannot start the converter mswrd632.wpc

Don't believe everything you read. Wordpad was/is not my default for .doc
files. Word 2007 is.

This error came up for me in Microsoft Accounting when I tried to print to
my Word Template for my invoices.

I applied this fix by modifying the registry........I added the Wordpad key
under applets and then added the AllowConversion and now all is well.
  #28  
Old December 16th, 2009, 07:48 PM posted to microsoft.public.word.newusers
Grup
external usenet poster
 
Posts: 1
Default Word cannot start the converter mswrd632.wpc

I had the similar problem, with a 3rd party software program called PPM that
uses Word. I re-installed Word and problem solved. The patch 973904 is
still on the computer.
--
Rich


"Josh" wrote:



"Danny" wrote:

Thanks for the link - I'm having the same problem. I tried to make the registry change described in the article, but did not have Wordpad at HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion
\Applets\Wordpad

Have you seen anything else that helped with this problem?

---
frmsrcurl: http://msgroups.net/microsoft.public...r-mswrd632.wpc
.



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????????????????

  #29  
Old December 17th, 2009, 08:43 AM posted to microsoft.public.word.newusers
Flip
external usenet poster
 
Posts: 15
Default Word cannot start the converter mswrd632.wpc

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.


.



  #30  
Old December 17th, 2009, 12:56 PM posted to microsoft.public.word.newusers
Josh
external usenet poster
 
Posts: 236
Default Word cannot start the converter mswrd632.wpc



"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
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 01:30 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.