(Updated) Upcoming Change to Teams Desktop Client on Windows [MC1189656]

(Updated) Upcoming Change to Teams Desktop Client on Windows [MC1189656]

Message ID: MC1189656 (Updated)

Updated December 12, 2025: Thank you for the valuable feedback we’ve received. We are currently reassessing the rollout timelines to ensure alignment with your needs and operational requirements. You can expect a formal update from us by mid to late January 2026.

[Introduction]

We’re improving the performance and startup time of calling features in the Microsoft Teams Desktop Client for Windows. To achieve this, we’re introducing a new child process named ms-teams_modulehost.exe that will handle the calling stack separately from the main application process (ms-teams.exe). This change optimizes resource usage and enhances meeting experiences.

[When this will happen:]

Updated rollout timing will be announced in January 2026

Note: Timelines may shift due to year-end feature flag rollout freeze.

[How this affects your organization:]
  • Who is affected: All users running the Teams Desktop Client on Windows.
  • What will happen:
    • A new process (ms-teams_modulehost.exe) will appear in Task Manager under the main Teams process (ms-teams.exe).
    • This process is dedicated to calling features and improves performance.
    • No changes to user workflows or UI; however, admins should ensure endpoint and security software allow this new process.
[What you can do to prepare:]
  • Update endpoint management and security software to allowlist ms-teams_modulehost.exe alongside ms-teams.exe.
  • Communicate this change to helpdesk staff to avoid confusion during troubleshooting.
  • Update internal documentation if you reference Teams process names.
  • Make sure the same QoS settings applied to ms-teams.exe are also applied to ms-teams_modulehost.exe. Refer to this page for details: Implement Quality of Service (QoS) in Microsoft Teams
    • DO NOT remove QoS settings of ms-teams.exe. Only add QoS settings for ms-teams_modulehost.exe.
[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft

<<< [MC1189656] Archive
Tooltip: View earlier revisions of this post

Latest Posts

Pass It On
Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *