Windows Server 2022 — Windows Containers Fail to Start Due to HNS Network Creation Error — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Quick Checks
3. Deep Diagnosis
4. Primary Fix
5. Verification
6. Prevention & Hardening

Symptom & Impact

Container deployments fail at startup when Host Network Service cannot create or attach endpoint networks. CI/CD pipelines stall and microservices remain offline. Repeated network object corruption can affect all future deployments on the host.

Quick Checks

Validate HNS service state, Docker/containerd runtime status, and existing network object inventory.

Get-Service hns,docker
docker network ls
Get-HnsNetwork | ConvertTo-Json -Depth 5

Deep Diagnosis

Review HNS operational logs and virtual switch bindings for stale or duplicate network definitions.

Get-WinEvent -LogName 'Microsoft-Windows-Host-Network-Service-Admin' -MaxEvents 150
Get-VMSwitch
Get-NetAdapterBinding -Name '*' | Where-Object {$_.ComponentID -match 'vms_pp'}

Primary Fix

Purge corrupted HNS networks, restart services, and recreate known-good NAT or transparent networks.

Get-HnsNetwork | Remove-HnsNetwork
Restart-Service hns
Restart-Service docker
docker network create -d nat nat

Verification

New containers should start and obtain expected network connectivity without endpoint creation errors.

docker run --rm mcr.microsoft.com/windows/nanoserver:ltsc2022 cmd /c ver
docker network inspect nat
Test-NetConnection 8.8.8.8 -Port 53

Prevention & Hardening

Freeze runtime versions per cluster and validate host network cleanup in lifecycle automation.

docker version
Get-HnsEndpoint | Measure-Object
Get-Service hns,docker