High CPU usage when typing a message in Outlook

Anonymous
2024-11-06T10:00:58+00:00

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.

0 comments

92 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2025-04-21T15:40:51+00:00

    This issue will repro in the retail SKUs. It's not an issue that everyone will notice though. You can check if it's affecting you by opening Task Manager and open an email side by side and compare as you type. If you find it affecting your work, you can switch the retail SKU to Semi Annual channel using the registry key workaround in the Known Issue, CPU spikes when typing in classic Outlook for Windows - Microsoft Support.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-04-19T22:54:20+00:00

    Does this issue also occur in Classic Outlook from the Office Pro Plus 2024 Retail version?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-04-14T20:12:21+00:00

    Hi all,

    I posted a Known Issue article to formally track it, CPU spikes when typing in classic Outlook for Windows - Microsoft Support. The Outlook Team is currently investigating. I'll post back when I know more.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2025-04-14T04:53:02+00:00

    It looks good and also with version 2408 (but only in Semi-Annual Channel) I also did not experience the high CPU load while typing an e-mail in Outlook again. So this should be the more safe workaround, not stopping the security fixes at version 2405 like with the rollback workaround. Thank you very much, Gabriel!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-04-12T14:21:10+00:00

    Dear Gabriel, dear all,

    today I finally successfully changed to Semi-Annual Channel ("Semi-Annual Enterprise Channel") by using ODT (Microsoft online deployment tool) as explained here.

    But what's important, to make the update to the new Channel work, you also have to revert the rollback if done by ODT, again by using ODT: https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841

    Therefore, you use an empty TargetVersion in the XML file. If you don't, the update version is still limited to 2405 and the update to SemiAnnual Channel stops with an error message. But if you reset the TargetVersion, you can start the update process in any Office 365 app under File -> Office Account -> Update Options.

    Now my build is 2408 Build 17928.20512 and I hope that you are right and also this does not have the CPU spikes when typing an e-mail in Outlook. I will check it from today on and will let you know here.

    Was this answer helpful?

    0 comments