This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
-
Friday, January 25, 2013 4:41 PM
Testlab Domain Controller (no recent snapshot unfortunately)
In VMWare Vcenter, I removed the E1000 NIC driver and replaced it with a VMXNET3 adapter.
Now I'm getting "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)" on the adapter.
I've tried uninstalling and reinstalling VMWARE tools as well as reverting to an E1000 adpater (I even tried a MS loopback adapter)....all to no avail (Code 31).
I've spent 3+ hour on the phone with VMWare Tech Support and they deferred to Microsoft.
I've tried deleting the config reg key under network and removing any recent Windows Updates.
Help! This server simply won't let me install any drivers and this particular server (testlab DC), while not production, would be a royal pain to reinstall from scratch.
David W King
All Replies
-
Friday, January 25, 2013 9:04 PM
Hello David,
maybe my answer doesn't hit purposes of this forum but: did you already checked following configuration parameters with VMware Support ?- Virtual Hardware version: VMXNET3 is supported only for VMs version 7 or later (VMware link: Choosing a network adapter for your virtual machine); which is VH version of your VM ?
- Did you try to remove and add again VMXNET3 network adapter from VMware VM Hardware properties ?
- Which is VMware (build) version ?
- Do you upgrade VH recently? VMware link: Upgrading virtual hardware on 2008R2 causing NIC to not load
Then about Operating System:
- Which is OS version of your DC ?
- Did you also try to clean all hidden/orphaned devices:
1. From Command Prompt type: set show_nonpresent_devices = 1 (enter)
2. Then launch Device Manager: devmgmt.msc (enter)
3. From View menu tick "Show hidden devices" item
4. Now you should see orphaned devices (if exist), grayed out: remove those Network cards no more in use.
5. Try to remove and re-add VMXNET3 network adapter
Note: Try also to update VMXNET3 driver from Device Manager manually (Folder: %ProgramFiles%\VMware\VMware Tools\Drivers\vmxnet3)
Bye,
Luca
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
- Edited by Luca Fabbri Friday, January 25, 2013 9:59 PM
-
Monday, January 28, 2013 4:25 AM
In device manager, if you click hidden device, do you see other NIC as the one in error ? erase them, and the one in error and restart a device detection.
If nothing is found, does the VM got shutdown, and a nic is still binded to it ? in any other case please see; Manually installing the VMXNET driver in a Windows NT guest operating system
If you are really out of idea, install vConverter and re-converte it, and select to inject all drivers. (this step should work, as it do like a sysprep, and will force all virtual driver)
Please after that continue on vmware's forum. As this is a NIC'S driver issue IMO versus vsphere that does not seem to bind the correct NIC. http://communities.vmware.com/index.jspa
MCP | MCTS 70-236: Exchange Server 2007, Configuring
Twitter - @yagmoth555 (
)
Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/- Edited by Yagmoth555 Monday, January 28, 2013 4:25 AM
-
Monday, January 28, 2013 12:43 PM
It's a 2008R2 box and the VM version is 7 (has been for over a year....no recent VH upgrades).
Yes, early on in the trouble-shooting I did the set show_nonpresent_devices=1 command and removed hidden devices.
What's strange is that I can't install any NICs....even non-VMWare NICs like the Microsoft loopback NIC....with or without VMWARE tools installed.
David W King
-
Monday, January 28, 2013 1:08 PMThanks for the ideas. Early on in the trouble-shooting I did the set show_nonpresent_devices=1 command and removed hidden devices. I did it repeatedly every time I subsequently unsuccessfully installed a myriad of NICs....all of which failed. I intalled the VMXNET3 nic from the VMWARE TOOLS directory to no avail. I also could not install non-VMWare NICs like the Microsoft loopback NIC....with or without VMWARE tools installed. Converter would make sense if it was a NIC driver issue, but I think it's an OS issue because no NIC will install. I think I'm going to get Microsoft support to remote in and hold their feet to the fire.
David W King
-
Monday, January 28, 2013 6:27 PM
Hello David,
did you already try to remove and recreate Virtual Machine using existing VMDK ?- Make a backup of all VM configurations file
- Remove VM from Inventory
- Remove VM configuration *.vmx file (not *.vmdk !!!)
- Create new VM using existing VMDK
What about server Event Viewer ? Does it report some errors useful for investigation ?
Luca
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
- Edited by Luca Fabbri Monday, January 28, 2013 6:29 PM
-
Monday, January 28, 2013 6:39 PM
Yep...removed it from inventory and added it back.
Nothing helpful in event viewer.
Microsoft support didn't have a quick fix for the error....said the registry may be corrupt. Rather than take the time to export and ship all the logs, I've decided just to forcible remove references of the downed Domain Controller and add a new one back under the same name. At least I know that fix will work and shouldn't take that long.
I'll let you know if I have a successful outcome.
Thanks.
David W King
- Proposed As Answer by Luca Fabbri Saturday, April 13, 2013 11:15 AM
- Marked As Answer by Santosh BhandarkarMicrosoft Community Contributor, Moderator Friday, April 19, 2013 9:04 AM
-
Monday, January 28, 2013 8:44 PM
Hello David,
you don't have a critical production environment, but a test lab, so I agree with you faster solution is to rebuild a new DC.Bye,
LucaDisclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
.png)
