Just to note i'm running 2411 build. So this doesn't appear to be unique to the older versions.
High CPU usage when typing a message in Outlook
OS: Win 11 Pro
Office: 2016 Pro
Hi everyone,
CPU activity goes to 16-22% when typing a message in Outlook 2016 and returns to 1 % when typing stops.
Deactivating (all) add-ins and Graphic acceleration did not solve the issue.
Deactivating spell check options did not cure the problem either.
The problem seems to be specific to Win 11 and does not occur on Win 10 OS.
If anyone has any suggestion on how to solve this issue...
PDMC
***moved from Outlook / Windows / Classic Outlook for Windows / For business***
Outlook | Windows | Classic Outlook for Windows | For business
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.
92 answers
Sort by: Most helpful
-
Anonymous
2024-12-09T05:27:12+00:00 -
Anonymous
2024-12-09T08:46:04+00:00 Dear Wage Slave,
Thank you for your feedback confirming that this problem is not an isolated case, although being ignored by Microsoft (just like many other pending issues).
As previously mentioned, the only temporary fix might be to redact the mail in Notepad, and then paste it into Outlook before sending (other solution: get rid of all Microsoft products, including their OS).
Best regards.
-
Anonymous
2024-12-13T16:56:10+00:00 I am not sure if this is your problem or related to it or not, but I've found that the text prediction feature can definitely negatively impact CPU, and I think it gets worse the more email a user has. It can be turned off through GUI or registry and it's worth a shot to measure what your CPU looks like while typing a sentence with it both on and off.
https://www.reddit.com/r/sysadmin/comments/o9pit6/disable_outlook_365_text_predictions_orgwide/
-
Anonymous
2024-12-16T11:26:11+00:00 Thank you, this would have been worth trying it, but I neither get text predictions in Outlook nor is there a setting to didable it.
-
Anonymous
2024-12-17T14:21:12+00:00 It doesn't totally solve the problem either. I'm seeing abnormally high cpu usage from OUTLOOK.EXE with one client using monthly enterprise channel of Office 365 on Windows Server 2016. However another client in the same configuration and channel does not.