I just installed two new HP ProLiant DL360 G6 with Microsoft Windows Server 2008 R2. Everything worked fine until I installed the HP Support Pack which includes Drivers and Firmware for the HP Server.
After I installed the HP ProLiant Support Pack one of my Network Interfaces could not start. I got the following error in the Device Manager:
HP NC382i DP Virtual Bus Device
This device cannot start. (Code 10)
I tried to uninstall the device and rebooted the server but this didn’t work. I had still the same error.
The problem was that just uninstalling the driver does not work, you also have to check the checkbox on “Delete the driver software for this device.”
After doing that you can rescan for new hardware and the system will find this adapter again and everything will work fine.Tags: Code 10, DL360, DL360 G6, Driver, error, Hewlett-Packard, HP, HP NC382i DP Virtual Bus Device, HP ProLiant, HP ProLiant DL360, HP Support Pack, install, install driver, Microsoft, Network Interface Error, Proliant, ProLiant DL360, Support Pack, This device cannot start, uninstall Last modified: March 23, 2011
Do you know what the underlying issue is? I am experiencing the same issue upgrading NIC driver to v18.104.22.168. Driver upgrades fine but Virtual Bus device fails to start after reboot.
Maybe you must follow these steps:
1. Update Firmware.
2. Install O.S. through SmartStart
Had the same trouble on two HP ProLiant BL460c. Installed O.S. on the first through the latest SmartStart, and second one was cloned. Your solution worked, but afted each reboot of any of the servers I’m getting the same warning in device manager, and NC382i network adapters dissapear from the corresponding tab.
Try having this happen on a DL380 G5 running Server Core. I did an upgrade through the Version Control Agent and after the restart I had no network available. Nothing I could think to try worked so I ended up doing a rebuild just to get the network running again. It was only when it happened on a windows server with a GUI that I saw this Code 10 error on the network controllers and came across this webpage. Your method worked, although I did end up having to rebuild my virtual network in Hyper-V. Now I’ve just got to figure out how to do this from the command line in Server Core…