Strange thing started happening last week. When you double click a Word doc
either from and email (GroupWise), network drive or local drive it takes
about 10-15 minutes for Word to even appear. During this time, WINWORD.EXE
is not showing in the taskmgr window and the entire computer comes to a
screeching halt (Vostro 1700, 3gb ram). I usually have to logoff and log
back in to Windows.

Last week I had done a repair installation of Office and that fixed the
problem, however today the same issue is back. My temporary workaround is
to open Word first to a blank doc and then open any document from inside
Word. That process experiences no delays and docs open instantly.

Any thoughts as to what is going on? I disabled the one add-in that was
listed (send to Bluetooth).

Could use some help here, thanks.

Tom

Re: 10-15 minutes to open Word 2007 doc by Terry

Terry
Tue May 06 15:34:05 PDT 2008

Try Uninstalling the Bluetooth utility. Bluetooth drivers are notorious from
causing all sorts of conflicts - usually because they have been written by
telephone developers who know nothing about desktop computers. After
uninstalling it, go to Start, Run and type in

winword /r

and press enter. Test again.

--
Terry Farrell - MSWord MVP

"SoxFanInVA" <tjubb@no.spamsalot.hotmail.com> wrote in message
news:u3RtrU8rIHA.2492@TK2MSFTNGP06.phx.gbl...
> Strange thing started happening last week. When you double click a Word
> doc either from and email (GroupWise), network drive or local drive it
> takes about 10-15 minutes for Word to even appear. During this time,
> WINWORD.EXE is not showing in the taskmgr window and the entire computer
> comes to a screeching halt (Vostro 1700, 3gb ram). I usually have to
> logoff and log back in to Windows.
>
> Last week I had done a repair installation of Office and that fixed the
> problem, however today the same issue is back. My temporary workaround is
> to open Word first to a blank doc and then open any document from inside
> Word. That process experiences no delays and docs open instantly.
>
> Any thoughts as to what is going on? I disabled the one add-in that was
> listed (send to Bluetooth).
>
> Could use some help here, thanks.
>
> Tom
>