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 No comments

92 answers

Sort by: Most helpful
  1. Anonymous
    2025-05-21T15:16:49+00:00

    Hi Gabriel I've had that option turned off for a while so that's not the issue. More CPU spiking again today. This really needs to be fixed properly and quicker.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-05-21T14:48:47+00:00

    This past week we had an issue where the Text Predictions feature went missing, Text predictions unexpectedly become unavailable and are missing in Outlook options - Microsoft Support. I'm not sure if that could have exacerbated the issue but that feature is now back available. If you are not using Text Predictions, I would turn it off and that may help minimize the CPU usage.

    To turn off Text Predictions:

    1. Click File > Options > Mail.
    2. Under Compose messages, uncheck Show text predictions while typing.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-05-20T09:14:23+00:00

    Hi Gabriel, I updated to 2503 build 18623.20266 on Thursday last week and it's been better but still had CPU spike on 3 occasions.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-05-01T18:56:05+00:00

    It sounds that the GPU bug will take the same way as the CPU bug: For a very long time over months or even years (as the other CPU bug before from 2021/07 - 2023/03 which produced permanent CPU load while e-mail attachments were opened), nobody will believe it and everybody says "if it really would be like this, millions of users would have complained". As you can see in the current CPU bug case, over months millions did not complain - also because Microsoft's way to work on bug reports quickly discourages everybody because they never give up their thinking that the mistake is always caused by the user and not by MS, so they let the few users who complain do this and that and this again, until everybody gives it up. Except Gabriel in this case, who after months has been a really glorious exception, thank you so much again!

    After all this, I guess the only way out of this repeated coping with really severe bugs in Outlook which are fixed after many months, years or even never, will be Thunderbird or similar competing e-mail clients.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-04-30T22:09:19+00:00

    I only use an external monitor (2.560x1.440), and my integrated display (which I don't use in dock) has the same resolution.

    According to DXDiag, I have DirectX 12, the main driver is dated 20210820, and no problems had been detected.

    I'm quite sure that it's not a question of versions, options etc., because 2405 has not this bug, but later versions have.

    All of my machines are on DirectX 12 as well. The oldest driver I have is from 2024. Please double check there is not something newer. Switch to the Beta Channel and test with the Word fix if that has any affect on the GPU issue. When you are on the Beta Channel you should be able to submit an In App ticket (Help, Contact Support). I would do that and see if the In App support can identify any causes for the GPU spike. Since you already have it I would attach the DXDiag report.

    Was this answer helpful?

    0 comments No comments