Skip to main content

How to Restart a Windows Service in Batch Script

Restarting a Windows Service is one of the most common tasks in system administration and automated maintenance. Whether you are clearing a hung print spooler, applying a configuration change to a database, or refreshing a custom background agent, knowing how to perform a "clean" restart via a script is essential. Unlike a manual restart in the GUI, a Batch script must handle the timing between stopping and starting to ensure the process completes successfully.

This guide will explain how to use native Windows commands to restart services reliably, including a robust method to wait for the service to fully clear before starting it again.

The Basic Method: NET STOP and NET START​

The most straightforward way to restart a service is to use the net command suite. This method involves two distinct steps: stopping the service and then starting it back up.

Basic Implementation​

@echo off
set "ServiceName=Spooler"

echo [ACTION] Stopping %ServiceName%...
net stop "%ServiceName%"

echo [ACTION] Starting %ServiceName%...
net start "%ServiceName%"

if %errorlevel% equ 0 (
    echo [SUCCESS] Service restart complete.
) else (
    echo [ERROR] Service failed to start. Ensure you are running as Administrator.
)

pause

The "Access Denied" Problem​

Service management is a protected system action. If you try to run these commands from a standard command prompt, you will receive an "Access Denied" or "System error 5 has occurred" message.

warning

Administrator Privileges Required. Always right-click your Batch script and select "Run as Administrator". Without elevation, the script cannot communicate with the Service Control Manager.

The Challenge: Dealing with Timing Issues​

A major pitfall of using simple net commands in a sequence is that net stop returns a success message as soon as the signal is sent, but the service might still be "Stopping" in the background for several seconds. If your script immediately tries to run net start, it will fail because the service is still flagged as active.

The Wrong Way (Unreliable)​

:: BAD PRACTICE: This often fails for heavy services
net stop MSSQLSERVER
net start MSSQLSERVER

Why it fails: Heavy services like SQL Server or Exchange take time to flush their memory and close file handles. The second command executes too quickly, resulting in an error like: "The service is starting or stopping. Please try again later."

The Professional Way: A Robust Restart Script​

To create a truly reliable restart script, you should use a loop that checks the service status and waits for it to reach the STOPPED state before proceeding to the start command.

Robust Restart Logic​

@echo off
setlocal
set "svc=Spooler"
set "MaxWait=30"
set "WaitCount=0"

:: Verify the service exists
sc query "%svc%" >nul 2>&1
if %errorlevel% neq 0 (
    echo [ERROR] Service '%svc%' does not exist.
    pause
    exit /b 1
)

echo [1/3] Attempting to stop %svc%...
net stop "%svc%" /y >nul 2>&1

:CheckStop
:: Use SC to query the specific state
sc query "%svc%" | findstr /i "STOPPED" >nul
if %errorlevel% equ 0 (
    echo [2/3] Service successfully stopped.
    goto :DoStart
)

set /a WaitCount+=2
if %WaitCount% gtr %MaxWait% (
    echo [ERROR] Timed out waiting for service to stop after %MaxWait% seconds.
    echo         The service may be hung. Manual intervention required.
    pause
    exit /b 1
)

echo [WAIT] Service is still stopping... (%WaitCount%s / %MaxWait%s^)
timeout /t 2 /nobreak >nul
goto :CheckStop

:DoStart
echo [3/3] Starting %svc%...
net start "%svc%"

if %errorlevel% equ 0 (
    echo [SUCCESS] Service '%svc%' is back online.
) else (
    echo [ERROR] Could not start service. Check the Windows Event Viewer for details.
)

pause
endlocal

Explaining the Robust Logic:​

  1. net stop "%svc%" /y: The /y flag automatically answers "Yes" to any prompts (for example, if stopping this service also stops dependent services).
  2. sc query | findstr /i "STOPPED": This treats the status output as data. The script won't move forward until the word "STOPPED" is detected.
  3. timeout /t 2: This prevents the script from consuming 100% of the CPU while it waits. It checks the status every 2 seconds.
  4. Timeout guard: Prevents the script from looping forever if the service is truly hung.

Practical Example: Clearing a Hung Service​

Sometimes a service is "hung" in a "Stopping" or "Starting" state and won't respond to net stop. In these extreme cases, you may need to find the specific process ID (PID) and force it to close before you can start it again.

@echo off
setlocal enabledelayedexpansion
set "svc=MyHungService"

:: Verify the service exists
sc query "%svc%" >nul 2>&1
if %errorlevel% neq 0 (
    echo [ERROR] Service '%svc%' does not exist.
    pause
    exit /b 1
)

echo [ACTION] Attempting graceful stop of %svc%...
net stop "%svc%" /y >nul 2>&1

:: Wait briefly for graceful stop
timeout /t 5 /nobreak >nul

:: Check if it stopped gracefully
sc query "%svc%" | findstr /i "STOPPED" >nul
if %errorlevel% equ 0 (
    echo [OK] Service stopped gracefully.
    goto :StartSvc
)

echo [WARNING] Service did not stop gracefully. Force-killing process...

:: Find the PID associated with the service
set "spid="
for /f "tokens=2" %%a in ('sc queryex "%svc%" ^| findstr /i "PID"') do set "spid=%%a"

if not defined spid (
    echo [ERROR] Could not determine service PID.
    pause
    exit /b 1
)

if "!spid!"=="0" (
    echo [INFO] Service process is not running (PID is 0^).
) else (
    echo [ACTION] Terminating PID: !spid!
    taskkill /f /pid !spid!
    timeout /t 2 /nobreak >nul
)

:StartSvc
echo [ACTION] Starting %svc%...
net start "%svc%"

if %errorlevel% equ 0 (
    echo [SUCCESS] Service '%svc%' is back online.
) else (
    echo [ERROR] Could not start service after force-kill.
    echo         Check the Windows Event Viewer for details.
)

pause
endlocal

Best Practices and Security Rules​

1. Monitor Dependencies​

Before restarting a service, check if other services depend on it. Restarting the "Workstation" service, for example, will stop several network-related services that might not restart automatically.

2. Check for Service Existence​

Always verify the service is installed before trying to restart it to avoid error messages that confuse the user.

sc query "%svc%" >nul 2>&1
if %errorlevel% neq 0 (
    echo Service not found!
    exit /b 1
)

3. Log the Restart Events​

In a production environment, it is helpful to log when a restart was triggered, especially if it's part of a scheduled task.

echo %date% %time% - Restarted %svc% >> C:\Logs\service_restarter.log

How to Avoid Common Errors​

Problem: Service name with spaces​

If your service name has spaces (e.g., "SQL Server (MSSQLSERVER)"), your commands will fail if you don't use quotes.

Correct Way:

net stop "SQL Server (MSSQLSERVER)"

Best Practice: Silent Operation​

If you are running this as a background task, you can hide the output and just check the exit codes.

net stop "Spooler" >nul 2>&1

Conclusions​

Restarting a Windows Service via Batch script is a dual-process of communication and patience. While net stop and net start provide the basic foundation, incorporating a status-check loop using sc query is the key to creating professional-grade automation that doesn't fail due to timing issues. By following the "Wait for Stop" pattern, you ensure that your services are refreshed cleanly and reliably every time.

Table of Contents