Windows Server 2022 — Static routes disappear after NIC metric changes — 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

Traffic to branch networks fails after reboot or adapter updates because persistent routes are missing.

Environment & Reproduction

Windows Server 2022 build 20348 with multiple adapters and manually maintained routes.

route print
Get-NetRoute -AddressFamily IPv4 | Sort-Object DestinationPrefix,RouteMetric
Get-NetIPInterface | Select InterfaceAlias,InterfaceMetric

Root Cause Analysis

Routes were added as active-only entries or attached to changing interface indexes.

Quick Triage

Check whether required routes are persistent and bound to correct next hop.

reg query HKLMSYSTEMCurrentControlSetServicesTcpipParametersPersistentRoutes
Get-NetRoute -DestinationPrefix 10.20.0.0/16

Step-by-Step Diagnosis

Audit route persistence and interface index drift after updates.

Get-NetAdapter | Select Name,InterfaceDescription,InterfaceIndex,Status
Get-NetRoute | Where-Object DestinationPrefix -eq '10.20.0.0/16'

Solution — Primary Fix

Recreate persistent routes with stable next-hop and metric values.

route -p add 10.20.0.0 mask 255.255.0.0 10.10.1.1 metric 10
Set-NetIPInterface -InterfaceAlias 'LAN' -InterfaceMetric 10
Set-NetIPInterface -InterfaceAlias 'WAN' -InterfaceMetric 50

Solution — Alternative Approaches

Automate route restore at startup with signed script task.

$routes = @('10.20.0.0/16','10.30.0.0/16')
foreach ($r in $routes) { New-NetRoute -DestinationPrefix $r -InterfaceAlias 'LAN' -NextHop 10.10.1.1 -PolicyStore PersistentStore }

Verification & Acceptance Criteria

Route table remains correct after restart.

Restart-Computer -Force
route print
Test-NetConnection 10.20.1.10 -TraceRoute

Rollback Plan

Remove new routes and restore previous metric profile.

route delete 10.20.0.0
Set-NetIPInterface -InterfaceAlias 'LAN' -AutomaticMetric Enabled

Prevention & Hardening

Keep route definitions in source-controlled scripts and run post-patch validations.

Export-Clixml -InputObject (Get-NetRoute) -Path C:Temproutes.xml

Related Errors & Cross-Refs

Related to asymmetric routing and firewall stateful drop behavior.

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 static routing management and interface metric behavior.