Ddos 
Earlier this month, Microsoft confirmed, following user feedback, that the classic Outlook mail client was experiencing severe system lag caused by abnormally high CPU usage during text input, with related processes consuming between 30% and 50% of CPU resources.
Upon investigation, Microsoft found that only the Microsoft 365 Semi-Annual Channel was unaffected by this issue. As a temporary measure, the company advised affected users to switch to the Semi-Annual Channel until a comprehensive fix could be deployed, after which they could transition back to other update channels.
Microsoft has now released an update regarding the resolution of this problem, stating that the Word support team has devised a fix that will soon be rolled out to the Current Channel and Beta Channel. However, as of the publication of this notice, the corrective update has not yet been released.
In its update log, Microsoft provided the following timeline:
- Beta Channel (Version 2505 Build 18822.15000) – ETA early May 2025, to check for build, go to Update History for Office Beta Channel – Office release notes.
- Current Channel Preview (Version 2505 18827.20000) – ETA mid May 2025, to check for build, go to Update History for Office Current Channel (Preview) – Office release notes.
- Current Channel (Version 2505 18827.20000) – ETA late May 2025, to check for build, go to Update history for Microsoft 365 Apps (listed by date) – Office release notes.
Regrettably, it has come to light that the problem also affects the Microsoft 365 Semi-Annual Channel, although version 2405 specifically does not exhibit the issue. However, subsequent versions include critical security updates, meaning that reverting to version 2405 would expose users to known security vulnerabilities — a course of action Microsoft strongly advises against. Nevertheless, at present, no alternative solutions are available.
For users in urgent need of relief, a rollback to version 2405 remains the only option. The procedure is as follows:
Open Command Prompt in administrator mode, paste the following command, and press Enter:
Upon completion, Outlook will be downgraded to version 2405, and the CPU usage spike during text input should be resolved. However, unless frequent use of Outlook is critical, downgrading is not recommended, as it entails significant security risks.
Donate