🧡 Skip to main content🔍 Skip to search

The Start & Stop Service Action allows for the automation of all Windows service status changes, including starting, stopping, pausing, resuming, and restarting services.

Create no-code workflows with a few easy mouse clicks to intelligently start, stop, or restart a service and all its dependent services. Automation Workshop detects and manages dependent services fully automatically.

ServiceDetails
ServiceSelect a service to manage. Choose it from the list, or type a service name, or use a variable. Kernel and filesystem drivers are also supported:
  • Simple · a list of all installed services, including kernel and filesystem drivers. The list is split into 4 parts and sorted by service display name in the alphabetic order: normal services, "hexadecimal" services, kernel drivers, and file system drivers.
  • Dynamic · provide a service name or display name (usually from a file or dynamic variable).
Service infoShows the current status of a service, for example:
  • The service "MSSQLSERVER" is currently running.
  • The "Cryptographic Service" is currently stopped.

The tooltip displays extended service information in real-time.
Activity Choose a service management activity:
  • Start service
  • Stop service
  • Stop service + linked services · stops a service and all its dependencies
  • Restart service
  • Restart service + linked services · restart a service and all its dependencies
  • Pause service
  • Resume service
Parameters If the Start service activity is selected, it is possible to provide startup parameters. These parameters are passed to the ServiceMain function and should not be confused with the command-line arguments passed during the service executable's startup. Note that drivers do not support startup parameters.
Reason An optional service stopping reason that is logged in the Event Log and can later be queried or observed in the Event Viewer · Preview
  • None
  • Planned
  • Unplanned
Major Provide an optional major service stopping reason:
  • Hardware
  • Operating system
  • Software
  • Application
  • Other
Details An optional minor service stopping reason:
  • Unstable
  • Unresponsive
  • Maintenance
  • Reconfigure
  • Upgrade
  • Installation
  • Security
  • Security update
  • Software update
  • Service pack
  • Environment
  • Disk
  • Network card
  • Networking
  • Driver
  • MMC · Microsoft Management Console
  • WMI · Windows Management Instrumentation
  • Other
Comment An optional comment for the stop service operation. The maximum length of the comment is 127 characters.
Variable WizardVariable Wizard buttonUse dynamic data input—substitute a parameter from a file, web, connected Trigger, other Actions, date and time presets, etc.
YouTube video · Auto-restart Windows services

Interconnect

  • Start & Stop Service integration and auditing—Variables (dynamic data) and Events (recorded activity). After the Action runs, you can access the current and previous status of the Windows service, along with its short and long names, and its executable file.

    Additionally, detailed information is logged, including the operation performed, the service's current status, any timeouts, and ongoing operations.

More service controls…

Automation Workshop provides a comprehensive set of options to monitor and manage Windows services. These tools allow you to start, stop, pause, and resume services automatically. Additionally, you can retrieve real-time information about one or multiple services, enabling efficient system management and automation.

Notes

  • The start service activity automatically starts all dependencies (linked services), however, this is not reflected in the service.log file. On the other hand, the stop service activity logs all stopped dependencies, if any.
  • The pause and resume activities are only supported if the selected service is specifically designed to support them.
  • When working with kernel and filesystem drivers, consult the documentation for the specific driver to see which activities are supported.
  • It's important to note that service management is a complex task, however, Automation Workshop allows you to create automated workflows without writing complex scripts or custom apps. It's always recommended to test the service automation in a non-production environment before implementing it in production.
  • By default, Windows Servers have the ability to log the stopping reasons when services are stopped, while this feature is not enabled on Windows workstations.
  • The same stopping reason is also logged for all dependencies (linked services) that are stopped during the specific service stop procedure.

Event Viewer…

When a Windows service is stopped with a reason, it is logged in the Windows Event Log under the System logs category. The default source for these events is the Service Control Manager, and they are logged with event ID 7042.

Event Viewer · Windows Logs · System · Service Control Manager
Event Viewer · Windows Logs · System

The Event Properties window shows detailed information about the logged stop reason. The textual part displays the service's display name and your specified stopping reason in both hexadecimal and textual formats. Your provided comment is also displayed here.

Event Properties · Event 7042, Service Control Manager
Event Properties · Event 7042 · Service Control Manager

Additional details such as a computer name and the exact date and time of the event are also displayed there. Usually, it is enough to select a standard service stop reason from the system-predefined values, however, the comment field allows you to pass any custom text that can be generated automatically at runtime using Variable Wizard.

The art of automation. A 90-second journey.

Questions?

If you have any questions, please do not hesitate to contact our support team.