Windows Server 2022 — WinRM HTTPS listener fails to bind on Windows Server 2022 — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

WinRM HTTPS listener fails to bind on Windows Server 2022 on Windows Server 2022 disrupts operations and prevents the affected service from meeting its SLA until remediated.

Environment & Reproduction

The issue reproduces on Windows Server 2022 hosts where the monitoring subsystem is in use, typically following configuration drift or recent updates.

Get-ChildItem Cert:LocalMachineMy | Where EnhancedKeyUsageList -like '*Server Auth*'
Test-NetConnection localhost -Port 5986

Root Cause Analysis

The defect stems from misaligned winrm listeners settings, missing prerequisites, or a corrupted state that blocks normal operation.

Quick Triage

Confirm the service is running and capture current configuration state before applying any change.

winrm get winrm/config
Get-NetTCPConnection -LocalPort 5986

Step-by-Step Diagnosis

Walk the monitoring stack from configuration to runtime, collecting logs and counters that point at the failing component.

winrm enumerate winrm/config/listener
Get-WinEvent -LogName 'Microsoft-Windows-WinRM/Operational' -MaxEvents 30

Solution — Primary Fix

Apply the corrected configuration and restart dependent services so the winrm listeners component re-initialises cleanly.

$cert = New-SelfSignedCertificate -DnsName $env:COMPUTERNAME -CertStoreLocation Cert:LocalMachineMy
winrm delete winrm/config/Listener?Address=*+Transport=HTTPS
New-Item -Path WSMan:localhostListener -Transport HTTPS -Address * -CertificateThumbPrint $cert.Thumbprint -Force
Restart-Service WinRM

Solution — Alternative Approaches

Where the primary fix is blocked by policy or downtime windows, use the alternative configuration path or staged rollout below.

winrm create winrm/config/Listener?Address=*+Transport=HTTPS '@{Hostname="server01.contoso.com";CertificateThumbprint="ABCD1234"}'
New-NetFirewallRule -DisplayName 'WinRM-HTTPS' -Direction Inbound -LocalPort 5986 -Protocol TCP -Action Allow

Verification & Acceptance Criteria

Confirm the service reports healthy state and end-to-end functionality succeeds against a representative workload.

Test-WSMan -ComputerName localhost -UseSSL
winrm enumerate winrm/config/listener

Rollback Plan

If the fix introduces regressions, revert configuration to the pre-change baseline and restart the service to restore prior behaviour.

winrm delete winrm/config/Listener?Address=*+Transport=HTTPS
winrm quickconfig

Prevention & Hardening

Bake the validated winrm listeners configuration into baseline GPOs or DSC and add a monitoring check for early detection.

Set-Item WSMan:localhostServiceAllowUnencrypted -Value $false
New-ScheduledTask -Action (New-ScheduledTaskAction -Execute 'powershell.exe' -Argument 'Check-WinRMCertExpiry.ps1')

Related Errors & Cross-Refs

Related: other monitoring failures, dependent service errors, and downstream client-side symptoms.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Windows Server 2022 and the relevant component, plus internal runbooks.