Seven proven methods to launch the Windows Services Manager — from the quickest Run command to PowerShell one-liners for power users.
Windows Services are long-running background processes that start automatically with the operating system and continue to run silently without any user interaction. They handle everything from network connectivity and audio playback to Windows Update and antivirus scanning.
Unlike regular applications, services don't have a visible window. They run under dedicated user accounts (often SYSTEM or LOCAL SERVICE) and are managed through a dedicated tool called the Services Manager (services.msc).
You might need to open the Services Manager to:
Windows Management Instrumentation or RPC Endpoint Mapper — can cause system instability or prevent Windows from booting correctly. Always research a service before changing its startup type.
All seven methods described in this guide work on both Windows 10 (all editions, version 1507 through 22H2) and Windows 11 (all editions, version 21H2 and later). Minor UI differences between the two versions are noted where relevant.
The Run dialog is the quickest way to open the Services Manager on any version of Windows. Power users have relied on this method for decades — it requires only two keystrokes and works even when the Start Menu is unresponsive.
services.msc in the Open field. The text is case-insensitive — SERVICES.MSC works too.
Run Dialog — command
services.msc
The .msc extension stands for Microsoft Management Console snap-in. The Services snap-in file is located at %SystemRoot%\system32\services.msc on every Windows installation.
The Windows Search bar is the most beginner-friendly method. On Windows 11, search is integrated into the Taskbar; on Windows 10, you can click the magnifying glass icon or simply start typing with the Start Menu open.
On Windows 11, the Search panel has a clean unified interface that groups results by category. You may also see a quick-action button labeled Open directly in the search panel, so you don't even need to navigate to the result.
Task Manager has its own Services tab that gives you a quick overview of all running services. From there, you can jump directly into the full Services Manager for advanced configuration.
services.msc snap-in with all advanced options.The classic Control Panel route uses the Administrative Tools folder (renamed Windows Tools in Windows 11), which groups all built-in management consoles including Services, Event Viewer, and Disk Management in one place.
control admintools (Windows 10) or searching "Windows Tools" in the Start menu (Windows 11).
Command Prompt gives you two options: open the graphical services.msc window from the terminal, or use the built-in sc (Service Control) and net commands to manage services entirely from the command line.
Command Prompt
services.msc
Alternatively, you can interact with services directly without opening any GUI window at all. The sc command communicates with the Service Control Manager, while net provides simpler start/stop syntax:
Command Prompt — sc command examples
sc query # List all services and their status
sc query "wuauserv" # Query Windows Update service
sc start "wuauserv" # Start Windows Update
sc stop "wuauserv" # Stop Windows Update
sc config "wuauserv" start=auto # Set startup type to Automatic
Command Prompt — net command examples
net start # List currently running services
net start "Windows Update" # Start by display name
net stop "Print Spooler" # Stop by display name
PowerShell is the most powerful command-line option for service management. Unlike sc, PowerShell's Get-Service and related cmdlets return structured objects that you can filter, sort, and pipe — making them ideal for scripting and automation.
PowerShell
services.msc
PowerShell — service management cmdlets
# List all services with name, status, and startup type
Get-Service | Select-Object Name, Status, StartType | Format-Table -AutoSize
# Get a specific service
Get-Service -Name "wuauserv"
# Start, stop, restart a service
Start-Service -Name "Spooler"
Stop-Service -Name "Spooler"
Restart-Service -Name "Spooler"
# Change startup type to Disabled
Set-Service -Name "XblGameSave" -StartupType Disabled
# Find all stopped services that are set to Automatic start
Get-Service | Where-Object { $_.Status -eq 'Stopped' -and $_.StartType -eq 'Automatic' }
-ComputerName parameter (on older PowerShell) or Invoke-Command, making it straightforward to administer services on multiple machines simultaneously.
Computer Management (compmgmt.msc) is an all-in-one administration hub. It embeds the Services snap-in alongside Disk Management, Device Manager, Event Viewer, and more — useful when you want to perform multiple administrative tasks in one session.
compmgmt.msc, and press Enter.
Run Dialog — Computer Management
compmgmt.msc
Once you've opened Services, you'll see a two-pane window. Here's what each element means:
| Column | Description |
|---|---|
| Name | The friendly display name of the service (e.g., "Windows Update"). |
| Description | A brief explanation of what the service does. |
| Status | Running or blank (Stopped). Some services also show Paused. |
| Startup Type | Automatic, Automatic (Delayed), Manual, Disabled, or Trigger Start. |
| Log On As | The Windows account under which the service runs (e.g., Local System). |
The left pane shows a description of the currently selected service. Double-clicking any row opens its Properties dialog where you can change startup type, view dependencies, and configure recovery actions (what happens if the service crashes).
Whether you opened Services via services.msc or Task Manager, the procedure to control a service is the same:
Remote Procedure Call (RPC), DCOM Server Process Launcher, or Windows Management Instrumentation.
When you open a service's Properties dialog, you'll find a Startup type dropdown. Here's what each option means:
| Startup Type | When It Starts | Use Case |
|---|---|---|
| Automatic | Immediately at boot, before user login | Critical services (e.g., DHCP Client, Event Log) |
| Automatic (Delayed Start) | ~2 minutes after the desktop loads | Non-critical auto services (reduces boot time impact) |
| Manual | Only when another process or the user starts it | On-demand features (e.g., Bluetooth, Fax) |
| Manual (Trigger Start) | When a specific system event occurs (trigger) | Smart services that activate only when needed |
| Disabled | Never — cannot be started until re-enabled | Services you explicitly don't want running |
Below is a reference table of frequently encountered Windows services, their default startup type, and what happens if you stop or disable them.
| Service Name | Short Name | Default Startup | Impact if Disabled |
|---|---|---|---|
| Windows Update | wuauserv |
Manual (Trigger) | No automatic OS updates |
| Print Spooler | Spooler |
Automatic | Printing stops working entirely |
| Windows Audio | AudioSrv |
Automatic | No sound output or input |
| DHCP Client | Dhcp |
Automatic | No automatic IP address assignment |
| Windows Defender Antivirus | WinDefend |
Automatic | Real-time malware protection disabled |
| Superfetch / SysMain | SysMain |
Automatic | Slower app launches (safe to disable on SSDs) |
| Bluetooth Support Service | bthserv |
Manual (Trigger) | Bluetooth devices stop working |
| Remote Desktop Services | TermService |
Manual | Remote Desktop connections blocked |
| Task Scheduler | Schedule |
Automatic | Scheduled tasks stop running |
| Windows Search | WSearch |
Automatic (Delayed) | File indexing and Start menu search broken |
This error means you're not running the Services Manager (or your command prompt/PowerShell) with administrator privileges. Right-click the Services shortcut and choose Run as administrator, or open CMD/PowerShell as admin before issuing sc or net commands. Note that some services owned by TrustedInstaller cannot be stopped even by administrators without changing permissions — these are protected OS components.
It can be, but only if you do your research first. Services set to Manual (Trigger Start) are already optimized — Windows starts them only when needed, so there's nothing to gain by disabling them. Commonly safe candidates for disabling on desktop PCs include Fax, XboxGipSvc (if you don't use Xbox peripherals), and WbioSrvc (Windows Biometric Service, if you don't use fingerprint/face login). Always note the original setting before changing it so you can revert if something breaks.
Task Manager's Services tab is a simplified view: it shows the service name, PID (process ID), description, and status, and lets you start/stop services with a right-click. The full services.msc snap-in offers much more: you can change the startup type, configure recovery actions (what Windows does when a service crashes — restart it, run a program, etc.), manage service dependencies, and modify the logon account. For everyday quick fixes use Task Manager; for configuration use services.msc.
Open Task Manager (Ctrl+Shift+Esc) and click the CPU or Memory column header to sort processes by usage. If you see svchost.exe using a lot of resources, right-click it and select Go to service(s) — Task Manager will switch to the Services tab and highlight the specific services running inside that svchost process. In Windows 10/11, each service group runs in a separate svchost instance (on systems with ≥3.5 GB RAM), making it easier to pinpoint the culprit.
Yes — you can open and view the Services Manager without admin rights. However, you won't be able to start, stop, pause, or change the configuration of most services. Read-only access is useful for checking service statuses and dependencies. To make changes, you must open Services as an administrator (right-click → Run as administrator, or use an elevated prompt).
There's no single built-in button to reset all services at once. The safest approaches are: (1) run System Restore to a point before you made changes; (2) use DISM (DISM /Online /Cleanup-Image /RestoreHealth) to repair Windows component defaults; or (3) compare your service list against a fresh Windows installation using Microsoft's official service configuration documentation and revert individual services manually.
Trigger Start (also shown as "Manual (Trigger Start)" in the Services Manager) means the service has one or more registered triggers — specific system events that automatically start it when they occur. Common triggers include: a USB device being connected, a network interface coming online, a specific ETW (Event Tracing for Windows) event, or the system reaching a certain state. This is more efficient than Automatic because the service starts only when genuinely needed and stops when idle. You cannot create or modify triggers from the GUI — it requires the sc triggerinfo command or Group Policy.
All seven methods described in this guide reach exactly the same destination — the Windows Services Manager. The right choice depends entirely on your workflow and comfort level.
For the fastest access, memorize one keyboard shortcut: Win+R, then type services.msc and press Enter. This works on every version of Windows from XP to 11, even when the Start Menu or Taskbar is unresponsive.
If you're new to Windows administration, the Search bar method (type "Services" in the Start menu) requires no memorization and is equally reliable. For IT professionals and power users managing multiple machines, PowerShell cmdlets offer unmatched flexibility through scripting and remote management capabilities.
Fastest single access: Win + R → services.msc
No command memorization: Start menu search → "Services"
Already in Task Manager: Services tab → Open Services
Scripting & automation: PowerShell Get-Service cmdlets
Manage multiple admin tools at once: Computer Management (compmgmt.msc)
Regardless of how you open it, always research a service before disabling it and keep notes on what you changed — this makes troubleshooting far easier if something unexpected stops working.