Windows Server 2025 NIC Teaming Adapter Shows as Disconnected After Update — Fix & Prevention

📖 ~2 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

After applying a Windows Server 2025 cumulative update or upgrading a NIC driver, the LBFO (Load Balancing/Failover) NIC team shows as ‘Degraded’ or ‘Down’ in Network Connections, and the team adapter’s connection speed drops from the expected aggregate to zero or single-member speed. Server applications experience network interruption, and the IP address associated with the team becomes unreachable. The issue is particularly impactful on production servers where NIC teaming provides the primary network redundancy — losing the team means losing the failover capability and potentially the primary connection.

Environment & Reproduction

Occurs on Windows Server 2025 when: (1) A NIC driver update changes the adapter name or GUID, invalidating the team member reference. (2) A Windows update modifies LBFO service (netio.sys) in a way that conflicts with the installed driver version. (3) A physical NIC is replaced with a different model and the team is not rebuilt.

# Check team status
Get-NetLbfoTeam
Get-NetLbfoTeamMember
Get-NetAdapter | Where-Object {$_.InterfaceDescription -match 'Team'}
Get-NetAdapterStatistics | Select Name,LinkSpeed

Root Cause Analysis

LBFO teams reference member adapters by a combination of their interface GUID and adapter name stored in the LBFO registry hive. When a driver update changes the adapter name (e.g., ‘Ethernet’ → ‘Ethernet 2’) or replaces the GUID, the LBFO service cannot re-attach the physical adapter to the team. The team continues to exist in the registry but has no valid members, resulting in a Degraded state. In some cases the team appears functional but packets are dropped because the member adapter is in an unknown state.

Quick Triage

Confirm the LBFO team status and identify which member adapter is causing degradation.

# Triage in 3 minutes
Get-NetLbfoTeam | Select Name,TeamingMode,LoadBalancingAlgorithm,Status
Get-NetLbfoTeamMember | Select TeamName,Name,AdministrativeMode,OperationalStatus
Get-NetAdapter | Where-Object {$_.Status -eq 'Disconnected' -or $_.Status -eq 'NotPresent'}
Get-NetAdapterBinding | Where-Object {$_.ComponentID -eq 'ms_implat'}

Step-by-Step Diagnosis

Confirm team degraded state and identify which member adapter(s) are causing the issue. Check Device Manager for yellow warning icons on NIC adapters. Run `Get-NetAdapter` to see if member adapters are visible and what state they are in.

Get-NetLbfoTeam
Get-NetLbfoTeamMember
Get-NetAdapter | Format-Table Name,InterfaceDescription,Status,LinkSpeed
Get-WinEvent -LogName System -Source 'Microsoft-Windows-NDIS' -Newest 20

Solution — Primary Fix

Rebuild the NIC team from scratch: remove the existing team (which retains the IP configuration on the team interface), re-add current physical adapters as members, and verify the team forms correctly.

# Remove and recreate team
$teamName = 'DataTeam'
$member1 = 'Ethernet'
$member2 = 'Ethernet 2'
$teamIP = '192.168.1.10'
$teamGW = '192.168.1.1'

# Record current IP before removal
$currentIP = (Get-NetIPAddress -InterfaceAlias $teamName -AddressFamily IPv4).IPAddress

# Remove team
Remove-NetLbfoTeam -Name $teamName -Confirm:$false

# Recreate
New-NetLbfoTeam -Name $teamName -TeamMembers $member1,$member2 -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic

# Re-assign IP
New-NetIPAddress -InterfaceAlias $teamName -IPAddress $teamIP -PrefixLength 24 -DefaultGateway $teamGW
Set-DnsClientServerAddress -InterfaceAlias $teamName -ServerAddresses '10.0.0.1'

Solution — Alternative Approaches

Alternative 1: Use SET (Switch Embedded Teaming) instead of LBFO for Hyper-V hosts — SET is maintained by the Hyper-V team and is more resilient to driver updates. Alternative 2: Vendor NIC teaming utilities (Intel PROSet, Broadcom BACS) instead of Windows LBFO — these manage the team at the driver level and are less affected by Windows updates.

# Create SET team for Hyper-V hosts (replaces LBFO)
New-VMSwitch -Name 'ExternalSwitch' -EnableEmbeddedTeaming $true -NetAdapterName @('Ethernet','Ethernet 2') -AllowManagementOS $true

Verification & Acceptance Criteria

Team status shows ‘Up’ in Get-NetLbfoTeam. Both members show ‘Active’ in Get-NetLbfoTeamMember. The team IP is reachable. Simulate failover by disabling one team member and confirm traffic continues on the remaining member.

Get-NetLbfoTeam
Get-NetLbfoTeamMember
# Failover test
Disable-NetAdapter -Name 'Ethernet' -Confirm:$false
Start-Sleep 5
Test-NetConnection -ComputerName 8.8.8.8
Enable-NetAdapter -Name 'Ethernet'

Rollback Plan

If team rebuild fails: restore from backup by reverting to the previous working NIC driver version in Device Manager. Alternatively use a single NIC temporarily until the team issue is resolved.

# Rollback NIC driver
# Device Manager -> Network Adapters -> Right-click NIC -> Properties -> Driver -> Roll Back Driver

Prevention & Hardening

Before applying NIC driver updates in production: test on a non-production server first. Document the team configuration (`Get-NetLbfoTeam`, `Get-NetLbfoTeamMember`) before any driver update. Implement network monitoring that alerts on team degradation (SNMP trap or WMI event).

# Alert on team degradation
Register-WmiEvent -Query "SELECT * FROM __InstanceModificationEvent WITHIN 30 WHERE TargetInstance ISA 'MSFT_NetLbfoTeam' AND TargetInstance.Status != 'Up'" -SourceIdentifier 'TeamDegraded' -Action { Write-EventLog -LogName Application -Source 'TeamMonitor' -EventId 1000 -Message 'NIC Team degraded' }

Related Errors & Cross-Refs

Related: Network adapter shows as ‘Unidentified network’ (routing or DNS issue, not teaming), Virtual NIC performance degradation in Hyper-V (vmswitch/VMNC driver issue distinct from LBFO), 802.3ad LACP negotiation failure (switch configuration issue on the upstream switch port).

View all Windows Server 2025 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft LBFO documentation at learn.microsoft.com/windows-server/networking. SET teaming guide for Hyper-V at learn.microsoft.com. NIC vendor teaming documentation. KB2855219 covers known LBFO issues after Windows updates.