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.
Thomas works as a Senior Program Manager & Chief Evangelist Azure Hybrid at Microsoft (Cloud + AI). He engages with the community and customers around the world to share his knowledge and collect feedback to improve the Azure hybrid cloud and edge platform. Prior to joining the Azure engineering team (Cloud + AI), Thomas was a Lead Architect and Microsoft MVP, to help architect, implement and promote Microsoft cloud technology.
If you want to know more about Thomas, check out his blog: www.thomasmaurer.ch and Twitter: www.twitter.com/thomasmaurer
Do you know what the underlying issue is? I am experiencing the same issue upgrading NIC driver to v6.2.8.0. Driver upgrades fine but Virtual Bus device fails to start after reboot.
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…
My name is Thomas Maurer. I am a Senior Program Manager & Chief Evangelist for Azure Hybrid at Microsoft. I am part of the Azure engineering team (Cloud + AI) and engage with the community and customers around the world. Opinions are my own.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
After doing that you can rescan for new hardware and the system will find this adapter again and everything will work fine.
Do you know what the underlying issue is? I am experiencing the same issue upgrading NIC driver to v6.2.8.0. Driver upgrades fine but Virtual Bus device fails to start after reboot.
Any ideas?
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…