Error message: Word cannot start the converter mswrd632.wpc. How can I correct?

Anonymous
2010-01-28T15:50:11+00:00

This error shows up when I try to open certain Word documents using the .doc extension.

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Ramesh 181.8K Reputation points Volunteer Moderator
2010-01-28T17:38:25+00:00

Hi LMatth,

Look at the "Known Issues" section of this Microsoft article.

http://support.microsoft.com/kb/973904

<excerpt>

Let me fix it myself To unregister the mswrd632 converter yourself, edit the registry as follows:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Text Converters\Import\MSWord6.wpc 3. On the Edit menu, click Delete. 4. Click Yes. 5. Exit Registry Editor.

This change will effectively unregister the converter and disable it for third-party applications and for Microsoft Office. Microsoft Office will use its own text converters to open these kinds of files.

</excerpt>

©2010 Microsoft Corporation.

Ramesh Srinivasan, Microsoft MVP [Windows Desktop Experience]

Was this answer helpful?

40+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2012-04-13T21:34:05+00:00

Solution to this is available here:  http://support.microsoft.com/kb/973904

Was this answer helpful?

9 people found this answer helpful.
0 comments

52 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2011-02-04T09:30:24+00:00

    I use Word 2003, and I occasionally encounter this error message, usually with a file from Word 2004 (not Word 2007 and Word 2010).

    Normally: not a problem. That is, since I have an up-to-date converter installed, Word 2003 recognizes the version, cautions me that I will not be able to use the features of the more recent version, and then without intervention converts the file so that I can edit as usual in Word 2003. Then, when I save, the converter saves in the original file format.

    When I encounter the problem, this work-around has worked consistently. In Word 2003:

    >Tools

    >Options

    >General tab

    >check: "Confirm conversion at open."

    Then, Word 2003 tries to open the problem file, stops, and asks me if I want to convert. After I assent, Word 2003 converts and opens the file. I can then edit as usual. When I save the file, the converter saves in the original format.

    Then, to avoid the additional step that is usually not necessary, I undo the change:

    >Tools

    >Options

    >General tab.

    >uncheck "Confirm conversion at open."

    A bit cumbersome, but it avoids the registry edit and has worked consistently over several years.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-01-24T12:17:36+00:00

    Well, I have taken all the advice above, without success - and realised that, as ever, I could have retyped the whole document in less time than I have wasted naively thinking I would get useful help from Microsoft. I do appreciate all the entries here and thank you. However, I am again reminded of the old, old joke about the airline pilot struggling to find Seattle Airport in thick fog... I am sure you are all familiar with it!

    Thanks anyway.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-11-30T15:38:25+00:00

    Hi Paul

    One of my users faces this issue regularly with documents that travel between two offices.  Our office is running Office 2007, and we believe the client is too. 

    While troubleshooting, I tried to recreate your scenario (it's quite possible our client is using this method), but I couldn't generate the mswrd632.wpc message.  Can you confirm the steps to reproduce?

    • create a .docx file
    • save in compatibility mode with .doc extension
    • save as .docx and check "Maintain Compatibility"
    • close the file
    • reopen
    • mswrd632.wpc message appears

    As I say, I can't reproduce the issue this way, and wondered if I'm missing something.

    The only other likely mechanism I can find to generate the message is to artificially change the file extension to .doc on the client's side, either manually or programatically as part of some document management or metadata automation.  

    However our user is quite clear that he's receiving the files in .docx format (so you can see how your post was of interest to us).

    Thanks

    Was this answer helpful?

    0 comments