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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-04-28T15:45:27+00:00

    Dear Gabriel,

    thank you very much, so I will re-enable updates for SemiAnnual Channel.

    I can see the GPU spike when I switch from mailbox to calendar in classic Outlook - then suddenly GPU load rises to and stays between 30-60%, and it does not drop afterwards, but stays high until I quit and restart Outlook. But this happens not every time, only quite often. My graphics driver is up to date.

    Was this answer helpful?

    0 comments
  2. 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

  3. Anonymous
    2025-04-27T14:35:17+00:00

    OK, I will check and report about the GPU bug again later after the CPU bug will be fixed.

    How long should it take until the CPU bug, which you mentioned now to occur also in SemiAnnual Enterprise Channel, will also be fixed in SemiAnnual? So would it be an alternative to disable updates using SemiAnnual Channel in time before the latest update (which should bring the CPU bug also to SemiAnnual), because here at my side I don't have it in SemiAnnual Channel up to now and I'd prefer to wait maybe 6-8 weeks until it will also be fixed in SemiAnnual?

    Because after this "special" experience with the CPU bug which was not fixed for such a long time over many months, I would generally prefer to stay in SemiAnnual Enterprise Channel for the future.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-04-25T14:20:26+00:00

    The only bug I am currently tracking is the original performance issue that caused the CPU to spike. If there is another bug affecting GPU it will help us to differentiate it after you can test with the upcoming fix. Please put a machine with the GPU issue on the Beta Channel so you can test it with the CPU fix next week when that build becomes available. If you still repro the GPU spike after that fix, please submit an In App ticket via Help, Contact Support. Also make sure you have the latest graphics drivers installed. I updated the Known Issue yesterday with the fixed build and status, CPU spikes when typing in classic Outlook for Windows - Microsoft Support.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-04-25T04:18:01+00:00

    The Word team implemented a fix and it will go to the Beta Channel with build 18822.15000. That build was just created so it will probably go out to Beta late next week at the earliest. It will go to Current Channel Preview and CC starting with build 18827.20000. CC Preview will get the fixed build in about two weeks. CC will get the build in late May. It's possible the Word Team will backport the fix after it has time in the Insider Channels and after it goes to CC.

    I'll update the Known Issue with the fix status as soon as I get a chance.

    Dear Gabriel,

    thanks a lot - but does your message concnern the original CPU bug of this thread, or the GPU bug I decribed again yesterday?

    Was this answer helpful?

    0 comments