Skip go content

mmc.exe

Windows ProcessMicrosoft Corporation

Catalog search terms mmc, microsoft management console, snap-in host

WindowsSystem Component

Microsoft Management Console. E dey host snap-ins like services.msc. E no be SystemSettings.exe and e no be services.exe.

Wetin you need know

mmc dey host snap-ins; e no be SystemSettings.exe and e no be services.exe.

mmc.exe na di console wey dey load .msc snap-ins. services.msc na document wey MMC dey open. services.exe na Service Control Manager, e dey always dey there. SystemSettings.exe na di Settings app. To close MMC no dey stop SCM.

E safe?
Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
Same thing as Settings?
No. Settings na SystemSettings.exe
Same as services.exe?
No. Dat one na Service Control Manager
Feex tok say
If I open services.msc, I dey expect mmc. I no dey end services.exe because I close di snap-in, and I no dey hunt Settings for dat list.

Wetin be mmc.exe?

mmc dey host snap-ins; e no be SystemSettings.exe and e no be services.exe. To open services.msc dey launch dis host with di Services snap-in. SCM remain services.exe. Settings remain SystemSettings.exe.

Wetin e dey do?

E dey load .msc and di snap-in DLL. E no dey replace di Services list inside Settings and e no dey become Service Control Manager.

Wetin make am dey run?

You open snap-in (Services, Event Viewer, Disk Management, Certificates). Copy wey no get window na leftover console.

Wetin make many copies dey?

Several mmc.exe copies na several consoles. Dat one no be several services.exe processes and no be several Settings apps.

Inspect the running instance

Inside Windows PowerShell, this read-only query show matching process IDs, creation times and executable paths on this PC. (pcm)

Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'mmc.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List

No result or a path we no fit access is inconclusive. Protected processes fit restrict access, and process IDs fit be reused. Keep personal paths local. (pcm)

Use the file-identity guide to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)

E dey safe?

Check dis running file

System32 mmc.exe na Microsoft Management Console. One mmc.exe inside Downloads no be am. Dis one still no be SystemSettings and no be services.exe.

Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)

C:\Windows\System32\mmc.exe

  • Dey host .msc snap-ins
  • Settings app: ImmersiveControlPanel\SystemSettings.exe
  • Service Control Manager: services.exe

I fit end am?

Dey close dat console

To end mmc.exe dey close dat snap-in window. services.exe dey stay. SystemSettings.exe dey stay. Dem fit lose console customizations wey pesin never save.

I fit comot am?

No

No delete mmc.exe. You go lose snap-in hosting. To uninstall management tool no dey remove Settings or SCM.

E suppose start with Windows?

Shortcut go .msc fit start am. services.exe dey start with di boot path. Dat one no be dis host.

Measure resource use

Measure the current process rather than assume a universal baseline
CPU and memory Compare several observations for the same PID and workload. This entry get no independently measured universal baseline. (pcm)
Disk and network Attribute activity to the actual process and current task; a filename alone no fit establish expected destinations or transfer volume. (pcm)

File information

mmc.exe file information
Executable name mmc.exe
Recorded installation path C:\Windows\System32\mmc.exe
Publisher Microsoft Corporation
Signature check Inspect the actual file; this entry no dey certify its certificate identity. (pcm)

Common wahala dem

People dey end services.exe after dem close Services.msc

You close snap-in. SCM na different process. To end services.exe na how you dey crash di session.

Dem reset Settings because Disk Management refuse to open

diskmgmt.msc na MMC. Repair di console or di VDS stack. SystemSettings.exe na di wrong app.

How to troubleshoot

Diagnose before you change anything wey fit scatter things.

Check di command line for di .msc name

services.msc, eventvwr.msc, diskmgmt.msc. Dat one dey name di snap-in. Task Manager own window na taskmgr.exe.

Author new console with mmc /a only if di .msc spoil

No replace services.exe. No delete System32\mmc.exe from zip "fix."

Technical details

Technical details
mmc.exe technical details
Image name mmc.exe
Role Microsoft Management Console snap-in host

Check the identity of running file

A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.

Dis article make sense to you?