Windows Server / Services, IIS & Secure Operations
Inspect an IIS application pool before recycling it
Repeated pool stops can reflect rapid-fail protection, identity problems or application crashes. Capture state and the associated event errors.
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.
Get-WebAppPoolState -Name 'AppPool'Read the result
With WebAdministration available, the result reports the selected pool's current state. It does not explain the failure history or prove a running worker is serving requests.
Resolve and verify
Correlate WAS and application events with the stop, then inspect identity, runtime and recent deployment changes. Repair the cause and perform a controlled restart if approved.
Before changing production
Do not disable rapid-fail protection or repeatedly recycle the pool without preserving crash evidence.