From: Sesquipedalian Sam on 14 Dec 2009 16:07 On Mon, 14 Dec 2009 14:37:49 -0500, "Jay Freedman" <jay.freedman(a)verizon.net> wrote: >Sesquipedalian Sam wrote: >> On Mon, 14 Dec 2009 11:47:36 -0500, "Jay Freedman" >> <jay.freedman(a)verizon.net> wrote: >> >>> Sesquipedalian Sam wrote: >>>> On Mon, 14 Dec 2009 09:53:10 -0000, "Terry Farrell" >>>> <terryfarrell(a)msn.com> wrote: >>>> >>>>> See >>>>> http://blogs.technet.com/wordonenotesupport/archive/2009/12/10/when-opening-the-word-document-users-are-getting-error-word-cannot-start-the-convertor-mswrd632-wpc-or-cannot-load-word-for-windows-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/AppErrors/ReRegisterWord.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. PS: We have two PCs in the office connected by a P2P LAN. I have a laptop and my admin has a workstation. They have identical software installed and run the same auto-update facility installed and maintained by the company that procides tech support. I just copied one of the documents that fails on my PC to the workstation and opened it in Word there. No error.
From: Bob on 14 Dec 2009 16:45 I am also getting the above error message when I try to run mail merge from full Outlook to word label document for my Christmas cards. Hope we can find a fix before I have to hand address them. Bob --- frmsrcurl: http://msgroups.net/microsoft.public.word.newusers/Word-cannot-start-the-converter-mswrd632.wpc
From: Sesquipedalian Sam on 14 Dec 2009 16:58 On Mon, 14 Dec 2009 13:45:10 -0800, Bob <user(a)msgroups.net/> wrote: > >I am also getting the above error message when I try to run mail merge from full Outlook to word label document for my Christmas cards. Hope we can find a fix before I have to hand address them. >Bob > >--- >frmsrcurl: http://msgroups.net/microsoft.public.word.newusers/Word-cannot-start-the-converter-mswrd632.wpc Several articles mentioned this being a problem with mail merge, which I never use. If I recall correctly, they recommended reinstalling the converter. I know you really didn't want to send cards to all those ghoofy relatices anyway. Now you have a good excuse. ;-)
From: Flip on 15 Dec 2009 02:50 Hello, Removing the patch from the software did it for us sofar, it's KB973904. Just have to await if it comes back with new updates. Flip "Sesquipedalian Sam" <sesquipod(a)nowhere.noway> schreef in bericht news:6qtbi59fsk5q1m4l3pjn4quadco4c8gp3o(a)4ax.com... >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.
From: InfinitiDC on 15 Dec 2009 11:18
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" > > <terryfarrell(a)msn.com> wrote: > > > >> See > >> http://blogs.technet.com/wordonenotesupport/archive/2009/12/10/when-opening-the-word-document-users-are-getting-error-word-cannot-start-the-convertor-mswrd632-wpc-or-cannot-load-word-for-windows-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/AppErrors/ReRegisterWord.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. > > > . > |