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
  #1  
Old December 14th, 2009, 09:39 AM posted to microsoft.public.word.newusers
Sesquipedalian Sam
external usenet poster
 
Posts: 131
Default Word cannot start the converter mswrd632.wpc

A couple of days ago, I started getting this error message

Word cannot start the converter mswrd632.wpc

Can anyone tell me what this is?

Sometimes it will pop up twice, sometimes 3 times.

I did a search on this phrase and found articles on Lotus Notes and
Mail Merge. I have never used Notes. I have never used Mail Merge on
this PC.

I'm running Office 2007 on Win XP. I believe I have all the latest
updates.
  #2  
Old December 14th, 2009, 10:53 AM posted to microsoft.public.word.newusers
Terry Farrell
external usenet poster
 
Posts: 3,004
Default Word cannot start the converter mswrd632.wpc

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

--
Terry Farrell - MSWord MVP

"Sesquipedalian Sam" wrote in message
...
A couple of days ago, I started getting this error message

Word cannot start the converter mswrd632.wpc

Can anyone tell me what this is?

Sometimes it will pop up twice, sometimes 3 times.

I did a search on this phrase and found articles on Lotus Notes and
Mail Merge. I have never used Notes. I have never used Mail Merge on
this PC.

I'm running Office 2007 on Win XP. I believe I have all the latest
updates.


  #3  
Old December 14th, 2009, 03:39 PM posted to microsoft.public.word.newusers
Danny[_10_]
external usenet poster
 
Posts: 1
Default Word cannot start the converter mswrd632.wpc

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
  #4  
Old December 14th, 2009, 04:38 PM posted to microsoft.public.word.newusers
Matthew[_14_]
external usenet poster
 
Posts: 1
Default Word cannot start the converter mswrd632.wpc

The cause of this error, for myself, has had nothing to do with Wordpad. When opening an Office '07 file in Office '03, with the compatibility pack installed on the system, this error is cropping up. The '07 files would open fine up to a couple days ago, so all the right software is on the machine.

---
frmsrcurl: http://msgroups.net/microsoft.public...r-mswrd632.wpc
  #5  
Old December 14th, 2009, 05:24 PM posted to microsoft.public.word.newusers
Sesquipedalian Sam
external usenet poster
 
Posts: 131
Default Word cannot start the converter mswrd632.wpc

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.
  #6  
Old December 14th, 2009, 05:47 PM posted to microsoft.public.word.newusers
Jay Freedman
external usenet poster
 
Posts: 9,488
Default Word cannot start the converter mswrd632.wpc

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.


  #7  
Old December 14th, 2009, 06:41 PM posted to microsoft.public.word.newusers
Sesquipedalian Sam
external usenet poster
 
Posts: 131
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?
  #8  
Old December 14th, 2009, 06:45 PM posted to microsoft.public.word.newusers
Sesquipedalian Sam
external usenet poster
 
Posts: 131
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? 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.


PS: If this is "deliberate", then the left hand doesn't know what
right hand is doing. When the error pops up, there's a help button,
which says nothing about security or Notepad or anything else useful:

This message can appear if:

* The converter was not properly registered.

* The converter was inadvertently deleted without removing the
registry information.

* The converter support files are corrupt.

* The converter installation was removed and the uninstall tool did
not finish clearing the registry settings.

* The hard disk is damaged where the converter files were stored.

Usually, reinstalling the converter will overcome this problem. If the
converter reports that it is already installed, first uninstall it so
that the setup program can remove the files and registry settings.

If removing and reinstalling the converter is not successful, there
may be a problem with a resource on the computer (for example, an
executable file that is needed to properly register the converters on
the computer has failed or stopped running). In this case, it is best
to turn off the computer and start over.



I particularly like the last suggestion. I would only change it to
"turn the computer off and throw it out the window".
  #9  
Old December 14th, 2009, 08:37 PM posted to microsoft.public.word.newusers
Jay Freedman
external usenet poster
 
Posts: 9,488
Default Word cannot start the converter mswrd632.wpc

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.


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


  #10  
Old December 14th, 2009, 09:52 PM posted to microsoft.public.word.newusers
Sesquipedalian Sam
external usenet poster
 
Posts: 131
Default Word cannot start the converter mswrd632.wpc

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.


OK. I ran "winword /r" from the DOS box. It took about 30 seconds to
do something. I then tried opening a .doc document. The first 2 I
tried opened without any problems. The third one got the same error.

It didn't happen every time before. I thought it was intermittent, but
apparently it is just certain documents. I now have 2-3 that do not
get the error and 2-3 that do. That is consistent.
 




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 12:33 AM.


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