mmc.exe
Also called mmc, microsoft management console, snap-in host
Microsoft Management Console. It hosts snap-ins such as services.msc. It is not SystemSettings.exe and not services.exe.
What you need to know
mmc hosts snap-ins; it is not SystemSettings.exe and not services.exe.
mmc.exe is the console that loads .msc snap-ins. services.msc is a document MMC opens. services.exe is Service Control Manager, always there. SystemSettings.exe is the Settings app. Closing MMC does not stop SCM.
- Safe?
- Yes, in System32
- Same as Settings?
- No. Settings is SystemSettings.exe
- Same as services.exe?
- No. That is Service Control Manager
What is mmc.exe?
mmc hosts snap-ins; it is not SystemSettings.exe and not services.exe. Opening services.msc launches this host with the Services snap-in. SCM remains services.exe. Settings remains SystemSettings.exe.
What does it do?
It loads an .msc and the snap-in DLL. It does not replace the Services list in Settings and it does not become Service Control Manager.
Why is it running?
You opened a snap-in (Services, Event Viewer, Disk Management, Certificates). A copy with no window is a leftover console.
Why are there multiple copies?
Several mmc.exe copies are several consoles. That is not several services.exe processes and not several Settings apps.
Is it safe?
Usually safe
System32 mmc.exe is Microsoft Management Console. An mmc.exe in Downloads is not. This is still not SystemSettings and not services.exe.
A legitimate copy normally runs from:
C:\Windows\System32\mmc.exe
- Hosts .msc snap-ins
- Settings app: ImmersiveControlPanel\SystemSettings.exe
- Service Control Manager: services.exe
Can I end it?
Closes that console
Ending mmc.exe closes that snap-in window. services.exe stays. SystemSettings.exe stays. Unsaved console customizations may be lost.
Can I remove it?
No
Do not delete mmc.exe. You would lose snap-in hosting. Uninstalling a management tool does not remove Settings or SCM.
Should it start with Windows?
A shortcut to an .msc can start it. services.exe starts with the boot path. That is not this host.
Normal resource behavior
These are contextual labels, not universal averages.
- CPU
- Low unless a snap-in is refreshing hard
- Memory
- Moderate per open console
- Disk
- Low
- Network
- Remote snap-ins can talk to another PC
File information
| Executable name | mmc.exe |
|---|---|
| Common legitimate path | C:\Windows\System32\mmc.exe |
| Publisher | Microsoft Corporation |
| Signature expectation | Signed by Microsoft Windows |
Common problems
People end services.exe after closing Services.msc
You closed a snap-in. SCM is a different process. Ending services.exe is how you crash the session.
They reset Settings because Disk Management would not open
diskmgmt.msc is MMC. Repair the console or the VDS stack. SystemSettings.exe is the wrong app.
Troubleshooting
Diagnose before you change anything destructive.
Check the command line for the .msc name
services.msc, eventvwr.msc, diskmgmt.msc. That names the snap-in. Task Manager's own window is taskmgr.exe.
Author a new console with mmc /a only if the .msc is corrupt
Do not replace services.exe. Do not delete System32\mmc.exe from a zip "fix."
Technical details
Technical details
| Image name | mmc.exe |
|---|---|
| Role | Microsoft Management Console snap-in host |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft Learn: mmc · Microsoft Management Console hosts snap-ins
- Microsoft Learn: what is MMC · Snap-in host, not the Settings app
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
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.