我为服务配置了两个重启操作和一个 60 秒的重置期限：
sc 失败 SPOOLER 重置 = 60 操作 = 重新启动/1000/重新启动/1000//1000
预期是，当服务被终止两次后，不再执行重新启动。但是，在再次手动启动服务并使其运行至少重置时间后，它应该在下次故障后自动重新启动。
该行为与 Windows Server 2012 的预期一致。
但是 Windows Server 2016 有所不同，在重启操作用尽后，如果手动启动服务，则在发生故障后不会重新启动。
这是一个真正的问题。想象一下，在配置更改导致失败后启动服务。服务将很快失败，直到所有重新启动操作都用尽。然后您可能会修复配置并手动重新启动服务。下次服务失败时，无论它已成功运行多长时间，都不会重新启动。
请查看下面的事件日志。
有人遇到过同样的情况吗？这是 Windows 2016 服务管理器中的错误吗？
事件日志 Windows Server 2012：服务管理器重新启动了该服务两次。第三次失败后，没有重新启动。然后，大约 2 分钟后，手动重新启动，不久后被终止 -> 自动重新启动。
04.12.2018 08:18:42: The Print Spooler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.
04.12.2018 08:18:43: The Print Spooler service entered the running state.
04.12.2018 08:18:51: The Print Spooler service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.
04.12.2018 08:18:52: The Print Spooler service entered the running state.
04.12.2018 08:19:03: The Print Spooler service terminated unexpectedly. It has done this 3 time(s).
04.12.2018 08:19:16: The Print Spooler service entered the running state.
04.12.2018 08:21:24: The Print Spooler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.
04.12.2018 08:21:25: The Print Spooler service entered the running state.
事件日志 Windows Server 2016：服务管理器重新启动了两次服务。第三次失败后，没有重新启动。然后，大约 3 分钟后，手动重新启动，并在不久后终止 ->不执行自动重启。
12/4/2018 8:02:36 AM: The Print Spooler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.
12/4/2018 8:02:37 AM: The Print Spooler service entered the running state.
12/4/2018 8:02:45 AM: The Print Spooler service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service.
12/4/2018 8:02:46 AM: The Print Spooler service entered the running state.
12/4/2018 8:02:53 AM: The Print Spooler service terminated unexpectedly. It has done this 3 time(s).
12/4/2018 8:03:06 AM: The Print Spooler service entered the running state.
12/4/2018 8:05:08 AM: The Print Spooler service terminated unexpectedly. It has done this 1 time(s).