compmgmt.msc: Complete Guide to Windows Computer Management
QUICK ANSWER compmgmt.msc opens the Windows Computer Management console, a built-in collection of administrative tools for viewing events, managing disks and...
QUICK ANSWER
compmgmt.msc opens the Windows Computer Management console, a built-in collection of administrative tools for viewing events, managing disks and services, checking hardware, managing local accounts, monitoring performance, and performing other system-management tasks from one interface.
You can start it by pressing Windows+R, entering compmgmt.msc, and selecting OK. Viewing information may not require elevation, but many configuration changes require an administrator account and User Account Control approval.
What Is compmgmt.msc?
compmgmt.msc is the Microsoft Management Console file for Computer Management. It is included with supported Windows desktop and Windows Server editions.
The console brings several administrative snap-ins together in one window. Instead of opening Event Viewer, Disk Management, Services, Device Manager, and other tools separately, administrators can access them through a common navigation tree.
The .msc extension identifies a saved Microsoft Management Console configuration. When you run compmgmt.msc, Windows opens the file through mmc.exe and loads the registered management snap-ins.
The console itself is not a background service and does not continuously optimize, repair, or monitor the computer. It provides interfaces through which authorized users can inspect and change Windows configuration.
Supported Windows Versions
Computer Management is available on Windows 11 and supported Windows Server releases. The command also exists on Windows 10, but general support for most Windows 10 editions ended on October 14, 2025. Organizations still using Windows 10 should confirm that their edition is covered by an applicable support or Extended Security Updates program.
The exact tools displayed can vary according to:
- Windows edition
- Client or server operating system
- Installed roles and optional features
- User permissions
- Whether the local or a remote computer is selected
For example, the Local Users and Groups snap-in is not available in Windows Home editions. Domain controllers also manage accounts through Active Directory tools rather than a normal local account database.
How to Open Computer Management
Method 1: Use the Run Dialog
- Press Windows+R.
- Enter:
compmgmt.msc
- Press Enter or select OK.
Method 2: Use the Start Menu
Search for Computer Management, and then open the matching result.
To perform administrative tasks, right-click Computer Management and select Run as administrator.
Method 3: Use the Power User Menu
Right-click the Start button, or press Windows+X, and select Computer Management when that option is available.
Method 4: Use Command Prompt, PowerShell, or Windows Terminal
Run:
compmgmt.msc
To explicitly open the console through Microsoft Management Console, use:
mmc.exe %windir%\System32\compmgmt.msc
Microsoft also supports the following general MMC syntax:
mmc <path>\<filename>.msc [/a] [/64] [/32]
The /a option opens a console in author mode. The /32 and /64 options select an MMC architecture and are mainly useful when working with architecture-specific snap-ins. They are not normally needed for everyday Computer Management use.
How Computer Management Works
Computer Management uses a tree-based MMC interface with three areas:
- Console tree: Lists categories and snap-ins.
- Details pane: Displays information from the selected tool.
- Actions pane: Provides commands relevant to the selected item.
When you select a snap-in, MMC loads its registered management component. That component communicates with the appropriate Windows subsystem. For example:
- Event Viewer reads Windows event logs.
- Disk Management communicates with Windows storage-management components.
- Services communicates with the Service Control Manager.
- Device Manager obtains Plug and Play device information.
- Task Scheduler communicates with the Task Scheduler service.
Permissions are checked by the underlying Windows component. Opening Computer Management does not automatically grant administrative access.
Computer Management Tools and Their Uses
The available items are normally organized under System Tools, Storage, and Services and Applications.
| Tool | Primary purpose | Typical uses |
|---|---|---|
| Task Scheduler | Manages scheduled tasks | Review automated jobs, task history, triggers, and failures |
| Event Viewer | Displays Windows event logs | Investigate crashes, service failures, security events, and application errors |
| Shared Folders | Shows Windows file-sharing activity | Review shares, active sessions, and open files |
| Local Users and Groups | Manages local accounts and groups | Create local users and review local group membership |
| Performance | Provides performance monitoring | Examine counters, reports, and Data Collector Sets |
| Device Manager | Displays installed hardware | Check device status, drivers, and hardware errors |
| Disk Management | Manages disks, partitions, and volumes | Initialize disks, assign drive letters, and shrink or extend supported volumes |
| Services | Manages Windows services | Review status and startup type or start and stop authorized services |
| WMI Control | Displays Windows Management Instrumentation settings | Check WMI status, security, and configuration |
Some editions or configurations may show additional or fewer tools.
System Tools Explained
Task Scheduler
Task Scheduler runs programs, scripts, and system operations when defined triggers and conditions are met. Tasks can start at boot, at sign-in, at a specific time, or after certain events.
Use it to:
- Confirm that a scheduled task ran
- Review its last result
- Check triggers, conditions, and actions
- Disable an unwanted task temporarily while troubleshooting
- Create approved administrative automation
Do not delete unfamiliar Microsoft or application tasks merely because their purpose is unclear. Disabling system tasks can affect maintenance, updates, security, or installed software.
Event Viewer
Event Viewer records operational information from Windows, applications, drivers, and services. It is one of the most useful tools for diagnosing problems.
Common logs include:
- Application: Events generated by applications and application components
- Security: Audit events controlled by security policy
- Setup: Installation and configuration events
- System: Events generated by Windows components, services, and drivers
- Forwarded Events: Events collected from other computers when event forwarding is configured
When investigating a problem, note the event’s timestamp, level, source, event ID, and description. An individual warning or error does not automatically identify the cause; correlate it with the time and symptoms of the failure.
Avoid clearing logs during troubleshooting unless they have first been exported or are no longer required. Security and operational logs may be needed for auditing or incident investigation.
Shared Folders
Shared Folders can display:
- Shares: Folders and administrative resources shared from the computer
- Sessions: Remote users currently connected to shared resources
- Open Files: Files opened through Windows file sharing
Administrators can use it to identify who is connected before maintenance or determine why a shared file is locked.
Closing a session or open file can cause unsaved data loss. Contact the affected user first whenever possible.
Local Users and Groups
This snap-in manages accounts and group memberships stored on the local computer. It is useful for reviewing local administrators, disabling obsolete accounts, or adding an account to an appropriate local group.
Important limitations include:
- It is unavailable in Windows Home editions.
- It does not manage Microsoft Entra ID or Active Directory domain accounts centrally.
- A domain controller does not have the ordinary local user database found on member computers.
- Users should receive only the permissions required for their role.
For organizational devices, centrally managed identity and supported solutions such as Windows LAPS are preferable to reusing the same local administrator password across computers.
Performance
The Performance section provides access to Performance Monitor and Data Collector Sets. It can track counters such as processor utilization, available memory, disk activity, and network performance.
It is useful for:
- Establishing a performance baseline
- Investigating intermittent slowdowns
- Recording counters over time
- Comparing behavior before and during a problem
Short spikes are not necessarily faults. Performance data should be interpreted over an appropriate period and alongside workload information.
Device Manager
Device Manager shows detected hardware and associated device status. Warning symbols may indicate a missing driver, a disabled device, or another hardware or configuration problem.
Use it to:
- Verify that Windows detects a device
- Review device status and error codes
- Enable or disable supported devices
- Update, roll back, or uninstall drivers when appropriate
- View hardware IDs and driver information
Prefer drivers from Windows Update or the hardware manufacturer. Avoid third-party “driver updater” applications that cannot establish the authenticity or compatibility of a driver.
Modern Windows versions do not support remote Device Manager operation through Computer Management in the same way as older systems. Microsoft documents that remote access to the Plug and Play RPC interface was removed beginning with Windows 8 and Windows Server 2012. Use Device Manager locally or through an authorized interactive remote session.
Storage and Disk Management
Disk Management displays physical disks, partitions, volumes, file systems, capacity, and allocation status. Supported tasks include:
- Initializing a new disk
- Creating and formatting volumes
- Assigning or changing drive letters
- Shrinking supported basic volumes
- Extending supported volumes into suitable unallocated space
- Taking certain disks online or offline
- Attaching and detaching virtual hard disks
Disk Management Safety Precautions
Disk operations can make data or an operating system inaccessible. Before modifying storage:
- Back up important data.
- Confirm the disk number, capacity, and current volumes.
- Save or locate the BitLocker recovery key when encryption is enabled.
- Confirm that the backup can be restored.
- Avoid modifying EFI System, recovery, OEM, or other unfamiliar partitions.
- Understand where unallocated space is located before attempting to extend a volume.
Microsoft specifically recommends not modifying EFI System and recovery partitions. Although Disk Management may display misleading free-space information for these partitions, they contain files required for startup and recovery.
Disk Management does not replace all storage utilities. Storage Spaces, drive optimization, cleanup, and some advanced operations use separate Windows tools or PowerShell commands.
Services and Applications
Services
The Services snap-in displays installed Windows services and their current states. Depending on permissions, it can start, stop, pause, resume, or restart supported services and change their startup configuration.
Common startup types include:
- Automatic: Windows starts the service automatically.
- Automatic (Delayed Start): The service starts automatically after higher-priority startup activity.
- Manual: Windows or an application starts the service when needed.
- Disabled: The service cannot start until its startup type is changed.
Do not disable a service solely because it is unfamiliar. Services can have dependencies, and changing one may affect networking, sign-in, security, updates, device support, or applications. Record the original configuration before making a temporary troubleshooting change.
WMI Control
Windows Management Instrumentation provides management information used by Windows, scripts, monitoring products, and administrative tools. WMI Control can display status, namespaces, security settings, and other properties.
Changing WMI namespace security can disrupt applications and remote-management systems. Such changes should be made only when required by documented application or organizational procedures.
Managing Another Computer Remotely
Computer Management can connect to some management components on another Windows computer.
To attempt a remote connection:
- Open Computer Management.
- Select Action.
- Select Connect to another computer.
- Enter or browse for the target computer.
- Select OK.
- Confirm that the console root shows the correct remote computer name.
Remote management normally requires:
- Network connectivity and name resolution
- Appropriate administrative permissions on the target
- Required Windows services on the target
- Applicable firewall rules
- RPC or other management protocols required by the selected snap-in
- Organizational policies that permit remote administration
Not every Computer Management snap-in supports remote operation, and supported capabilities differ between Windows versions. Device Manager, certain storage operations, and application-specific extensions can be unavailable or limited remotely.
For security, do not broadly disable Windows Firewall or expose management ports to untrusted networks. Enable only the documented management rules required by your organization, restrict their network scope, and use authenticated administration channels. Remote Desktop, Windows Admin Center, PowerShell remoting, Microsoft Intune, or other approved management platforms may be more suitable.
Administrator and Security Requirements
Opening the console and viewing some information may work with a standard account. Actions such as changing services, modifying accounts, formatting disks, or managing protected logs usually require elevation.
For administrative work:
- Search for Computer Management.
- Right-click it.
- Select Run as administrator.
- Approve the User Account Control prompt using an authorized administrator account.
Follow these security practices:
- Use a standard account for normal work.
- Elevate only when an administrative task requires it.
- Verify the selected local or remote computer before making changes.
- Grant users the minimum necessary permissions.
- Document changes to disks, services, accounts, tasks, and shares.
- Back up important data and configurations before high-impact changes.
- Do not clear evidence during a security investigation.
- Do not enable unnecessary remote-management access.
Benefits of compmgmt.msc
Computer Management offers several practical advantages:
- Centralized administration: Frequently used tools are available in one console.
- Faster troubleshooting: Events, services, devices, tasks, and performance data can be compared without opening many applications.
- Consistent interface: MMC snap-ins share a familiar tree, details, and actions layout.
- Local and limited remote management: Administrators can examine supported components on another computer when correctly configured.
- No additional installation: The console is built into Windows.
- Granular control: Administrators can work with individual services, accounts, shares, devices, disks, and tasks.
- Custom MMC support: IT professionals can create separate MMC consoles containing selected snap-ins for particular administrative roles.
These benefits do not make Computer Management a complete enterprise-management solution. It lacks the centralized reporting, policy enforcement, automation, and fleet-scale capabilities of platforms such as Group Policy, Microsoft Intune, Configuration Manager, Windows Admin Center, or PowerShell-based administration.
Common Use Cases
Investigate an Application Crash
- Open Event Viewer.
- Select Windows Logs > Application.
- Filter or search around the time of the crash.
- Record the source, event ID, faulting application, and faulting module.
- Correlate the event with application logs and recent changes.
Investigate a Windows Service That Will Not Start
- Open Services and check the service status.
- Review its startup type and dependencies.
- Open Event Viewer and inspect the System and Application logs.
- Check the service account, required files, and application-specific documentation.
- Correct the underlying problem before repeatedly trying to start it.
Check a New Drive
- Open Disk Management.
- Identify the drive by capacity and hardware information.
- Confirm that it is the intended disk.
- Initialize and format it only if it contains no required data.
- Assign an appropriate drive letter.
If Windows requests initialization for a disk that previously contained data, cancel the operation and investigate the connection or disk condition first.
Find Who Has a Shared File Open
- Open Shared Folders > Open Files.
- Locate the file and connected user.
- Ask the user to save and close it.
- Close the remote handle only when necessary and with authorization.
Troubleshooting compmgmt.msc
Computer Management Does Not Open
Try the explicit path:
%windir%\System32\compmgmt.msc
If the .msc association is not working, use:
mmc.exe %windir%\System32\compmgmt.msc
Restart Windows and install pending supported updates. If Windows system files may be corrupted, open an elevated terminal and run:
sfc /scannow
Restart the computer if System File Checker repairs files.
“Access Is Denied” Appears
Possible causes include:
- The console was not elevated.
- The account lacks the required local or remote permissions.
- User Account Control elevation was declined.
- Organizational policy blocks the action.
- The target service or snap-in has separate security permissions.
Reopen Computer Management as an administrator and verify authorization. Do not weaken security policy simply to bypass the error.
A Snap-In Is Missing
A snap-in may be absent because:
- The Windows edition does not include it.
- A required role or optional feature is not installed.
- The computer is a domain controller or has another specialized role.
- The corresponding snap-in registration or system component is damaged.
- A remote target does not support that snap-in.
Use the appropriate supported alternative rather than downloading unknown .msc files.
Remote Connection Fails
Verify:
- The target computer name is correct.
- The target is online and reachable through the approved network.
- Name resolution works.
- Your account is authorized on the target.
- Required services and firewall rules are enabled.
- Organizational policy allows remote administration.
- The chosen snap-in supports remote access on those Windows versions.
A successful connection to the Computer Management root does not guarantee that every individual snap-in will work remotely.
Disk Management Is Blank or Stuck Connecting
Allow time for storage enumeration, especially when disconnected network storage, virtual disks, or failing hardware is present. Then check:
- The Virtual Disk service
- Storage-controller and disk status in Device Manager
- System events related to disk, NTFS, storage, or controllers
- Physical connections for removable or newly installed storage
Do not initialize, format, or clean a disk as a general troubleshooting experiment.
Alternatives to Computer Management
| Requirement | Suitable tool |
|---|---|
| Open one snap-in directly | eventvwr.msc, services.msc, taskschd.msc, devmgmt.msc, or diskmgmt.msc |
| Automate repeatable administration | PowerShell |
| Manage Windows Server through a browser-based interface | Windows Admin Center |
| Configure domain computers centrally | Group Policy and domain-management tools |
| Manage organization-owned endpoints | Microsoft Intune or another approved endpoint-management platform |
| Work interactively on a remote desktop | Remote Desktop, where authorized |
| Manage large numbers of servers or clients | Centralized enterprise-management and monitoring tools |
Computer Management is most effective for local administration, one-computer troubleshooting, and limited remote management. Automation or centralized management is usually safer and more consistent at scale.
FAQ
What does compmgmt.msc stand for?
It is the Microsoft Management Console file for Computer Management. The name is an abbreviation of “computer management,” and .msc identifies a saved MMC console.
Is compmgmt.msc safe?
Yes. The genuine Windows file is a built-in administrative console. Normally it is stored under %windir%\System32. Do not open an .msc file received from an untrusted source, because custom consoles can load registered management snap-ins or connect to management targets.
Does compmgmt.msc require administrator rights?
Not always for opening the console or viewing basic information. Most configuration changes require an administrator account and elevation through User Account Control.
Does compmgmt.msc work in Windows Home?
Computer Management is available, but some snap-ins are missing. In particular, Windows Home does not include the Local Users and Groups snap-in.
Can Computer Management manage a remote computer?
It can remotely manage supported components when the network, firewall, services, permissions, and policies are correctly configured. Not all snap-ins support remote management, and modern Device Manager must generally be used locally.
Can compmgmt.msc repair Windows automatically?
No. It is a collection of management interfaces, not an automatic repair utility. It helps administrators diagnose problems and perform specific authorized actions.
What is the difference between compmgmt.msc and mmc.exe?
mmc.exe is the Microsoft Management Console application. compmgmt.msc is a saved console definition that tells MMC which Computer Management snap-ins to load.
What is the difference between Computer Management and Control Panel?
Control Panel primarily exposes user and system settings. Computer Management concentrates administrative and diagnostic tools such as events, services, disks, devices, tasks, accounts, and shared resources.
Can I use compmgmt.msc to format a drive?
Yes, Disk Management can format supported volumes. Formatting can destroy access to existing data, so verify the disk and backup status before proceeding. Do not modify EFI, recovery, or unfamiliar system partitions.
FINAL RECOMMENDATION / CONCLUSION
Use compmgmt.msc as a central starting point for local Windows administration and troubleshooting. It is especially useful for correlating event logs, service status, scheduled tasks, hardware condition, storage configuration, shared-file activity, and local account settings.
Open it with standard permissions for inspection and elevate only when a required change is authorized. Before changing disks, services, accounts, tasks, or remote systems, verify the target, record the original configuration, and protect recoverable data. For organization-wide administration, use centrally controlled tools instead of making repeated manual changes through individual Computer Management consoles.
#compmgmtmsc #ComputerManagement #Windows11 #WindowsServer #WindowsAdministration #MicrosoftManagementConsole #MMC #EventViewer #DiskManagement #DeviceManager #WindowsServices #TaskScheduler #LocalUsersAndGroups #SharedFolders #PerformanceMonitor #RemoteManagement #WindowsTroubleshooting #ITSupport
SOURCES
- Microsoft Learn — MMC command reference
- Microsoft Learn — Overview of Disk Management
- Microsoft Learn — Connect to another computer with Windows Computer Management
- Microsoft Learn — Remote Device Manager limitations
- Microsoft Learn — Windows LAPS overview
- Microsoft Learn — RPC interface security restrictions
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.