kackland
asked on
Hyper-V Virtual Ethernet Adaptor - Code 31 in Device Manager
We are currently preparing a new Hyper-V host however have suddenly noticed that in Device Manager we have three driver issues all of which relate to Hyper-V. They are as follows.
Hyper-V Virtual Ethernet Adaptor
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Hyper-V Virtual Ethernet Adaptor #2
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Microsoft Hyper-V Network Switch Default Miniport
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
I did remove all Hyper-V instances as well as all Virtual Switches and then re-created them however these drivers still show up as problematic in Device Manager on the Host. Oddly enough this doesn't seem to be causing any issue with the Hyper-V instance in that we have installed Server 2012 onto it and it is able to gain full network/internet connectivity.
Thanks in advance.
Hyper-V Virtual Ethernet Adaptor
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Hyper-V Virtual Ethernet Adaptor #2
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Microsoft Hyper-V Network Switch Default Miniport
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
I did remove all Hyper-V instances as well as all Virtual Switches and then re-created them however these drivers still show up as problematic in Device Manager on the Host. Oddly enough this doesn't seem to be causing any issue with the Hyper-V instance in that we have installed Server 2012 onto it and it is able to gain full network/internet connectivity.
Thanks in advance.
ASKER
Hi Mutawadi,
It is happening on the host only.
Should I still try the registry fix above?
Thanks
It is happening on the host only.
Should I still try the registry fix above?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can also try doing this if the above didn't work: Delete the Config key under the registry path HKLM\SYSTEM\CurrentControl