Hyper-V Networking Problems

I found a series of keys in the registry that I could delete to get rid of the adapters.  I went back in the registry to see if the root folder was still there but it's gone so Unfortunately I'm not sure what it was called but it's located under:

If you search for the exact name of the adapter in the registry you will see the keys...

The fun part is actually deleting them... there are lots of embedded keys and most of them have no owner or at least administrator doesn't have the ability to see it.  You have to take ownership of the key then add administrator to the permissions... then once u do that u will be able to see the keys under it and you can keep doing the same thing... there are about 50+ keys you need to delete (individually because of permissions!) in order to delete the entire set for the adapter.

I wish recursive claim ownership was possible to grab every key under it but unfortunately that does not work.. you need to claim ownership and add permission to a key in order to see what's under it.

Hyper-V causes way too many problems on my system... and after deleting 5 adapters from the registry in the way I described above I'm more than done with it.  I might try again on next release but I'm finding the vmware server 2.0 beta works VERY well on server 2008 so I'm using that for now.

Lösung: I used subinacl (a free microsoft tool) to change the permissions on the keys.

For each 0000, 0001, etc. in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\VMS_MP\ run the following line (in a bat file or like):

"C:\Program Files (x86)\Windows Resource Kits\Tools\subinacl" /subkeyreg HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\VMS_MP\0000 /grant=administrators=f

After this, the keys (0000, 0001, etc) can be deleted, and the intefaces will go away:)

Link: Microsoft SubInACL


  1. Error : 5 Access is denied.

    Schade, hat nicht funktioniert. Muss ich vorher Hyper-V deinstallieren?


Kommentar veröffentlichen

Beliebte Posts