Keyboard shortcuts reassign themselves

Anonymous
2014-02-13T22:00:31+00:00

Word's built-in keyboard shortcuts sometimes reassign themselves.

For example, if I edit a table, such as copying and pasting cells, and return to working on the rest of the document, command-c no longer becomes available, command-v turns into "cut" and command-] becomes paste. Those functions listed in the pulldown menus no longer include those keyboard shortcuts. However, if I use the contextual menu, the cut/copy/paste functions work (and also the contextual menu lists the no longer functioning command-c/x/v shortcuts). Similar things seem to happen after I import a photo into the file.

It doesn't matter if I am working in a .doc or .docx document.

If I quit and restart the program, everything goes back to normal until I edit a table again.

This has been happening since I installed Word 2011, on my MacBook Pro and Air, and on various versions of OSX (now running 10.9.1).

Does this happen to anyone else out there?

Madeline

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

79 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-07-08T14:49:28+00:00

    Well, I'm using 14.4.3--the latest, greatest.  And the keystroke re-assignment just happened yesterday--again.

    Again, the solution is to quit and re-launch.

    I do have the "Start Dictation" item in my Edit menu.  Not sure why its existence would affect the keystroke assignments, but there it is.

    I have turned off Dictation in the OS X preferences.  Relaunched Word and the menu item is still there!  I could not find it in Word's menu items (I suppose because it's added by the system).  I was hoping to move it to a different menu and see whether the problem traveled with it.

    I suppose I'll have to restart the Mac for it to vanish…  I'll report back if that works--and if it stops the problem!

    Oh, and appreciate everyone's work on this!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-07-08T10:11:27+00:00

    Should anyone want to chime in at MS, our case number is 1253364983.

    I'v just started using the 14.4.3 update now and, for limited usage-time: so far so good.

    Forgive my cynicism, but I keep MS and OSX updated (both check for updates automatically weekly) and I can't believe that this latest MS update -- which is being downloaded as I type -- will fix this.

    So how do I go about chiming in on the case number? Thanks for launching it!

    Cheers,

    Madeline

    Beats me. I'm not sure I know how to re-contact them.

    Jim

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-07-08T02:47:47+00:00

    Should anyone want to chime in at MS, our case number is 1253364983.

    I'v just started using the 14.4.3 update now and, for limited usage-time: so far so good.

    Forgive my cynicism, but I keep MS and OSX updated (both check for updates automatically weekly) and I can't believe that this latest MS update -- which is being downloaded as I type -- will fix this.

    So how do I go about chiming in on the case number? Thanks for launching it!

    Cheers,

    Madeline

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-07-08T02:09:46+00:00

    Should anyone want to chime in at MS, our case number is 1253364983.

    I'v just started using the 14.4.3 update now and, for limited usage-time: so far so good.

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more