Problem adding second vmxnet nic - Windows 2008 R2 VM

[CCSL]

I have a Windows 2008 R2 VM in my production environment currently with 2 virtual nics installed, one vmxnet3 and one e1000. I need to add a second vmxnet3 nic. The problem is when I add the additional vmxnet3 device windows recognizes the device, starts to load the drivers, then fails. In device manager the new device is shown as not working. Disabling and re-enabling the device does not fix the issue. I'm able to successfully add a second e1000 nic but I need to use the vmxnet3 driver to replicate my dev environment.

I suspect a reboot will resolve the device issue but I'd like to fix the issue without a reboot as the server is in my production environment.

Any ideas?

[Gortee]

Evening,

Had this same issue earlier today with a vcloud implemented Windows 2008 R2.  Simple answer Windows cannot deal with it so reboot it your only real option.  There might be some magical command only microsoft knows but a reboot is much faster and less painful.  Sorry I don't have an easy answer udev would solve it on linux...

Thanks,

J

[PatrickHoban]

I wasn't able to reproduce the issue. I did loose console connectivity for a moment when it added the second vmxnet3 nic but other than that it installed. What if you Uninstall from Device Manager then scan for new hardware?