ms-teams.exe
Also called teams, microsoft teams, ms-teams, teams.exe
The current Microsoft Teams desktop process on many Windows 11 PCs. Older installs may still show Teams.exe.
What you need to know
This is Microsoft Teams, not a system host.
ms-teams.exe is the new Teams client on many PCs. It can stay in the tray. Meetings raise CPU, RAM, and GPU.
- Windows process?
- No. This is Teams
- High RAM normal?
- Meetings and many chats can be heavy
- Should I close it?
- Quit Teams if you are done
What is ms-teams.exe?
ms-teams.exe is the current Microsoft Teams desktop app. Older machines may still run Teams.exe from the classic client.
What does it do?
It handles chat, meetings, and calendar. It can use the GPU for video.
Why is it running?
You opened Teams, or it started with Windows because work policy or the app setting said so.
Is it safe?
Usually safe if the path is Teams
The new client typically lives under WindowsApps or Program Files\WindowsApps related packages, or a Microsoft Teams install folder. A Teams.exe from email is not that app.
A legitimate copy normally runs from:
C:\Program Files\WindowsApps\MSTeams_*\ms-teams.exe
- The exact package folder changes with updates
- Classic Teams used a different Teams.exe path under AppData
Can I end it?
Quit Teams
Quit from the tray when you are done. Ending it during a meeting disconnects you.
Can I remove it?
Uninstall or remove the app package
Work PCs may reinstall Teams through Microsoft 365. Deleting the exe by hand is the wrong removal.
Should it start with Windows?
Teams often starts with Windows. Turn that off in Teams settings if your admin allows it.
Normal resource behavior
These are contextual labels, not universal averages.
- CPU
- High during video meetings
- Memory
- Can stay high after many chats
- GPU
- Video and background effects
- Network
- Active in meetings
File information
| Executable name | ms-teams.exe |
|---|---|
| Common legitimate path | C:\Program Files\WindowsApps\MSTeams_*\ms-teams.exe |
| Publisher | Microsoft Corporation |
| Signature expectation | Signed by Microsoft Windows |
Common problems
Two Teams processes
Classic and new Teams can overlap during a migration. That is a client transition, not two viruses.
High RAM after work
Quit the tray app. A restart of Teams is a better first step than a Windows reinstall.
Troubleshooting
Diagnose before you change anything destructive.
Confirm the path and signature
Open the process properties and check that ms-teams.exe runs from the expected folder and is signed by the expected publisher. This is the first check, not a Registry edit.
See what the process is doing
Task Manager can show CPU, memory, disk, and GPU. High use during an obvious job is often normal. High use when the PC is idle needs a closer look at the related app or service.
Avoid destructive first steps
Do not delete ms-teams.exe, disable critical services without knowing the effect, or edit the Registry as the first move.
Technical details
Technical details
| Image name | ms-teams.exe |
|---|---|
| Legacy name | Teams.exe |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft Support: Microsoft Teams · Official Teams help
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.