In Windows NT operating systems, a Windows service is a computer program that operates in the background. It is similar in concept to a Unix daemon. A Windows service must conform to the interface rules and protocols of the Service Control Manager, the component responsible for managing Windows services. It is the Services and Controller app, services.exe, that launches all the services and manages their actions, such as start, end, etc.
Windows services can be configured to start when the operating system is started and run in the background as long as Windows is running. Alternatively, they can be started manually or by an event. Windows NT operating systems include numerous services which run in context of three user accounts: System, Network Service and Local Service. These Windows components are often associated with Host Process for Windows Services. Because Windows services operate in the context of their own dedicated user accounts, they can operate when a user is not logged on.
Prior to Windows Vista, services installed as an "interactive service" could interact with Windows desktop and show a graphical user interface. In Windows Vista, however, interactive services are deprecated and may not operate properly, as a result of Windows Service hardening.
Windows administrators can manage services via:
- The Services snap-in (found under Administrative Tools in Windows Control Panel)
- Windows PowerShell
- view a list of installed services along with service name, descriptions and configuration
- start, stop, pause or restart services
- specify service parameters when applicable
- change the startup type. Acceptable startup types include:
- Automatic: The service starts at system logon.
- Automatic (Delayed): The service starts a short while after the system has finished starting up. This option was introduced in Windows Vista in an attempt to reduce the boot-to-desktop time. However, not all services support delayed start.
- Manual: The service starts only when explicitly summoned.
- Disabled: The service is disabled. It will not run.
- change the user account context in which the service operates
- configure recovery actions that should be taken if a service fails
- inspect service dependencies, discovering which services or device drivers depend on a given service or upon which services or device drivers a given service depends
- export the list of services as a text file or as a CSV file
sc command's scope of management is restricted to the local computer. However, starting with Windows Server 2003, not only can
sc do all that the Services snap-in does, but it can also install and uninstall services.
|Name||Description||Windows support||ReactOS support|
|query||Show service status||Yes||Yes|
|queryex||Show extended service info (e.g. pid, flags)||Yes||Yes|
|start||Start a service||Yes||Yes|
|pause||Pause a service||Yes||Yes|
|continue||Continue a service||Yes||Yes|
|stop||Stop a service||Yes||Yes|
|description||Change a service description||Yes||Yes|
|qc||Show the service config (e.g. dependencies, full path etc.)||Yes||Yes|
|qdescription||Query a service description||Yes||Yes|
|delete||Delete a service||Yes||Yes|
|create||Create a service||Yes||Yes|
|GetDisplayName||Show the service DisplayName||Yes||Yes|
|GetKeyName||Show the service ServiceKeyName||Yes||Yes|
|EnumDepend||Show the service Dependencies||Yes||Yes|
The following example enumerates the status for active services & drivers.
C:\>sc query eventlog
The Microsoft.PowerShell.Management PowerShell module (included with Windows) has several cmdlets which can be used to manage Windows services:
Other management toolsEdit
Windows also includes components that can do a subset of what the snap-in, Sc.exe and PowerShell do. The
net command can start, stop, pause or resume a Windows service. In Windows Vista and later, Windows Task Manager can show a list of installed services and start or stop them. MSConfig can enable or disable (see startup type description above) Windows services.
Windows services are installed and removed via *.INF setup scripts by SetupAPI; an installed service can be started immediately following its installation, and a running service can be stopped before its deinstallation.
Writing native servicesEdit
For a program to run as a Windows service, the program needs to be written to handle service start, stop, and pause messages from the Service Control Manager (SCM) through the System Services API. SCM is the Windows component responsible for managing service processes.
Wrapping applications as a serviceEdit
The Windows Resource Kit for Windows NT 3.51, Windows NT 4.0 and Windows 2000 provides tools to control the use and registration of services:
SrvAny.exe acts as a service wrapper to handle the interface expected of a service (e.g. handle service_start and respond sometime later with service_started or service_failed) and allow any executable or script to be configured as a service.
Sc.exe allows new services to be installed, started, stopped and uninstalled.
- Windows services
- "Services overview". TechNet. Microsoft. Retrieved 29 March 2013.
- "Services". Microsoft Developer Network. Microsoft. Retrieved 29 March 2013.
- "New Elevation PowerToys for Windows Vista". TechNet Magazine. Microsoft. June 2008. Retrieved 21 June 2013.
The service CmdAsSystem is configured as interactive whose support is being deprecated. The service may not function properly. The problem is that this script tries to create and start an interactive service. Interactive services will not function correctly due to Session 0 Isolation in Windows Vista.
- "Services in Windows". MSDN. Microsoft. 18 October 2010. Retrieved 21 June 2013.
- "Start, stop, pause, resume, or restart a service". TechNet. Microsoft. Retrieved 29 March 2013.
- "ServiceInstaller.DelayedAutoStart Property (System.ServiceProcess)". Microsoft. Retrieved 28 November 2017See Remarks sectionCS1 maint: postscript (link)
- "How to create a Windows service by using Sc.exe". Support. Microsoft. 11 September 2011. Retrieved 29 March 2013.
- "Command-line reference A-Z: SC". TechNet. Microsoft. Retrieved 8 January 2014.
- "Command-Line Reference: Sc". TechNet. Microsoft. Retrieved 8 January 2014.
Windows 7, Windows 8, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Vista
- SC - Service Control - Windows CMD - SS64.com
- reactos/sc.c at master · reactos/reactos · GitHub
- MS-DOS and Windows command line sc command
- "Get-Service". TechNet. Microsoft. Retrieved 29 March 2013.
- "New-Service". TechNet. Microsoft. Retrieved 29 March 2013.
- "Restart-Service". TechNet. Microsoft. Retrieved 29 March 2013.
- "Resume-Service". TechNet. Microsoft. Retrieved 29 March 2013.
- "Set-Service". TechNet. Microsoft. Retrieved 29 March 2013.
- "Start-Service". TechNet. Microsoft. Retrieved 29 March 2013.
- "Stop-Service". TechNet. Microsoft. Retrieved 29 March 2013.
- "Suspend-Service". TechNet. Microsoft. Retrieved 29 March 2013.
- "Start, stop, pause, resume, or restart a service". TechNet. Microsoft. Retrieved 8 January 2014.
- "INF AddService Directive". Microsoft. Retrieved 10 July 2017.
- "SetupInstallServicesFromInfSection function". MSDN. Microsoft. Retrieved 10 July 2017.
- "SetupInstallServicesFromInfSectionEx function". MSDN. Microsoft. Retrieved 10 July 2017.
- "How To Create a User-Defined Service". Support. Microsoft. Retrieved 29 March 2013.
- Savill, John (5 March 1999). "What are the ErrorControl, Start and Type values under the Services subkeys?". Windows IT Pro. Penton Media. Retrieved 29 March 2013.
- David B. Probert, Windows Service Processes
|Wikibooks has a book on the topic of: Guide to Windows Commands|
- Windows Sysinternals: Autoruns for Windows v13.4 – An extremely detailed query of services
- Service Management With Windows Sc From Command Line – Windows Service Management Tutorial
- Windows Service Manager Tray