key takeaways
- Microsoft has admitted that Outlook has a bug in classic that slows CPUS to 30–50%.
- The company has offered a temporary solution by shifting to a semi-annual channel.
- The issue is six months old, but Microsoft has not yet offered a permanent fix.
Microsoft has accepted a bug in its outlook classic software, which increases the use of CPU by 30%-50%. This problem remains since November 2024, many users have an abnormal increase in CPU use when complaining of a slow system and typing emails.
Users have reported that disabled of spell-check and graphic acceleration also did not help. One user also said that the temperature of his i9–14900hx CPU reached 95 ° C when he opened the ‘New Sandesh’ tab.
However, Microsoft did not offer a long -term fix for the problem. Fix only a stopgap. Users can switch to a semi-annual channel, where this problem has not been seen. The issue appears to be specific to the current, monthly enterprise or internal formula channels.
Here’s how you can do it as a home user:
- Command prompt open
- Type the following command: Reg add hklm \ software \ Microsoft \ Microsoft \ Office \ 16.0 \ Common \ Officeupdate /V Updatebranch /T Reg_sz /D Semianual Add
- Once you have added the Registry Key, select the file> office account> update option> update to switch now.
If you are running an outfit, Microsoft has published a wide guide how you can update the channel using a group policy, office finance equipment (ODT), Configuration Manager, Microsoft Intune Administrative Template and Administrative Center.
Meanwhile, the company has said that the Outlook team is investigating the issue.
Why no fix?
The problem is now over six months, and it is quite strange that a technical Bham like Microsoft is sitting on it. Is the problem complicated, or something under the sheets?
Well, this is a known fact that Microsoft wants to remove with its outlook classic product and has transferred users to the new approach to Windows. However, the company has gone on record to say that it will provide support for the classic by the end of 2029. They do not align two commitments well, are they?
Users will not shift ‘voluntarily’ in the new approach as it lacks some features offered by the classic version. For example, there are no multiple mail profiles, shared mailboxes, custom forms or sharepoint calendar sinks with the new outlook.
In addition, many characteristics, such as offline support, notes modules and .pst support, are only partially available. So, why would the users like to switch to an inferior product?
Can it be possible that this is a strategy to push the entire ‘CPU-Slating Bug’ to users on the new product?
Well, these are just speculation, and we will never reach the bottom of this principle. It may be possible that Microsoft will soon release a permanent fix and keep these principles to relax. For now, we have to wait for the next development on this issue.
The take report editorial policy focuses on providing assistant, accurate material providing real value to our readers. We only work with experienced writers who have specific knowledge in subjects that they cover, including the latest development, online privacy, cryptocurrency, software and more in technology. Our editorial policy ensures that research is done and cured by our in-house editors on each subject. We maintain rigorous journalism standards, and each article is written by 100% real authors.
