High CPU usage when typing a message in Outlook

I have the same issue as described here. Everything is ok until start typing (new message or reply). Then CPU increases his activity to 10-20% for nothing! When stop typing, CPU activity goes down to normal.

I switched off all addons, no improvement...

Brand new notebook, Microsoft® Outlook® 2024 MSO (Version 2501 Build 16.0.18429.20132) 64 bit.

It's very annoying!

I'm not aware of way to open a formal complaint...

That's a good question. Because if you contact their customer support, they just endlessly let you try this and that and the same again, always assuming that you as the user would have misconfigured something and not Microsoft causes this bug.

Maybe the DSA (Digital services act) within the EU offers a possibility to force Microsoft to cover the issue?

Same Issue here.

But there's no hope this will be fixed. Today I installed the Office Desktop-apps from my MS-365-Subscription on a fresh installed Windows 11-System. As a surprise, no "classic" Outlook-Client could be found.

The "new" Outlook was installed instead as the default email program.This new application is terrible and a nightmare in terms of data.

Many users use PST files, which are not yet fully supported (read access only, but still). But that doesn't matter. Microsoft doesn't want people to work with the classic Outlook. But they offer a link to install the classic outlook separately.

We should also all get in touch with our local IT magazines, explain the Outlook bug to them and ask them to publish about it. That may impose some pressure on Microsoft and prevent others from switching from other e-mail clients to buggy Outlook.

Hi Dark Rider,

Totally agree; with your comments.
My experience of Microsoft technical support is that when confirmed the problem is supposed to be "escalated" to the next level of technician. Then, be prepared to wait for weeks, or months.
Hence why I asked Linda (above) whether the problem affects later versions of Office Pro or not ( it might be easier to buy a newer version of Office, than tinkering for weeks). Unfortunately, this question remained unanswered. Would be interesting to know if later versions of Office are affected, too.

Note: In your previous correspondence, you mentioned that the problem also affects Win 10. I have another machine running on Win 10 Pro, where Office 2K16 Pro is installed, but could not reproduce the problem on this machine. Strange.