Windows Server 2022 – Static routes disappearing after network adapter reset – 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

Inter-subnet traffic drops after interface reset because persistent routes are missing at runtime.

Environment & Reproduction

Usually triggered by NIC driver updates, interface rebinds, or VM mobility events.

Get-NetRoute -AddressFamily IPv4
Get-NetIPInterface
route print

Root Cause Analysis

Routes were added as temporary entries, tied to old interface indexes, or removed by configuration automation.

Quick Triage

Compare expected vs active routes and interface metrics.

Get-NetRoute | Sort DestinationPrefix
Get-NetIPInterface | Select InterfaceAlias,InterfaceIndex,InterfaceMetric
Get-WinEvent -LogName System -MaxEvents 20

Step-by-Step Diagnosis

Verify route persistence and interface binding consistency.

Get-NetRoute -PolicyStore PersistentStore
Get-NetAdapter
Get-NetIPConfiguration

Solution – Primary Fix

Recreate required persistent routes bound to current interface indexes.

New-NetRoute -DestinationPrefix 10.20.0.0/16 -InterfaceIndex 12 -NextHop 10.0.0.1 -PolicyStore PersistentStore
New-NetRoute -DestinationPrefix 10.30.0.0/16 -InterfaceIndex 12 -NextHop 10.0.0.1 -PolicyStore PersistentStore

Solution – Alternative Approaches

Use startup scripts or DSC to enforce route state after interface changes.

route -p add 10.40.0.0 mask 255.255.0.0 10.0.0.1
route -p add 10.50.0.0 mask 255.255.0.0 10.0.0.1

Verification & Acceptance Criteria

All required routes persist across reboot and interface bounce.

Get-NetRoute -PolicyStore PersistentStore
Restart-Computer -Force

Rollback Plan

Remove added routes if they conflict with dynamic routing protocols or policy.

Remove-NetRoute -DestinationPrefix 10.20.0.0/16 -Confirm:$false
Remove-NetRoute -DestinationPrefix 10.30.0.0/16 -Confirm:$false

Prevention & Hardening

Track route inventory and automate drift detection.

Get-NetRoute | Export-Csv routes-baseline.csv -NoTypeInformation

Related Errors & Cross-Refs

Can overlap with RRAS misconfiguration, firewall profile changes, and NIC team failover events.

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: Windows routing cmdlets and persistent route management.