The error “Object exists. An attempt was made to create an object and the object name already existed” when renaming a NIC teaming interface in Windows Server 2019 typically occurs because the new name you’re trying to assign is already in use—either by another network adapter, a previously deleted but not fully cleaned-up virtual adapter, or a leftover registry/configuration entry.
Here’s how to resolve it:
✅ Step-by-Step Fix
1. Check for Existing Adapters with the Target Name
Open PowerShell as Administrator and run:
powershell
Get-NetAdapter | Select-Object Name, InterfaceDescription
Look for any adapter (including hidden/disabled ones) that matches the name you’re trying to use.
💡 Also check Device Manager:
- Open Device Manager → View → Show hidden devices
- Expand Network adapters
- Look for grayed-out entries with your desired name. If found, right-click → Uninstall device → Check “Attempt to remove the driver” if available.
2. Check for Leftover Virtual Adapters or Teams
Run:
powershell
Get-NetLbfoTeam
Ensure no existing team uses the name you’re trying to assign.
Also list all network interfaces including virtual ones:
powershell
Get-NetIPConfiguration | Select-Object InterfaceAlias
3. Clean Up Registry (If Needed)
⚠️ Back up the registry before making changes.
Leftover entries may exist under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}
Each subkey here represents a network adapter. Look for entries where the Connection → Name matches your target name.
🛑 Do not delete randomly—only remove entries that correspond to non-existent adapters (e.g., no matching device in Device Manager even with hidden devices shown).
4. Use PowerShell to Rename Properly
Instead of GUI, use PowerShell to rename the team:
powershell
# First, get the current team name
Get-NetLbfoTeam
# Rename it (replace “OldTeamName” and “NewTeamName”)
Rename-NetLbfoTeam -Name “OldTeamName” -NewName “NewTeamName”
🔒 Ensure the new name:
- Contains no spaces or special characters (use hyphens or underscores if needed)
- Is not already used by any physical or virtual adapter
- Is under 15 characters (recommended for compatibility)
5. Reboot if Necessary
After cleaning up hidden devices or registry entries, reboot the server to ensure all stale references are cleared.
🔒 Prevention Tips
- Avoid reusing names of recently deleted teams/adapters.
- Use consistent naming conventions (e.g.,
TEAM-DB,TEAM-WEB). - Always delete teams via PowerShell or Server Manager—not just by disabling.
Example Workflow
powershell
# Check current teams
Get-NetLbfoTeam
# Check all adapters
Get-NetAdapter -IncludeHidden
# If “NewTeam” already exists as a hidden adapter, remove it first
Remove-NetAdapter -Name “NewTeam” -Confirm:$false
# Now rename
Rename-NetLbfoTeam -Name “OldTeam” -NewName “NewTeam”
If the issue persists after these steps, there may be a deeper system inconsistency—consider checking Windows logs (Event Viewer → System) for related errors from Netwtw04, NDIS, or LBFO sources.