I recently discovered that Hyper-V adds a NTFS security group permission to the parent location path where the virtual disk (vhd) are located called “Virtual Machines”. This became a issue when I placed a virtual disk on the root of a NTFS partition I was able to discover that the permission was missing but was unable to add it manually with GUI’s security settings window as “Virtual Machines” was unknown so it must be a security identifier. I was able to use the get-acl powershell command-let to read the SID which was returned as “S-1-5-83-0”.
An interesting note I couldn’t find this SID in Microsoft’s Well-known security identifiers list (kb243330).
I used the following powershell script to add the needed security right manually:
$sid=get-acl H:\
$sid.SetSecurityDescriptorSddlForm( ($sid.sddl + "(A;;FA;;;S-1-5-83-0)(A;OICIIO;0x101f01ff;;;S-1-5-83-0)") )
> set-acl H:\ -AclObject $sid
Thank you, thank you, thank you.
That worked. Thanks!
Works like a charm… actually I had to apply the sid recursivly
Thanks. Worked for me too.
There are no permissions assigned to “Virtual Machines”, the ACL is empty. Does it require Full Control to C:\ProgramData\Microsoft\Windows\Hyper-V as well as where ever I want to store the VM’s?
Cool, you can also use:
icacls X:\filename.vhd /grant “*S-1-5-83-0:(R)”
They automatically turn on and off based on pre-set temperature settings in the attic
area of one of these questions before even allotting a monetary investment on
your home invasion project. Remodeling may present an opportunity to give
your Home Invasion contract to.