Built by IT engineers, made for IT teams.
Best PracticesNovember 20, 2026· 5 min read

Restart a Windows Service Automatically If It Stops

A program feature suddenly stops working because a background service stopped? Find the service and have Windows restart it automatically from now on.

Nico Haslberger
Nico HaslbergerCEO & Co-Founder · November 20, 2026
Share
Windows-Dienst automatisch neu starten, wenn er stoppt

The ERP no longer sends files. Not because it is broken, but because a service silently stopped.

“Files can no longer be sent from the ERP.” That was the report from the sales department of a machine manufacturer. The program itself was running, orders could be processed – only sending documents failed. The cause was not at the workstation and not in the ERP itself: on the server of the connected document management system, a process service had stopped. After the service was started, the message soon followed: “It works again, according to our ladies.”

Cases like this repeat if you only start the service. Here is how you find the service – and make sure Windows restarts it on its own in the future.

Why does only one function fail although the program is running?

Because many functions do not run in the program itself, but in a service in the background. ERP and line-of-business programs hand tasks such as sending, archiving, printing or importing to a service on a server. If that service is not running, the user notices it in exactly one place – often with a meaningless error message.

Typical examples:

  • Sending from ERP or inventory management → mail or DMS service
  • Archiving or filing documents → document management service
  • Scanning to folder → scan or import service
  • Automatic exports or interfaces → job or interface service
Restart a Windows Service Automatically If It Stops – at a glance
Restart a Windows Service Automatically If It Stops – at a glance

Step 1: Find the stopped service

On the affected server, list all automatically starting services that are not running:

Get-CimInstance Win32_Service |
  Where-Object { $_.StartMode -eq 'Auto' -and $_.State -ne 'Running' } |
  Select-Object Name, DisplayName, State

Some Windows services regularly show up there because they exit after finishing their work (such as update services). The interesting ones are the services of the line-of-business application's vendor – usually recognizable by the name.

Graphically: Windows+R › services.msc › sort by Status and Startup type.

Step 2: Start the service and check

Start-Service -Name "DienstName"
Get-Service -Name "DienstName"

Then have the user test the function. If the service does not start, Event Viewer usually shows the reason – such as an expired password of the service account or an unreachable database.

Step 3: Find out why it stopped

In the System log of Event Viewer (Windows Logs › System), look for these events:

  • 7034 – Service terminated unexpectedly
  • 7031 – Service terminated unexpectedly, recovery action follows
  • 7036 – Service changed state (started/stopped)
  • 7000 / 7009 – Service failed to start / timeout
  • 7038 – Service account logon failed

With PowerShell:

Get-WinEvent -FilterHashtable @{LogName='System'; Id=7031,7034,7036,7038} -MaxEvents 30 |
  Where-Object Message -match "DienstName" | Select-Object TimeCreated, Id, Message

Common causes: a server restart after which the service started too early and could not yet reach its database, a crash of the application, or a changed password of the service account.

Step 4: Set up automatic restart

Graphically: services.msc › service › Properties › Recovery tab:

  • First failure: Restart the Service
  • Second failure: Restart the Service
  • Subsequent failures: Restart the Service
  • Reset fail count after: 1 day
  • Restart service after: 1 minute
  • Check Enable actions for stops with errors

On the command line (as administrator; the spaces after = are mandatory):

14 days free

IT support that fixes itself.

SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.

Start free trial
sc.exe failure "DienstName" reset= 86400 actions= restart/60000/restart/60000/restart/300000
sc.exe failureflag "DienstName" 1
sc.exe qfailure "DienstName"

With this, Windows restarts the service after one minute following a crash, and after five minutes the third time.

Important: Recovery only applies to crashes and stops with an error. If someone stops the service manually, it stays stopped.

Step 5: Adjust the startup type

If the service starts too early after a server restart, delayed start helps:

sc.exe config "DienstName" start= delayed-auto

Graphically: Properties › Startup type › Automatic (Delayed Start). The service then starts about two minutes after boot – when network and database are ready.

If the service depends on another service (such as SQL Server), you can also enter the dependency permanently – but you should coordinate that with the application's vendor.

Step 6: Monitor instead of waiting

Ideally, IT notices the stopped service before users call.

  • RMM or monitoring: Set up service monitoring for the most important line-of-business application services.
  • Task Scheduler: A scheduled task that reacts to event 7034 and sends an email or starts the service.
  • Documentation: Which function depends on which service on which server? That saves the search next time. In the real-world case, exactly that was in the MSP's documentation.

Similar cases where the cause is not at the workstation: Windows Server shuts down every hour and .NET runtime versions do not match.

Example view in SuperSupport – Restart a Windows Service Automatically If It Stops
Example view in SuperSupport – Restart a Windows Service Automatically If It Stops

How does SuperSupport help with cases like these?

At the workstation, the SuperSupport agent can check whether the program itself is running and whether the associated server is reachable – and so narrow down that the problem is not with the PC. IT receives a case noting which function is affected, instead of a general report “ERP doesn't work”. Services on servers are still started by IT. What this looks like for internal IT teams and MSPs is described on the respective pages.

Restart a Windows Service Automatically If It Stops – frequently asked questions
Restart a Windows Service Automatically If It Stops – frequently asked questions

Frequently asked questions

How do I make a Windows service restart automatically?

In the Services console (services.msc), open the service's Properties › Recovery tab and choose “Restart the Service” for the first failure, the second failure and all subsequent failures. On the command line, use sc.exe failure with the actions you want.

Why doesn't my service restart despite the recovery option?

Recovery only applies if the service crashes. If it exits seemingly cleanly with an error code, you also need the option “Enable actions for stops with errors” (sc.exe failureflag service 1). If the service is stopped manually, Windows does not restart it.

How do I know a service has crashed?

In the System log of Event Viewer: Event 7034 means a service terminated unexpectedly, 7031 additionally means a recovery action is being run. 7036 shows every status change.

What is “Automatic (Delayed Start)”?

The service does not start immediately with Windows but shortly afterward. This helps with services that depend on a database or the network that are not yet ready at startup.

Why do you only notice the stopped service in one program?

Many programs – ERP, document management, scan or mail functions – rely on services on a server. If the service is not running, the program works in general, but a single function such as sending or archiving fails.

14 days free

IT support that fixes itself.

SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.

Start free trial
Nico Haslberger

Nico Haslberger is Co-Founder & CEO of SuperSupport.ai. With years of experience as an IT technician, he knows the problems in IT support first-hand: from overloaded help desks to recurring tickets that slow teams down. That knowledge is built into every feature of the platform today. He makes sure SuperSupport.ai solves exactly the problems he experienced himself for years.

Share

This article was created with AI assistance and editorially reviewed.

Related Articles