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-06-27T00:49:37+00:00

    I'm not certain this applies but I have a problem with graphics driving up CPU usage as well. Both Photoshop elements and Google Earth (in street view mode) drive the CPU up and make the CPU fan howl way too loud for comfort. I have a ten year old Laptop that handles Google earth without all of the fireworks. My PC has a Intel Core i7 14700F CPU and an NVIDIA T1000 8GB GPU. I don't think these programs should be putting such a load on the CPU that the cooling fan runs at full speed. I have my MS Office Outlook locked on version 2405 per Gabriel's message of 3/12/25. That at least keeps Outlook quiet.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-06-20T08:28:11+00:00

    Unfortunately, the GPU (not CPU) bug also appears on other machines with other processors.

    Before it really appears, it's already striking that GPU load rises massively when you just move the mouse over Outlook's folder list. That's no complicated graphical work, really not.

    Microsoft agents here seem not to be able to reproduce the bug because they use virtual machines without GPU. Maybe you should then reproduce the GPU bug on real machines instead, because most customers also use real machines with GPUs, at least integrated GPUs?

    It cannot be true that also this bug will be neglected again!

    Was this answer helpful?

    0 comments