A family of Microsoft word processing software products for creating web, email, and print documents.
I confirm quitting Dropbox solves that ridiculous M$oft lag for me.
But Bill Gates just put 1 billion in SoftBank so all bugs will be gone.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
It is impossible to edit some documents because of VERY slow, jerky, jumpy, laggy, erratic, stuttering cursor movement (horizontal worse than vertical). I have been forced to go back to using Word 2011. I am a professional novelist and cannot practice my trade with Word 2016!! This is very disappointing.
As a novelist I work with large word count simply formatted documents with a file size of less than 1M. I have not experimented to find a cut off point with regard to word count but documents in the 100K word size or more (less than 1M file size) exhibit this slow, jerky, laggy cursor movement problem. Small documents in the 5K word range do not have this problem on any of my notebooks.
It can take 10 seconds or more to move the cursor from the right to left side of the page (or vice-versa). This slow erratic cursor movement is especially troubling when trying to select a few words (highlighting them) for editing. It is very frustrating.
I have experimented and found that brand new documents in 2016 file format exhibit this problem. I have created documents with zero text formatting and they have this problem. I removed all formatting in these test documents by copying and pasting ASCII text into the newly created 2016 format doc from original Word 2011 documents.
I have replicated this same problem on three different macbook computers all with SSD and max ram. None of these computers are running with more than 5% CPU utilization (running nothing else except Word 2016). All of these notebook computers edit the same files just fine using Word 2011.
Track changes is not turned on, nor is any other unusual "feature" or function. This problem occurs in all display modes: draft, layout, etc.
**All these notebooks are running the latest version of Yosemite and all with 100% up to date software.
**This is a fatal mission-critical problem for me which has forced me to revert back to using Word 2011. Again, this is very disappointing.**I have been a Word user for something over 25 years (started on MS/PC DOS).
Similar / same problems here:
A family of Microsoft word processing software products for creating web, email, and print documents.
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.
I confirm quitting Dropbox solves that ridiculous M$oft lag for me.
But Bill Gates just put 1 billion in SoftBank so all bugs will be gone.
It's now Nov 16. I was writing one of my board exams, and the problem was so bad that I had to go back to my old laptop with a failing hard drive. Clearly, this is not a priority for MS. Maybe it's finally time to switch to Nota Bene.
Another update...
Installed Word 15.16.0 (as part of the latest updates) and the sluggish UI problems are still there... as bad as ever. This is with NO OTHER SOFTWARE running on a 2015 MacBook Pro Retina with 16GB of RAM and 1TB of SSD hard drive running El Capitan 10.11.1.
I've continued to experiment and have found that I can recreate the problem with a small document (8 pages, about 790kB). Going to the next page takes 2-5 seconds and scrolling from page 1 to 8 (or 8 to 1) causes the CPU utilization to jump to 100% for a few seconds.
Just now used the "frowny face" to offer to send that document to Microsoft. We'll see *IF* they are REALLY serious about fixing this problem.
Meanwhile, I'm sticking with Word 2011.
Exactly same bug exists on Windows, question's "Applies to" section should be edited
Hi all,
I think I found the problem that is causing Word 2016 to be sluggish. It seems to be related to its grammar and spelling checker.
I've recently published this fix. I hope this can help you too while Microsoft releases a "real fix".
Thanks!
Check my fix here: