Guest NIC Not Working

[JaxIsland7575]

The Host is Win 10 64bit v1909 running VB v6.1. The guest is also Win 10 64bit v1909.

The issue is the network on the guest will not connect. My goal is to have it set to Bridged Adapter through the hosts Intel Gigabit CT Desktop Adapter. The host has 2 network cards on separate networks so I need it to go through the CT adapter. The guest is set to use Intel PRO/1000 MT Desktop (82540EM) adapter. When the VM boots device manager has a yellow exclamation point and says:

Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

Object Name not found.

I have uninstalled and restarted with no change. I tried manually installing new drivers but it always reports back that it has the latest driver which is listed as 3/23/2010 version 8.4.13.0.

I have tried going through each of the adapters in the configuration and none of them work in the guest.

I am not sure what else I can do to try and get this connected, my expectation was VB uses adapters that are natively supported in the guest OS so this shouldnt be happening. Any help would be appreciated.

[birdie]

I'm almost sure it's down to your company firewall policy or firewall software. Ask your admins. VBox has nothing to do with your issue.

[scottgus1]

Pro MT Desktop is the default network card Virtualbox provides for a Windows 10 guest.

Start the guest from cold boot, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please zip and post using the forum's Upload Attachment tab, these two files in the guest's folder:

the .vbox file
vbox.log in the Logs folder

[JaxIsland7575]

It was a new VM that had been converted from vhdx to vdi using vboxmanage.exe. I deleted the whole thing and converted the same source vhdx to vdi and created a new VM. It started working as soon as I booted. Not sure if it was a bad conversion or something went sideways but its working now. Thanks for the responses though.

[scottgus1]

Bits don't flip when they should sometimes. Stray cosmic ray, or Martian mind-probe missed its target?

Glad you're up and running!

("Where's my PU-238 explosive space modulator?!")

[birdie]

It was a new VM that had been converted from vhdx to vdi using vboxmanage.exe. I deleted the whole thing and converted the same source vhdx to vdi and created a new VM. It started working as soon as I booted. Not sure if it was a bad conversion or something went sideways but its working now. Thanks for the responses though.

You completely omitted this important piece of info earlier. Glad it's working for you now.