Windows Server 2016 – NIC RSS and VMQ driver mismatch causes packet loss – Fix and 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

Intermittent packet drops and jitter affect app traffic.

Environment & Reproduction

Appears after NIC driver updates on Hyper-V hosts.

Get-NetAdapter
Get-NetAdapterRss
Get-NetAdapterVmq

Root Cause Analysis

Driver defaults changed queue behavior and affinity.

Quick Triage

Validate RSS/VMQ/interrupt settings against baseline.

Step-by-Step Diagnosis

Capture packet errors and queue allocation.

Get-NetAdapterStatistics -Name '*'

Solution — Primary Fix

Apply stable driver and rebalance queue settings.

Disable-NetAdapterVmq -Name 'Ethernet 2'
Enable-NetAdapterRss -Name 'Ethernet 2'

Solution — Alternative Approaches

Temporarily disable VMQ while validating corrected package.

Verification & Acceptance Criteria

Packet errors stay near zero at peak.

Rollback Plan

Roll back to last known-good NIC package.

Prevention & Hardening

Use adapter tuning templates per hardware model.

Related Errors & Cross-Refs

Often co-occurs with heartbeat misses and SMB instability.

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

View all Windows Server 2016 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

RSS/VMQ tuning guidance for Hyper-V.