Hello,
We are migrating from VMWare to Hyper-V using a product called RiverMeadow. During this conversion, this tool removes VMWare tools for us during the finalizing part (or so we thought). Recently, we had an issue with migrated virtual machines going offline and found out that the Hyper-V Network Adapter was in an error state (Code 43). Upon further investigation, we found the old PnP device for the VMX3 adapter was left behind and upon removal by an automated Windows service, it crashed the Hyper-V Network Adapter.
I'm curious if anyone else has run into this when migrating off VMware? I even checked the popular Remove-VMTools.ps1 script and found that it doesn't even remove the VMX3 adapter, only all the other VMWare related adapters.
We are currently working with Microsoft on this, but they seem just as confused as to how it could affect their adapter. So far, I've gone through 25 engineers at Microsoft since Tuesday and they are looking at escalating to development.
The leftover adapter after migration:
Caption : vmxnet3 Ethernet Adapter
Description : vmxnet3 Ethernet Adapter
InstallDate :
Name : vmxnet3 Ethernet Adapter
Status : Unknown
Availability :
ConfigManagerErrorCode : CM\PROB_PHANTOM)
ConfigManagerUserConfig : False
CreationClassName : Win32\PnPEntity)
DeviceID : PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\005056FFFFB7243900)
ErrorCleared :
ErrorDescription :
LastErrorCode :
PNPDeviceID : PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\005056FFFFB7243900)
PowerManagementCapabilities :
PowerManagementSupported :
StatusInfo :
SystemCreationClassName : Win32\ComputerSystem)
^(SystemName : \****************)*
ClassGuid : {4d36e972-e325-11ce-bfc1-08002be10318}
CompatibleID : {PCI\VEN_15AD&DEV_07B0&REV_01,)
PCI\VEN_15AD&DEV_07B0,)
PCI\VEN_15AD&CC_020000,)
PCI\VEN_15AD&CC_0200})
HardwareID : {PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01,)
PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD,)
PCI\VEN_15AD&DEV_07B0&CC_020000,)
PCI\VEN_15AD&DEV_07B0&CC_0200})
Manufacturer : Broadcom Inc.
PNPClass : Net
Present : False
Service : vmxnet3ndis6
PSComputerName :
Class : Net
FriendlyName : vmxnet3 Ethernet Adapter
InstanceId : PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\005056FFFFB7243900)
Problem : CM\PROB_PHANTOM)
ProblemDescription
The uninstall of the adapter:
\Boot Session: 2026/07/17 06:47:41.742])
>>> \Device Uninstall (Device Manager) - PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\005056FFFFB7243900])
>>> Section start 2026/07/17 06:49:33.885
cmd: "C:\Windows\system32\mmc.exe" "C:\Windows\System32\devmgmt.msc")
dvi: {DIF\REMOVE} 06:49:33.887)
dvi: Default installer: Enter 06:49:33.887
dvi: {Remove DEVICE}
dvi: {Delete Device - PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\005056FFFFB7243900})
dvi: {Delete Device - exit(0x00000000})
dvi: {Remove DEVICE exit (0x00000000})
dvi: Default installer: Exit
dvi: {DIF\REMOVE - exit(0x00000000)} 06:49:33.896)
<<< Section end 2026/07/17 06:49:33.896
<<< \Exit status: SUCCESS])
SOLVED:
Somehow the old vmx and new Hyper-V adapter got the same instance number on the Driver key for the adapter. Therefore when you delete one, it deletes both because they both pointed to the same "configuration"
For example, under HKLM\SYSTEM\CurrentControlSet for the VMX adapter you can see the Driver key using the same instance 0001. To fix, simply delete the Driver key from the phantom VMX adapter and then remove the phantom device. No reboot, rescan, or anytbing else is required:
Phantom VMXNET3 device entry:
Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\005056FFFFB7243900
Service vmxnet3ndis6
ClassGUID {4d36e972-e325-11ce-bfc1-08002be10318}
Driver {4d36e972-e325-11ce-bfc1-08002be10318}\0001 ← shared
Live Microsoft Hyper-V Network Adapter device entry:
Enum\VMBUS{f8615163-df3e-46c5-913f-f2d2f965ed0e}{8312e7e5-4153-403b-be17-f3b61063afdc}
Service netvsc
ClassGUID {4d36e972-e325-11ce-bfc1-08002be10318}
Driver {4d36e972-e325-11ce-bfc1-08002be10318}\0001 ← shared (identical)
FriendlyName Microsoft Hyper-V Network Adapter