Mouse doesn't work on Word after Vista update
Vista updated overnight and now my mouse (external or mouse pad)
doesn't work on Word. I can close the window with the mouse, but it
doesn't even show in the document itself. When I close the window, I
get a message that Word keeps crashing, but Microsoft doesn't come up
with a fix. It suggested I run a Windows diagnostic program, which
turned up no problems. Any suggestions? I'm a little hampered since
I'm composing this from work on a different machine.
Re: Mouse doesn't work on Word after Vista update
Hi there,
You probably took in a driver from Windows Update which is not a good idea.
Drivers if they are REALLY needed to be updated because the hardware is not
working well should only be taken from the manufacturers website.
You can try rolling back on the driver of the hardware that has the problem
or use system restore in safe mode and restore to a date before the problem
occured.
Good Luck and best regards
Mouse stops working in Word 2007 on Vista
The exact same thing occurs for me, and I have not taken any mouse driver updates. There are none to roll back to.
When I first open a word doc, everything is fine. Once I switch to another app, and then return to Word, the document area of the Word application handles no mouse events. The ribbon and menus function just fine, just the document area is 'dead'.
I sure hope MS remedies this soon as Word is pretty much useless once this occurs.
Re: Mouse doesn't work on Word after Vista update
same thing "exactly" happened to me as well - no drivers were taken from
the MS Update... did anyone solve this issue?
btw, tried to uninstall Word and then reinstall it - didn't solve the problem
appreciate it if anyone could drop a word here
thanks,
pro
Just happened to me as well!
I just had this same experience, yet I don't see a word about it on Microsoft's forums. I don't really want to muck around in the registry. What's going on?
Re: Mouse doesn't work on Word after Vista update
Yep - I have the same issue as of about 3 days ago. I had this problem 1 year ago and an update fixed it. I can't believe it's back. Can someone explain the regedit fix or an alternative fix? Thanks much!