Failure to add device 'microsoft virtual hard disk'

[guest]

A new server install running hyperv RC1.

When i try to add a .vhd to a VM machine, it returns the following error.:

'DOTNET83' failed to add device 'Microsoft Virtual Hard Disk'. (Virtual machine ID 48B19B7B-650B-4395-8FF3-1CA15219CEFB)

'DOTNET83': The file 'D:\Virtual Machines\Production\New Virtual Hard Disk.vhd' does not have the required security settings. Error: 'General access denied error' (7864368). To fix the security settings, remove the device associated with this file from the virtual machine and then add it again. (Virtual machine 48B19B7B-650B-4395-8FF3-1CA15219CEFB)

'DOTNET83': Cannot get information for attachment 'D:\Virtual Machines\Production\New Virtual Hard Disk.vhd'. (Virtual machine ID 48B19B7B-650B-4395-8FF3-1CA15219CEFB)

This is a fresh server throwing this error when creating a new vm.

Anyone encountered something like this before?

[guest]

This error usually indicate that the Security settings of the specified .vhd are not configured properly.

First, ensure that you are a member of local Administrators group. And make sure the path is not a network mapped drive.

Then, check the specified .vhd file to see if all the Security settings are correct. You can do this by simply creating a new virtual hard disk and comparing the Security settings with the new created .vhd file.

Usually, you should (not limit to) give the current logon user Read and Write permissions, otherwise this problem may occur.

If the same error remains, you may need to re-install the server, upgrade to RC1 (not creating new virtual machines before upgrading)and then create new

[guest]

I have resolved the issue, kinda.

It turns out that the failure is actually brought about by the Intel System Management Software ( to be precise the intel serer management pack for microsoft windows) that I installed on my S5000PAL intel motherboard. As soon as this software is installed, HyperV is broken, irrevocably. The only way to restore functionality is to rebuild the server from scratch without the software.

Note that the software doesn't break HyperV immediately, but only after a reboot.

I can only advise that you rebuild the server, test that HyperV beta does work for you, then install all necessary software in small chunks at a time, making sure to reboot in between. I'd also recommend grabbing some imaging software of some sort and taking _lots_ of snapshots.

[guest]

I'm experiencing the same problem. The original VHD file was copied from a Microsoft Virtual Server machine to a Hyper-V server. I don't have the intel management software installed. I see the same additional user permission GUID mentioned before but I don't see any way to add it in windows (maybe ACL command line? not sure) ...

A bunch of other machines were imported from the same host and they work fine.

I gave the "User" full control to the disk and it worked. After going back to the security settings, I noticed that it added the GUID user with read and write permissions. Will try removing the "User" full control now and see if it works still.