Find out what I'm doing, Follow Me :)

Sunday, April 17, 2011

How to fix MS Word File opening Error

Microsoft Word is the power tool for users who have to deal a lot with writing articles, creating reports and proposals and more. Microsoft Word offers lots of flexibility in terms of editing, creating and beautifying a document. But many a time, we encounter minor errors while using Microsoft Word. One of them is the file opening error which happens frequently. The message saying that Microsoft word cannot open the converter and thus preventing a file from opening is very common encounter among Microsoft word users. You can fix the mswrd632 converter issue on Microsoft Word with these simple tricks.

You must have come across the following message a lot of times.

Word cannot start the converter mswrd632

You need to unregister the mswrd632 converter in order to fix this issue. You can do it by either modifying the registry manually or using the fix provided by Microsoft. Before modifying the registry, make sure you have exited all Microsoft office applications. Now from the Run Command(Ctrl+R), type regedit and click on OK to open the registry editor for Windows. Now, locate the following key on the registry editor.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Text Converters\Import\MSWord6.wpc
Now, delete this key from the Edit Menu(Edit>Delete).

On 64 bit version, delete the following key in the registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Shared Tools\Text Converters\Import\MSWord6.wpc

After doing this, Microsoft Word will use its own converters to convert and open the document. You’ll see a dialogue box with File Conversion option, the next time you open the file on Word.

Microsoft also provides a dedicated Fix tool to help you fix this quickly. Download this fix file from Microsoft and Run it. Follow the instructions carefully. But be sure to exit Microsoft Word and other Office Applications before doing this.

Thus, you can easily fix the converter mswrd632 issue by manually editing the registry or using the fix from Microsoft Corporation.

No comments:

Post a Comment