Outlook for Mac freezes after switching to the new editor

Gershon Goldenberg 0 Reputation points
2025-12-10T20:06:46.4833333+00:00

Hello,

Outlook for Mac freezes only when replying to an email (Reply). When typing the first character in the reply window, CPU spikes to 99% in multiple “Microsoft Outlook Web Content” processes, and the editor hangs. Creating a brand-new email works normally. The issue appears only in the separate compose window with the new editor.

Thank you,

Outlook | MacOS | New Outlook for Mac | For business
{count} votes

2 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-12-10T20:06:56.1866667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It appears that you are experiencing performance issues with Outlook for Mac when using the new editor, particularly when replying to emails. Unfortunately, the provided context does not contain specific information regarding this issue with the new editor in Outlook for Mac.

    However, general troubleshooting steps for performance issues in Outlook include ensuring that your software is updated to the latest version, disabling any unnecessary add-ins, and checking for conflicts with antivirus software. If the problem persists, consider reaching out to Microsoft support for further assistance.


    References:

    0 comments No comments

  2. Teddie-D 9,045 Reputation points Microsoft External Staff Moderator
    2025-12-11T04:38:58.9966667+00:00

    Hi @Gershon Goldenberg  

    Thank you for posting your question in the Microsoft Q&A forum.  

    We understand how frustrating it can be to wait several hours between support responses, especially when a critical feature like replying to emails isn’t working and is impacting your productivity. Thank you as well for providing detailed information and screenshots; they are extremely helpful in understanding the issue clearly.

    As community moderators, we don’t have access to Outlook’s internal diagnostics or engineering tools, so our ability to troubleshoot issues like this is limited to public documentation and what other users have reported. Since you’ve already opened a support case and provided an Incident ID, you’ve taken the right step to get this properly investigated. 

    We completely understand how disruptive this situation is, and it’s absolutely reasonable to expect timely updates. The support team is the group that can review logs and escalate this issue directly to engineering. Continuing to follow up on your case will help ensure the issue receives the right level of attention.

    We truly appreciate your patience and understanding, and we hope the support team can identify the root cause quickly so you can return to a smooth workflow.


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.