Hyper-V Program Manager
There have been a number of people reporting that when they start a virtual machine - they get the following error:
The network adapter with address "00:00:00:00:00:00" of virtual machine "...." failed to initialize because the address is a null address.
To fix this problem you should use REGEDIT to:
This registry value was added in Virtual PC SP1’s Virtual Machine Network Services driver. It is supposed to be setup during installation by the driver’s notify object. However, under certain circumstances the notify object of the old version is used during the installation of the new version and this registry value is never created. It is used by the driver to determine if a particular host adapter can be used in the MAC address generation algorithm. If the key is not present, we assume that the host adapter cannot be. In the case you experienced, none of your adapters appear suitable as a basis for MAC address generation and the driver returns a NULL MAC address which causes VPC to report the error.
Estou com o mesmo problema, vou fazer o teste e ver se funciona
This doesn't seem to work. And I'm lost as to what the flags thing means. Am I supposed to copy over the GUID number and make it a folder or something? I don't see the same GUID in the Adapters "folder". I've tried this multiple ways, but it's still not working.
Thank you. This works on Virtual 2005 server R2 as well.
In case this works for anyone else:
What I did, which was much easier for me, was I simply deleted the Virtual Machine config file (.vmc) and recreated it attaching to the hard drive file (.vhd). Took about 5 seconds and worked great.
Thanks but after restart the message
(The network adapter with address "00:00:00:00:00:00" of virtual machine "New Virtual Machine" failed to initialize because the address is a null address.)
I'm using VPC 2007. The original solution did not work for me, nor did Matt's. What worked for me was changing the network adapter (Settings > Networking > Adapter 1) to "Not connected," power cycling the VM, and then changing it back.
Thank you Christian Campbell, your solution worked great for me.