Microsoft warns of Outlook Classic bug that can crank CPU use up to 50% when typing
The company recommends switching update channels as a band-aid solution.

Microsoft has confirmed a bug in Outlook Classic, where users are experiencing CPU usage spikes, as high as 50%, when simply typing in the application. Notably, reports of this incident can be traced back to November last year, and even now, users have been asked to switch to the Microsoft 365 Apps update channel as a temporary workaround.
After around six months since the first sighting, Microsoft is finally addressing an issue in Outlook (Classic), which led to increased CPU usage, visible slowdowns, and even freezes whenever you'd sit down to compose an email or type a message. Microsoft quotes a figure ranging from a 30-50% hit to the CPU utilization, and that's sure to be noticeable, especially on aging hardware.
The developer team was able to reproduce this bug on updating to Microsoft 365 Apps Version 2406 Build 17726.20126+, which was released in June 2024, on the Current, Monthly Enterprise, and Insider Channels. As of writing, a concrete solution is not available, so users have been recommended to move to the Semi-Annual Channel release, where this issue has not been observed.
If you're running an organization with several devices, Microsoft offers a detailed guide for migrating your update channel with options like Group Policies, the Office Deployment Tool, Microsoft Configuration Manager, and Intune, just to name a few. For home users, a simpler way to achieve the same result is by just tweaking the registry as follows:
- Open a Command Prompt (CMD) window with admin privileges.
- Paste the following command and hit Enter: "reg add HKLM\Software\Policies\Microsoft\office\16.0\common\officeupdate /v updatebranch /t REG_SZ /d SemiAnnual"
- In Outlook, navigate to File > Office Account > Update Options and select "Update Now" to switch to the Semi Annual Channel.
Affected users went through several troubleshooting hoops, like turning off graphics acceleration, disabling the spell-check utility, along with add-ins, but to no avail. It got so bad that a user with a beefy i9-14900HX reported CPU temperatures breaching 95 degrees Celsius just by having the 'New Message' window open, which is used to compose emails.
As the problem is still under investigation by the Outlook team, this is no more than a stopgap solution. The nature of this bug seems to be tied to how the software handles text fields, but it's quite puzzling how such an obvious issue slipped past the developers in the first place.
Stay On the Cutting Edge: Get the Tom's Hardware Newsletter
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.

Hassam Nasir is a die-hard hardware enthusiast with years of experience as a tech editor and writer, focusing on detailed CPU comparisons and general hardware news. When he’s not working, you’ll find him bending tubes for his ever-evolving custom water-loop gaming rig or benchmarking the latest CPUs and GPUs just for fun.
-
Notton :rolleyes:Reply
If only outlook (new) didn't randomly revert to outlook (classic) and vice versa with every other borked Win11 24H2 update.
What a FSS.
:rolleyes::rolleyes::rolleyes::rolleyes::rolleyes::rolleyes::rolleyes: -
Alvar "Miles" Udell Surprised they bothered to fix it instead of saying "Move to the "New Outlook""...Reply -
ohio_buckeye Alvar Miles Udell said:Surprised they bothered to fix it instead of saying "Move to the "New Outlook""...
We use outlook quite a bit at work and the new version imo has some gaping holes. For one the ability to read a pst file. Also limitations with public folders. I’ve also seen the new one when someone wanted to download a photo for example to act weird and have issues. While the classic version worked as always. -
kyzarvs As a bit of an Outlook super-nerd since O2003, I'm getting more motivated to try and find something else that can handle my workload. 2019 was the last decent version, I struggle with the web version for just one corp account and Classic has more bugs than I can shake a stick at. MS had something so right for so long, yet have managed to completely balls it up over the last couple of years...Reply -
das_stig It slipped past the developers due to them being sh!t at writing code and bug checked by any reasonable coder. They live in a world of code it, push it out to the masses for testing, fix whatever it breaks or doesn't work and repeat. I very much doubt anybody in big business coding now understands their own code until they need to do a fix. In my opinion documenting coding has went the same way as QA, unnecessary expense and cut from project budgets.Reply -
2Be_or_Not2Be I wonder if this is related to the cloud-connected stuff. It's been a while, but I feel like I had to turn off "Optional connected experiences" when I had some Outlook slow-downs in the past. Anyway, I don't need AI-analysis of my emails that I'm writing - thanks, but no thanks.Reply