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: Oldest
  1. Anonymous
    2025-04-29T21:55:08+00:00

    So far, I cannot cause the GPU to spike. I tested switching mail to calendar and otherwise. Does this happen on the primary monitor or is it secondary or does it matter?

    In the past when we looked into graphics issues engineers would get a DXDiag report, Which version of DirectX is on your PC? - Microsoft Support. This will show you the driver date which could help indicate if the driver is old and needs to be updated.

    Another thing to test if it would help is the option File, Options, General, User interface options, Office support for high definition displays - Microsoft Support. Test with best appearance and optimize for compatibility.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-04-30T05:35:13+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.

    Was this answer helpful?

    0 comments No comments
  3. 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

  4. Anonymous
    2025-04-30T21:56:24+00:00

    Hi all,

    The CPU spike fix is now available in the Beta Channel (Version 2505 Build 18827.20006). If you are able to switch to the Beta Channel to test, please do. The Word Team will backport the fix to the other channels, and I will post back with those specifics once I get them and will update the Known Issue as well, CPU spikes when typing in classic Outlook for Windows - Microsoft Support.

    Simplest steps to switch to the Beta Channel:

    Use a registry key to Beta Channel. For more information, go to Use a registry command to install Microsoft 365 Insider on Windows device.

    1. Open a Command Prompt window with Run as administrator for Administrator context.
    2. Paste the command below and press Enter:

    reg add HKLM\Software\Policies\Microsoft\office\16.0\common\officeupdate /v updatebranch /t REG_SZ /d BetaChannel 3. After you add the registry key, select FileOffice Account > Update Options, then Update Now to initiate the switch to Beta Channel.

    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