This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi Guys, just to let you know that the final version of Office does not work properly and have 70-100% CPU issue as reported on numerous posts here. In my case, it's the WORD with which I have the issue with and no remedies posted here help. Please provide the fix as soon as possible, because this bug renders the new suite useless...
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.
Hi,
To resolve this issue, is your installation of Office for Mac fully updated?
In any Office application go to the Help menu and choose Check for Updates to launch the Auto Update app. Let AutoUpdate install the updates and then restart your Mac.
Update us with results for further assistance.
Hi everyone,
This issue is now fixed. For more information about how to obtain the fix, see https://support.microsoft.com/en-us/kb/3165798.
We very much appreciate your patience!
Best,
-Erik
I'm having the same issue on the same software versions.
It's a large document ~130 pages with a lot of tables. Typing and scrolling are both laggy and I'm frequently getting SBBOD when I change a style (e.g. set a highlighted section of text to bold takes ~5 secs).
CPU usage is <1% when Word is in the background, but bring it to the front and CPU is >50%. It jumps to 80-110% when typing or making changes.
I have the latest Word for Windows in a VM with a fraction of the resources allocated and am not seeing the same issues with this document.
Changing to Draft view has sped up scrolling and improved typing lag somewhat, but the high CPU usage remains.
UPDATE: updating to the latest fast preview (15.31 161227) has fixed the lagginess, but still experiencing 40-50% CPU when typing. At least it's now usable.
Update 15.22 due in May hopefully will correct the problem.
Oh - good grief - "maybe this release will correct the problem"!!!!
Again!!!!
This is a bug. Just find it, fix it and tell us when it is fixed. Instead of this lame request to "try it now, maybe it is fixed" which we get with each new version!
This is a user-to-user forum. Once in a while Microsoft employees visit, but usually it's just fellow users like you and me. Neither you nor I have the ability to fix the problem.
As has already been mentioned, we DO have the ability to let Microsoft know about problems. John got the ball rolling. Perhaps you helped by also reporting the problem using the Smile button (maybe not, you didn't say).
Microsoft doesn't usually report back as to when they will fix particular bugs. For years they simply never told anyone anything about upcoming bug fixes. This policy has been easing lately.
MVPs know for sure that Microsoft is aware of the problem. We see it reported daily here in the forum. Our experience is that Microsoft does generally fix problems of this sort quickly. Therefore you see the advice to install the next update as soon as it comes out. If you want to be the first, click the check box in AutoUpdate to join the "Insider" program (Help > Check for Updates).
What MVPs can not do is accurately predict the future. For that you have to go to fortune tellers and others who have not yet been picked up by the bunko squad. We can't tell you with absolute certainty the problem will be fixed in the next update. We can tell you that we think it most likely will be, and that's why we urge you to get the update when it comes out.
I sense that you think I work for Microsoft... I don't. I volunteer on this forum. The knowledge I share is my own, though I do have connections with certain people on the product team.
FWIW - I don't give lame excuses, never have and never well. I share what I can and sometimes what is known can't be explicitly stated. All one can hope is that those concerned will read between the lines.
Have a good day... sorry to have upset you.