Windows Server / Services, IIS & Secure Operations
Check service recovery policy when a server repeatedly restarts a failing process
Automatic restart can make a broken service appear intermittently healthy while it generates repeated failures. Preserve the underlying error and configured recovery actions.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
sc.exe qfailure AppServiceRead the result
In a Windows terminal, the command reads recovery actions for the named service. It does not identify why the process fails or whether the application is safe to restart.
Resolve and verify
Compare crash times with recovery intervals and application evidence. Fix the root cause and review bounded recovery behavior with the service owner.
Before changing production
Do not configure an endless restart loop or a machine reboot action to hide a deterministic application fault.