Odd cursor behavior in Word 2013 and 2007

Layback Bear said:

A suggestion.
Use msconfig/Startup and make sure that the Office products are not checked.

What this will do is make sure neither Office will startup at boot and run in the background when you are not using them.
They will work when you choose and tick on the one you want to use.

Okay, so I did this, and I have a backhanded solution, so thank you! After unchecking the office products startups, I rebooted. I immediately opened Word and had no active cursor behavior by opening many documents. I then started a new document and tried to print. As soon as I invoked the printer I had the active cursor behavior, and then I tried opening other documents, and it wouldn't stop. I closed Word, exited the printer (which boots automatically) and didn't have the same behavior, was in fact normal cursor.

So while not the exact solution, it brought me to know it was conflicting with my printer....so now to search for the driver I need for my Canon MX882 - don't laugh, old printers need love too! THanks for the help Layback, I appreciate it.

LafnSu

Layback Bear said:

Your welcome.

I don't like buying new printers either. You never know if the new one is going to work better that the old one.

LOL...I hear that! Besides I'm cheap and won't replace until it absolutely dies....it's 4,000 some pages past life expectancy now...slow but steady, sort of like me

Going back to the original question, I am having the same problem with word 2010. It happens with all documents and sometimes in Outlook. I have checked talk manager to see what else is running, but that provided no answers. Of course there are many things running in the background, but which might be causing the problem I have no idea.

kmwandel said:

Going back to the original question, I am having the same problem with word 2010. It happens with all documents and sometimes in Outlook. I have checked talk manager to see what else is running, but that provided no answers. Of course there are many things running in the background, but which might be causing the problem I have no idea.

It may well be a conflict with printer, keyboard, mouse...mine was printer, but I'm thinking any device that you use with the program would be the first suspects.