We use a mix of Windows 7 physical desktops and vitual machines (hosted on ESX). We use the same image and AD domain for both.
On the VMs, when we create a new volume, whether on an existing disk or a new one, it appears as read-only. Read-only flags are not set in diskpart, nor does clearing those flags make the disk readable. This problem does not affect our physical desktops.
Here are steps you can replicate on your Win7 system:
- Apply a Windows 7 image. Don't join to a domain. Log on as local administrator.
- Open computer management and browse to disk management.
- If Disk 0 is full, right click on the C volume and shrink it to get some free space. Or just add a hard drive in vCenter.
- Right-click on the unallocated space and create a new simple volume. In the wizard, give it a drive letter and format it as NTFS.
- Open DiskPart. In Diskpart, enter 'select disk 0' and 'select volume y' where y is the volume number of the new volume.
- Enter the commands 'attr disk clear readonly' and 'attr volume clear readonly'
- Enter 'detail disk' and 'detail volume' to verify that the read only flag is set to no.
- Close DiskPart and open Windows Explorer. Right-click on the new drive and bring up properties.
- Verify permissions are set so that the Administrators group has Full Control.
- Right-click on open space in Windows Explorer and notice that "New" is not in the context menu.
- Drag a file to the drive and get an error that the media is write-protected.
- Go back into properties and try to change permissions. Get "media is write protected" errors again.
- Repeat steps 5 - 10 until you go nuts.
If we apply this same Win7 image to a physical desktop, new volumes are read-write as normal. If we perform these steps on Server 2012 VMs on the same datacenter/cluster/datastore, new volumes are read-write as normal. If we apply this Win7 image to a VM, the volumes are read-only despite diskpart listing them as read-write.