locked
"Failed to add device Virtual Hard Disk" error on removable storage in Windows 8 Hyper-V RRS feed

  • Question

  • I've installed Hyper-V on a Windows 8 Enterprise PC and can't seem to assign any virtual disks created on my second disk (D: drive) to a virtual machine.

    I have created the virtual machine (XML stored on C: drive) in the Hyper-V Manager console without a disk assigned to it. I then successfully created a virtual disk in the Hyper-V Manager console. However, when I try and assign the disk to the virtual machine, it gives me the following error when I press OK:

    Error applying Hard Drive changes

    Failed to add device 'Virtual Hard Disk'

    Hyper-V Virtual Machine Management service Account does not have permission to open attachment. Error: 'General access denied error' (0x80070005)

    I have checked the permissions on the virtual disk and the virtual machine ID account has been assigned Read/Write permissions (I have tried adding full control permissions but this does not resolve the error). The D: drive has been formatted in Windows 8 and if I create a virtual disk on the C: drive then it works fine. As far as I can tell, I can't see any obvious differences between the C: and D: drives in terms of configuration or permissions. I have BitLocker installed on both of them.

    Hyper-V has been installed with the default settings - no configuration or service account changes.

    Any help would be greatly appreciated - Thanks.


    Phil Childs http://get-spscripts.com

    Tuesday, August 21, 2012 9:50 PM

Answers

All replies

  • Hi,

    Please help me to collect the following information:

    1. What’s the type of the second disk?
    2. What’s the format of the D: drive? Fat32 or NFTS or others?

    Wednesday, August 22, 2012 1:34 AM
  • Hi Vincent,

    NTFS - It appears to have the same configuration as the first disk, although I haven't gone further than what you can check in the UI.

    Thanks


    Phil Childs http://get-spscripts.com

    Wednesday, August 22, 2012 6:53 AM
  • Where is the VHD stored?

    The Computer system account needs access to the VHD file (not your user account).

    Also, do you have any anti-virus running?


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Wednesday, August 22, 2012 3:16 PM
  • Hi Brian,

    The VHDX file is stored on the D: drive and has the following permissions:

    Authenticated Users (Modify)

    SYSTEM (Full Control)

    Administrators (Full Control)

    Users (Read & Execute)

    Virtual Machine ID account (Read & Write)

    I have not installed any 3rd party anti-virus software, although there is AV software built into Windows 8.

    Phil


    Phil Childs http://get-spscripts.com

    Wednesday, August 22, 2012 3:20 PM
  • When the virtual disk is attached to the VM, the hyperivsor will attempt to modify the permissions on the file - this requres that it open it exclusively (just as it also requires when it boots the VM).

    You should never have to manually set the permissions.

    Is the virtual disk open by any other process?  Mounted to any other VM (only one VM can have hte virutal disk attached)?

    And, the virutal disk is local?  Not on any removable storage?


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Wednesday, August 22, 2012 3:36 PM
  • No manual permissions have been set on the virtual disk file - only those set by the Hyper-V console.

    The virtual disk is not used by any other process.

    The virtual disk is on removable storage (the D: drive is a separate disk to the local C: drive)

    Thanks,

    Phil


    Phil Childs http://get-spscripts.com

    Wednesday, August 22, 2012 4:12 PM
  • If hte portions of hte VM are on D:\...

    Are they within a folder on D:\ or at the root of D:\?

    I have run into problems placing virtual disks at the root of a drive, they must be at least one folder deep.  Same problem on Server 2008 at the root of C:\

    So, it should be at least: D:\MyVM\My.vhdx


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Wednesday, August 22, 2012 4:25 PM
  • I just caught your comment about BitLocker..

    Here is an oldie:

    http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/06/25/whitepaper-hyper-v-and-bitlocker.aspx


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Wednesday, August 22, 2012 4:26 PM
  • Hi Brian,

    The virtual disk is currently one folder deep, but has been two folders deep in earlier tests...

    Phil


    Phil Childs http://get-spscripts.com

    Wednesday, August 22, 2012 5:19 PM
  • Hi Brian,

    I'll definitely read the article, although I did try it first of all with BitLocker switched off and it didn't make a difference. I'll take a look again though, thanks.

    Phil


    Phil Childs http://get-spscripts.com

    Wednesday, August 22, 2012 5:22 PM
  • Hmm..

    I am wondering if there is something strange going on.  Possibly the removable disk is mounted in user space and not system space.  Folks hit this a lot with 2008 and removable disks. 

    Not all removable disks mounted at the local system level and thus were not usable with Hyper-V.

    Only certain removable drives mounted properly for the system to use them.

    You stated; "I then successfully created a virtual disk in the Hyper-V Manager console" - were you having a problem that caused you to not created the empty virtual disk at the time of VM creation?

    Also, have you tried creating a virutal disk using Disk Manager?  And then mounting it?  This might also point to an issue.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.


    • Proposed as answer by BrianEhMVP Friday, October 26, 2012 7:55 PM
    • Edited by BrianEhMVP Friday, October 26, 2012 7:56 PM
    • Unproposed as answer by BrianEhMVP Friday, October 26, 2012 7:59 PM
    Wednesday, August 22, 2012 5:28 PM
  • Strange indeed, Brian.

    OK, I trashed the disk using Disk Manager and mounted it to the same Virtual Machine as before and this is working - Not an ideal configuration for me as I wanted to host multiple virtual disks from a single drive, but I'll live with it until I find out more.

    What is interesting is that when building the OS on this virtual machine using a Windows 2008 R2 iso from another removable disk (E: drive), I received a similar message as before saying the Virtual Machine service account does not have permission to access the iso file. I copied the iso file to the C: drive of my Windows 8 host and it accessed it with no problems.

    The disk used for the E: drive is connected using a SATA cable and is a conventional hard disk drive, whereas my D: drive is an SSD disk connected as a second drive inside the laptop itself. Once my machine has finished building, I am going to try and create a virtual disk on the E: drive using Hyper-V Manager and see if I get the same problems as I had with the D: drive.

    I'm now wondering if this is maybe laptop hardware specific rather than disk (BIOS, maybe?), but I'm going to keep plugging away and shall update this thread with anything I discover.

    Thanks for all your suggestions so far, Brian.


    Phil Childs http://get-spscripts.com

    Wednesday, August 22, 2012 9:46 PM
  • I too have this problem and more info to contribute.

    I have a VHD on an external drive.  Using eSATA connected to my docking station I'm able to mount and run the VHD without issue.  If I move that exact same drive to USB or eSATA on my laptop I'm unable to mount the VHD and get the access denied error.  There appears to be something different about the way the drive is presented to the OS when attached via the docking station vs. directly to the laptop.  Once I plug the external drive into the docking station it works fine again.

    Sunday, August 26, 2012 12:15 AM
  • Hi, what worked for me, but still think is not the best solution. Is to create a VHD (fixed) with use of disk management attach this and assign a drive letter and format as a simple volume. Then create a new Virtual Machine on the just created VHD.

    Remco van Beek

    • Proposed as answer by Remco van Beek Friday, August 31, 2012 6:03 AM
    • Unproposed as answer by Phil Childs Wednesday, September 5, 2012 8:37 AM
    Thursday, August 30, 2012 8:20 PM
  • I too have the exact problem. I used to have Windows Server 2008 R2 on my laptop with a C drive and an extra D drive. Hyper-V in that instance worked fine - on both drives. Now that I have Windows 8 and Hyper-V, I simply cannot use the second hard disk (same problems as described above) - general access denied errors.

    Could this be a bug in Windows 8 & Hyper-V & this particular second eSATA hard disk setup?

    Karel Deman

    Avanade Inc.

    Monday, September 3, 2012 3:20 PM
  • Anyone figure this out?  I am experiencing similar issue.  I have a dell laptop with two hard drives installed (D: one in the CD rom bay instead).  I want to move the HyperV folders to the D: drive because I have a smaller SSD system drive (C:).  When doing so I get the same message as Phil states above when creating a new VM.  I do not have bitlocker enabled so we can rule that one out.
    Wednesday, September 5, 2012 7:05 AM
  • I've also noticed another side effect of this issue. When I try and mount an ISO stored on an external drive to my VM I get the message "Failed to modify device 'Virtual CD/DVD Disk'. Hyper-V Virtual Machine Management service Account does not have permission to open attachment.

    If I copy the ISO to my C: drive then it mounts fine. I think I can assume that if the first issue gets sorted then this one will also be fixed.


    Phil Childs http://get-spscripts.com

    Wednesday, September 5, 2012 8:34 AM
  • Hi Jamin - not fixed for me. I think its a bug or a driver issue somewhere in Windows 8. It will probably be miraculously fixed after a Windows Update further down the line ;-)

    Phil Childs http://get-spscripts.com

    Wednesday, September 5, 2012 8:35 AM
  • I'm experiencing same problem with Windows 8 Enterprise.

    My computer has 2 physical drive - SSD for C: drive and SATA3 HDD(not removable) for D: drive (Also I tried with another removable disk). I can create VM on C: drive, but can't create it on D: drive by 'General Access denied error'. More strange things, I can create VHD on D: drive through New->Hard Disk, but can't attach it to VM. After creating VM on C: drive, then I tried to move it to D: drive, but it doesn't work.

    I know this problem caused by permission, then I try to solve the problem by giving full permission to several accounts using icacls.exe. (Hyper-V Administrators, Users, Authenticated Users, INTERACTIVE, and even for Everyone) but failed. Even I removed D: disk volume/partition and reassigned it, but result was same.

    Note I'm using domain account assigned to local administators, and tried to run Hyper-V Manager as Administrator but failed too.

    Thursday, September 6, 2012 12:27 AM
  • This is intersting.  Has anyone tried Server 2012 instead of Windows 8?  Is there a behavior difference?

    I have been running Server 2012 since September in various builds and have never seen this on my laptop or test workstations.  I do admit I do not use USB drives as those have just been historically problematic.

    One behaviour that I have noted is that I cannot use objects created at the root.  Such as D:\My.vhdx  It must be in a folder.

    I also simply have the common practice of using %users%\public just to avoid any permissions issues.

    This drive thing is interesing.  Have you check Disk Management?  Is the drive in question attached as Removable Media?

    I am going to play with one of my boxes as I have eSATA and see what I get..


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Thursday, September 6, 2012 3:42 PM
  • Hi all,

    I wonder if we are all using the same hardware: I have exactly the same issues, using an SSD in the expansion port of my Dell Latitude E6420. the same config worked fine running Server 2008 & 2008 R2. -

    Remco, I might end up using your solution in the interim but you gotta admit its ugly :)

    Phil, I get the same message when I try to mount an ISO my External USB drive.

    /Matthew

    Thursday, September 6, 2012 4:23 PM
  • Good point - mine is an E6420

    Phil Childs http://get-spscripts.com

    Thursday, September 6, 2012 4:26 PM
  • I just tried Remco's solution, mounting the VHD (which I created on a GPT partition on a simple volume on the VHD on the simple volume of the physical partition on the SSD) to a folder at the root of the SSD partition. I received the same errors as before although the new VM wizard did in fact create a folder for the VM.

    Mounting the same VHD to a folder on C: and tadah! it works.

    /Matthew

    Thursday, September 6, 2012 4:50 PM
  • I am using similar one as Phil (as we work for the same company :)): Dell E6420

    The secondary eSATA Harddisk is a SAMSUNG 830 SSD series mounted in a simple DVD replacement bay.

    Same config worked as well with Windows Server 2008 R2.

    //K.

    Friday, September 7, 2012 3:57 PM
  • I was also able to create a "standalone" VHD without virtual machine configuration file. The minute I want to link it with a virtual machine config, I get the "General Access Denied error" rap.

    So depending on what I do, I get a slightly (but related) error:

    Scenario #1: I add a new Virtual Machine (save it to the C drive) and add a new VHDX (save it on the D Drive). I get the following error:

    Failed to add device "Virtual Hard Disk"

    Hyper-V Virtual Machine Management service Account does not have permissions to open attachment.

    "Test Machine" failed to add device "Virtual Hard Disk"

    "Test Machine": Hyper-V Virtual Machine Management service account does not have permission required to open attachment "D:\HyperV\Test machine.vhdx": Error General access denied error"

    Scenario #2: I add a new Virtual Machine (save it to the D Drive) and add a new VHDX (save it on the D Drive). I get the following error (smaller error):

    The operation failed.

    Failed to create external configuration store at "D:\HyperV\": General Access denied error.

    The Operation failed.

    User "domain\user" failed to create external configuration store at D:\HyperV\: General access denied error.

    //K.

    Friday, September 7, 2012 4:05 PM
  • Has anyone tried Server 2012 in this configuration instead of Windows 8? 

    You all state it worked with Server 2008 R2 and Win 8 is client and distinctly different in multiple ways.

    I am also wondering if the OS sees this as removable media and if it is mounted Read/Write vs Read Only

    or if the new built-in AV / Anti-Malware is actually at fault somehow (again due to it being Removable media).


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Friday, September 7, 2012 4:11 PM
  • Hardware details:

    Dell Precision M4600

    Corsair SSD in main hard drive bay

    Hard drive caddy for second drive with Seagate 750 GB Hard drive

    Monday, September 10, 2012 3:46 AM
  • I am running a Dell Latitude E6510.

    Seagate Hybrid drive in main bay, does not matter what I use external, all get the same error unless connected to eSATA port on my docking station.


    Monday, September 10, 2012 5:53 PM
  • I have a 6330 with an SSD in the HD bay, and a 500GB HD in the drive bay.  I haven't had any problems creating new VMs on the D: drive...but I've created the VMs and VHDs completely through the Hyper-V management console.
    Monday, September 10, 2012 6:36 PM
  • In your case the drives are all local.

    I still think it is tied to the disk being detected as Removable.  jb7706 mentioned that it only works in his / her eSATA port - that would most likely not be considered removable by the OS.

    I stumbled on the following to disable writing to Removable disks:

    HKLM\Software\Policies\Microsoft\Windows\RemovableStorageDevices\{F33FDC04-D1AC-4E8E-9A30-19BBD4B108AE} set to Deny_Write to preventing writing to Removable disks.

    Since you all work for the same company, could there be a new security policy in place that is actually causing the block?  Are all the Win8 machines domain joined (Group Policy push to lock down drives not working as expected with HV)?  Or are they not?


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.


    • Edited by BrianEhMVP Friday, October 26, 2012 7:56 PM
    • Proposed as answer by ddarling85 Saturday, May 25, 2019 12:33 AM
    Monday, September 10, 2012 11:15 PM
  • Hi Brian,

    My computer is domain-joined, so there could be a link with GPOs I guess, although we don't all work for the same company on this thread :-)

    I've checked the registry and there is no RemovableStorageDevices key in the HKLM\Software\Policies\Microsoft\Windows path, but I agree that the OS is likely to be seeing the drive as removable, even though it is installed inside the laptop.

    Phil


    Phil Childs http://get-spscripts.com

    Tuesday, September 11, 2012 8:24 AM
  • Hi Brian,
    My compute is domain-joined too, I checked all GPOs but I can't found any special things. As Phil said, we don't all work for the same company on this thread - I'm working in Korea. :-)

    I don't have RemovableStorageDevices key in registry too.

    Well, you're suspecting 'Removable disk'.. it means the following statements on http://blogs.msdn.com/b/b8/archive/2011/09/07/bringing-hyper-v-to-windows-8.aspx is NOT TRUE?

    Hyper-V’s “Live Storage Move” capability helps your VMs to be fairly independent of the underlying storage. With this, you could move the VM’s storage from one local drive to another, to a USB stick, or to a remote file share without needing to stop your VM. I’ve found this feature to be quite handy for fast deployments: when I need a VM quickly, I start one from a VM library maintained on a file share and then move the VM’s storage to my local drive.


    • Edited by Jaewoo Ahn Tuesday, September 11, 2012 11:17 AM
    Tuesday, September 11, 2012 11:16 AM
  • Brian, 

    Why do you assert that smjain's disks are all local? The drive bay on the E6420 is the same kind of thing: the DVD drive that is normally in the media bay is replaced with a similarly shaped option but that contains a HDD. In the disk management section of the storage manager console the disk is not marked as removable.

    I have searched the registry on the  disk ID that appears in the "detail disk" command from diskpart and cannot find a reference to it being considered as removable. The disk has the same type attribute as the system disk.

    I can't see the reg path that you listed.

    For info my machine is domain joined and I cant see any Policy detail that seems related to removable devices being the issue.

    smjain it seems to be working for you, are you joined to a domain?

    If smjain is not domain joined I posit that the issue could be an authN issue as related in this aold post from  Jose Barreto http://blogs.technet.com/b/josebda/archive/2008/06/27/using-constrained-delegation-to-remotely-manage-a-server-running-hyper-v-that-uses-cifs-smb-file-shares.aspx

     I know it is not the same situation but there are similarities.

    /Matthew

    Wednesday, September 12, 2012 12:03 PM
  • I would agree with Matthew. My secondary HDD is inserted in a eSATA drive bay - just like the DVD drive bay. Nowhere is a mention of a removable device.

    //K.

    Wednesday, September 12, 2012 12:36 PM
  • smjain was one to mention the detail of the secondary disk being eSATA, which the OS should consider local.  That happened else where in this thread.

    And, this thread is not specific to this hardware, as others have chimed in as well on other configurations including USB devices.

    And there was not enough information to be sure that the way the device attached might not be considered 'removable' in any way by the OS.

    Not being familiar with the hardware I can only guess in attempting to help.

    I see that an A14 BIOS updates was released on 8/29.  One of the listed fixes is hard drive detection issues.

    http://www.dell.com/support/drivers/us/en/555/DriverDetails/DriverFileFormats/Product/latitude-e6420?DriverId=1WT16&FileId=3000326027&urlProductCode=False


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.


    • Edited by BrianEhMVP Wednesday, September 12, 2012 2:38 PM
    Wednesday, September 12, 2012 2:36 PM
  • Updated the BIOS to A14 - but that didn't change anything - still same issues. Anything else someone can suggest I have to do after this update?

    Karel Deman

    Friday, September 14, 2012 11:58 AM
  • As I see from all the postings, is that I am not alone....  :- )

    I have tried everything, in creating a VHD drive on anything OTHER than C:\"Whatever I Create Folder Name",  for which works.

    C:\ ( New Folder created for VHD's) is the only thing that works

    I have other drives physically attached, D:, E:, F:, G:, I:, and have tried creating a folder, checked permissions, compared permissions to the C:\Test folder that does work, and all drives OTHER than C:\Test, Fail with error:

    """Hyper-V Virtual Machine Management service Account does not have permissions to open attachment""

    """ New Virtual Machine": failed to add device 'Virtual Hard Disk  (Virtual Machine ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx""""

    """General access denied error (0x800700005)""""""""""""""

    Just my 2cents......

    Your not alone !


    RF

    Friday, September 14, 2012 3:07 PM
  • Just so that other may know the hardware being used, software drivers.

    Hardware:

    Intel P67 DP67De motherboard

    Intel i3-2120 2 Core CPU

    8 Gigs mem

    6 Drives, C: Drive is SSD, Others are all standard SATA II Western Dig

    Software

    Windows 8 Pro with all patches/ updates

    Intel's latest NIC drivers for Win 8 ( think 17.3)

    No Chipset Drivers installed ( or avail yet from Intel for Win8)

    Have .NET 3.5 installed, .NET 4.5 was removed due to older apps needing earlier .NET

    Just reinstalled .NET 4.5 and will test creations again.....( Don't believe this will have any results, but must make sure)


    RF

    Friday, September 14, 2012 4:08 PM
  • I have a ticket open with MS Technical Support and am working with them on the issues.  I have provided them with numerous dumps, logs, and other data. 

    I urge each of you to do the same to help boost the priority and give them additional visibility to the issue.

     
    Friday, September 14, 2012 4:15 PM
  • I want to create a cross reference to another thread on this same topic.

    So as this gets solved there is a linkage (I can split threads but not combine them): http://social.technet.microsoft.com/Forums/en-US/w8itprovirt/thread/245cb7e3-e95f-44cf-932e-bf6687199953/


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Friday, September 14, 2012 7:52 PM
  • I know this is a bit cheeky and doesn't solve the underlying problem as such - but I have actually switched my hard disks around - so put the HDD which was in the laptop drive bay in the DVD drive bay and vice versa. This solved the problem nicely. Machine boots up nicely, original C drive is still C drive; similar to D drive - so all apps work fine. 

    I can now create Hyper-V images on my D drive, which is now detected as a non-removable HDD as it now sits in the original drive bay. Problem solved.

    //K.

    Sunday, September 16, 2012 12:36 PM
  • That is strange.....

    Overall, I am thinking this has to do with Chipset drivers, as all the Intel P67 or H67 chipsets/boards are new, while the drivers with Win 8/ Win Serv 2012, install drivers that are dated 2006.......6 year old drivers ""Out of the box" for MBoards that are only a year old........I have odd drive issues with Hyper-v on Win 8, and on a newly installed Win Serv 2012, both systems had multiple 2nd, 3rd, 4th drives that anomalies with this other drives that Hyper-V.

    the only other thought I have is that both Win 8 & Win Server 2012 are using SSD's as C: drives, with 2nd, 3rd, 4th drives being standard SATA II WD's........but this would also tell me chipset drivers....

    out of 3 boxes, 2 that are 2012, one Win 8, I have issues with hyper-v on all 3...... All worked fine with WIn 7, Win 2008R2, and Hyper-v

    2 Boxes were fresh installs on C:, one was an upgrade......

    And the resolution search continues !

    :-D

    Swapping the drives, although may resolve it for what I am experiencing based up your results, leaves me in some awe, as this means I have to open up 3 boxes, to try to get hyper-v to play nice......

    Mac users would eat this up !!

    :-DD


    RF

    Sunday, September 16, 2012 12:56 PM
  • These issues are on top of the RSAT tools for Win 8....RSAT x64 installs on Win 8, but nothing shows in installed programs, or Turn On Features. I had been told to install the En-US language pack, tried it, but it was already installed ........

    The little issues are concerning in the scope of a new release......Never experience simple aspects that are issues with a new OS.......Be cautioned IT world.....


    RF

    Sunday, September 16, 2012 1:01 PM
  • Crossposting from this other thread around the E6420

    http://social.technet.microsoft.com/Forums/en-US/w8itprovirt/thread/beeb430a-24dc-44a5-8198-628c68688573

    Based on the reply i got this morning from prosupport, it looks as though there are some "known" issues within the dell engineering group around the E6420 and win 8.  I suspect a new BIOS or drivers is in the pipeline based on their email below.

    from: prosupport@dell

    ......

    Regarding the issue you have been experiencing with Windows 8 VM tool Hyper V actually the drivers have not been released by us to fix this issue yet as it is the early stages of Windows 8 release however we should have the drivers available by late October as confirmed with our snr techs.

    Perhaps your best bet is to stick with Windows 7 until then.

    Thanks

    ....

    Friday, September 21, 2012 1:51 AM
  • Thank you for that info.....The info you have provided confirms it to me, that there is issue with the drivers for all users who are experiencing this issue.  I had referenced anther similar issue posted on MS forums a while back with Intel server chipset that experienced this same issue....

    ====== My Previous post info  ===================

    I think this link below will provide the solution !!!!

    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/b9c91808-67ee-4123-9d42-1f323d4d97e1

    Search for the Reg Key and view the subkeys, you will see it is relevant to Hyper-V also.....there are 40 + subkeys

    Looks like this

    0000

    0001

    >>

    >>>

    >>>>

    0040   ( this key for me Shows MS Hyper-V Virtualization Infrastructure Driver)

    0043  ( this key for me shows Microsoft Hyper-V Virtual Disk Server )

    We just have to follow the info in the link on how to deal / process / fix it

    =======================================

    This issue I have with two 2012 Win Servers, also with Win 8 box......I had performed the steps ....but it has not cured the problem.....

    Hopefully this will be addressed either by MS, or by Intel updated chipset drivers....


    RF

    Friday, September 21, 2012 6:25 PM
  • I have the same pb with the following event in the Windows logs :

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
      <EventID>4656</EventID>
      <Version>1</Version>
      <Level>0</Level>
      <Task>12812</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8010000000000000</Keywords>
      <TimeCreated SystemTime="2012-09-25T10:12:46.829030700Z" />
      <EventRecordID>31524354</EventRecordID>
      <Correlation />
      <Execution ProcessID="752" ThreadID="760" />
      <Channel>Security</Channel>
      <Computer>toshm750.corp.avanade.org</Computer>
      <Security />
      </System>
    - <EventData>
      <Data Name="SubjectUserSid">S-1-5-83-1-625552963-1158575344-1810672012-2549433875</Data>
      <Data Name="SubjectUserName">25492E43-74F0-450E-8CA9-EC6B1346F597</Data>
      <Data Name="SubjectDomainName">NT VIRTUAL MACHINE</Data>
      <Data Name="SubjectLogonId">0x585a97a</Data>
      <Data Name="ObjectServer">Security</Data>
      <Data Name="ObjectType">File</Data>
      <Data Name="ObjectName">\Device\HarddiskVolume12\Hyper-V\Virtual Hard
    Disks\New Virtual Machine.vhdx
    </Data>
      <Data Name="HandleId">0x0</Data>
      <Data Name="TransactionId">{00000000-0000-0000-0000-000000000000}</Data>
      <Data Name="AccessList">%%1538 %%1541 %%4416 %%4417 %%4418 %%4419
    %%4420 %%4423 %%4424
    </Data>
      <Data Name="AccessReason">-</Data>
      <Data Name="AccessMask">0x12019f</Data>
      <Data Name="PrivilegeList">-</Data>
      <Data Name="RestrictedSidCount">0</Data>
      <Data Name="ProcessId">0xa88</Data>
      <Data Name="ProcessName">C:\Windows\System32\vmms.exe</Data>
      <Data Name="ResourceAttributes">-</Data>
      </EventData>
      </Event>


    Francois Michael Dain

    Tuesday, September 25, 2012 11:04 AM
  • I think I saw all the variations of this problem.  It should not be this hard.  I found a few things that might help,.

    Windows 8 Enterprise x64  

    HP EliteBook 2740p with no USB 3 would work fine on just about any drive I threw at it.

    HP EliteBook 8540P with USB 3 would not work with any disk.   Migrations, export/import.  Nothing. Always some kind of security or access message..  I have Seagate Freeagent 1TB USB 3 Drives that would be great for this.  SATA drive even exhibited the problem.

    My resolution.  Quite simple.  Made it a Storage Space.  Control Panel / System and  Security / Storage Spaces.  I made a simple, no resiliency space and used the Seagate drive. It just works.

    I have 3 Virtual Machines running on my Elitebook 8540P.

    Hope this helps.

    DW

    • Proposed as answer by Danny de Vries Wednesday, March 6, 2013 4:15 PM
    Monday, October 1, 2012 11:57 AM
  • I appear to be having the same issues

    I have a new Windows 8 Enterprise box, domain joined, with Hyper-V installed and running.  It is a custom Intel Ivy Bridge i7 3770 with 32gb ram.   

    I have a 1TB SATA disk in it, split into:

    •          C:\ 200GB  (Boot volume)  (NTFS) (MBR)
    •          D:\ 800GB (NTFS) (MBR)

     I also have an Intel SSD 120GB Series 3 disk:

    •          S:\ 120GB (NTFS)(GPT - as a test, was MBR)

     I have Hyper-V installed and running OK.

     SUCCEEDS:

    •          If I create a virtual machine in the default locations
      •    VM Path: C:\ProgramData\Microsoft\Windows\Hyper-v\Virtual Machines
      •    VHD Path: C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
    •          If I create a new folder on c:\ drive”
      •    VM Path: C:\Hyper-V
      •    VHD Path: C:\Hyper-V

     

    FAILS:

    •          If I create a new folder on D:\ -  D:\Hyper-v and try create  VM there (second partition of boot disk)
    •          If I create a new folder on S:\ - S:\Hyper-V and try and create a VM there (SSD Disk)
    •          If I create a VHD on the C:\ location, move it to the S:\Hyper-V folder and try to reference it

    http://www.oasystems.co.nz | OA Systems Ltd | CRM Solution of the Year at the Microsoft NZ 2010 Partner Awards

    Wednesday, October 3, 2012 9:56 PM
  • Thank You !!!!!

    I was starting to feel alone in the world with my problem....

    :- ))))

    Glad ( in an odd way) that someone else is dealing with this issue, and its not just ME, or someone thinking it is ME.

    Hopefully they can correct this issue soon....

    Again, Thanks for your feedback..and reporting the issue....

    Hello ? Microsoft?  Hello ?


    RF

    Wednesday, October 3, 2012 10:20 PM
  • I'm actively working with someone at Microsoft on diagnosing this issue, providing all sorts of logs and debug info, so i'll update when (if) I get a resolution.....

    Regan


    http://www.oasystems.co.nz | OA Systems Ltd | CRM Solution of the Year at the Microsoft NZ 2010 Partner Awards

    Thursday, October 4, 2012 5:54 AM
  • Hi  Regan,

    This link may provide further technical details info that could help MS resolve the issue. As there is another link that I had found & provided regarding the chipset driver issue that was also experienced a ways back with Intel Server Boards some time ago, Microsoft back then recommended making some Reg Permissions changes.....Follow this link and there is a link on my posting that was provided by another user some time ago with Part of the resolution....recommended by MS....I had found the same issue applied to the present situation....regarding the Reg Perm's

    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/089c4938-156c-4684-8d5e-fe05b9defd21/

    Ron


    RF

    Thursday, October 4, 2012 9:27 AM
  • Hi Ron

    I read through your threads and I'm not sure there is a chipset driver issue in this case... my "D:\" drive, which is also experiencing the same error, is simply a second partition of Disk0 which hosts my "C:\" drive.  Hyper-V Machines and Disks host fine on C:\ partition but not on D:\ partition

    My S:\ drive is an SSD on a different MB SATA port - its exhibiting the same error, but this one is actually a different physical disk.

    I will feed it back to them anyhow.

    Cheers

    Regan


    http://www.oasystems.co.nz | OA Systems Ltd | CRM Solution of the Year at the Microsoft NZ 2010 Partner Awards

    Thursday, October 4, 2012 9:45 AM
  • Hi Regan,,

    I had the same issue on initial install with multiple drives/ 3 boxes / 2 Win 2012/ Win8 OS's, using NEWER Intel 6 Chipset / 3 different motherboard models until I did this below ( prior issue that was experienced with another user / while using earlier Win Serv OS and Intel Server MS, but also applies to this to a 80 % degree.

    Its a little time consuming, helped some, but didn't totally fix it...all drives (4 connected) worked after this, other than the (1 Connected) eSATA port drive on all 3 boxes... 2 Win 2012 and 1 Win 8.

    I had spent a lot of time researching, testing, diagnosing, and in my mind there is no doubt this is a chipset driver issue......If you look at a fresh install of either Win 8 or Win 2012 the supplied Chipset drivers are mostly 4-5-6 years old, for which is not a good thing for many reasons.

    If you look at the link below, this is a issue with the Chipset drivers and Windows Server

    -------------------------------------------------------------

    I think this link below will provide the solution !!!!

    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/b9c91808-67ee-4123-9d42-1f323d4d97e1

    Search for the Reg Key and view the subkeys, you will see it is relevant to Hyper-V also.....there are 40 + subkeys

    Looks like this

    0000

    0001

    >>

    >>>

    >>>>

    0040   ( this key for me Shows MS Hyper-V Virtualization Infrastructure Driver)

    0043  ( this key for me shows Microsoft Hyper-V Virtual Disk Server )

    We just have to follow the info in the link on how to deal / process / fix it

    --------------------------This issue I have with two 2012 Win Servers, also with Win 8 box......I had performed the steps ....but it has not cured the problem.....

    -------------------------------------------------------------------

    Basically once the regkey permissions  changes you should see two more sub reg keys, after you perform the Permissions Change...>Take Ownership, ...the directions in the link will provide further info on how.,,,, ( if I remember 006 and 003 will show after the changes, also there is a Sub Key Value  named I believe Security , and you have to delete it.

    After I performed these steps, along with Installing the Intel Chipset drivers (Updating each Device from an decompressed Intel chipset .Inf file on every device to make sure it is using the latest driver on all devices. ( Intel Driver Build  was INF_allOS_9.3.0.1021_PV.exe, expand/ extract it and then update each Devices specifically) I was able to use all hard drives other than the interanal eSATA intergrated port / drive.)

    Keep in mind Any OS has to work with and use the Chipset Drivers to properly communicate with the lower level hardware MB/Hard Drives/ Vid/ Etc, and if the drivers out of the box ( Windows 8 & 2012 Serv) are 4-5-6 years old, you are at risk of the OS not communicating with the OS properly, It is like speaking Spanish when the other person speaks a little Spanish but mostly English, you will understand some things, but fail to communicate properly on others.....If this helps to understand it.

    How old is the system you are using ? What Chipset on the PC is being used? Model?

    Regards,

    Ron


    RF

    Thursday, October 4, 2012 10:39 AM
  • This is a massive bug or a 'feature' with incredibly poor documentation. If I want to locate a VHD on ANY drive I should be able to do it with Admin access. Windows 8 seems to have introduced a new idea (well.. old if you consider they are trying to clone OSX in many ways) but lost support for the tried and true processes we had in Win 7.
    Tuesday, October 16, 2012 5:05 PM
  • I've resolved it following this steps
    • Mount the VHD (double click on the file)
    • into disk management tool, put offline the disk
    • into virtual machine settings, remove the link to the old vhd's path, add a new physical hard disk and select the offline disk

    Et voila, The system can manipulate the vhd. :D


    Sunday, October 21, 2012 8:30 AM
  • That's sounds like something I would like to try as a work around.......I would still like for Microsoft/Intel to address the issue ......

    Cool Beans !


    RF

    Sunday, October 21, 2012 12:22 PM
  • Issue Resolved!

    Dell has posted an updated intel storage driver that resolved this issue. 

    The driver is available for download here:  http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/latitude-e6430-atg?driverId=2PWDK&fileId=2998372451

    • Proposed as answer by Jamin Mace Friday, October 26, 2012 6:35 PM
    • Marked as answer by Phil Childs Wednesday, October 31, 2012 1:40 AM
    Friday, October 26, 2012 6:35 PM
  • In the end: a driver issue that affected how the disks were recognized and thus utilized by the system.

    I know there was more than this particular Dell model in this thread...


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Friday, October 26, 2012 7:58 PM
  • Thanks Jamin - that worked for me!

    Phil


    Phil Childs http://get-spscripts.com

    Wednesday, October 31, 2012 1:40 AM
  • Not for me...

    Francois Michael Dain

    Wednesday, October 31, 2012 10:21 AM
  • Same problem here, Dell latitude 6510 Primary HD: SSD Secondary: harddisk bay.

    Any other solutions so far?

    Wednesday, October 31, 2012 10:43 AM
  • I've been setting up a remote kernel debug environment for the microsoft engineers to dial in to and try and figure out whats going wrong in my environment.  They will be accessing it shortly (next few days), so hopefully that will give them some ideas as to where things are going wrong.

    --

    Regan


    http://www.oasystems.co.nz | OA Systems Ltd | CRM Solution of the Year at the Microsoft NZ 2010 Partner Awards

    Wednesday, October 31, 2012 11:29 AM
  • Same issue with Latitude E5420 using USB2 or eSata ports.
    Wednesday, October 31, 2012 8:06 PM
  • We are all patiently waiting for MS and Intel to address this issue, hopefully a resolution to the Chipset drivers comes soon !

    RF

    Sunday, November 4, 2012 10:01 AM
  • Updating with the new Dell Rapid Storage driver fixed the issue for VM's on my second internal SSD, but not any on an external eSata drive.
    Monday, November 12, 2012 4:52 AM
  • Creating a storage space (simple, no resiliency) resolved the issue for me.

    BTW, I'm sing a USB 3.0 external disk connected to USB 3.0 controller in drive bay.

    Friday, November 30, 2012 10:01 AM
  • I'm seeing a very similar issue as well (in fact as far back as Windows 8 CP, I believe). In my case it's a USB 3.0 external drive plugged via cable to a Lenovo W520. The host controller is reported as "Renesas USB 3.0 eXtensible Host Controller - 0096 (Microsoft)" - I wonder if there's a similar driver update for this as well? Would love to once again have the ability to distribute my disk I/O for Hyper-V to that nice fast external drive... might try the suggested Storage Space fix.

    Brian


    Brian Lalancette | MCTS, MOSS 2007 / SharePoint 2010 | Twitter: @brianlala | Blog: http://spinsiders.com/brianlala

    Saturday, December 15, 2012 1:38 AM
  • I change the setting of [Audit Removable Storage] from "Not Configured" to "No Auditing" in "Local Group Policy Editor".
    Reboot is necessary after setting.


    Wednesday, January 23, 2013 7:54 AM
  • Not an option in Win 8 Local Pol?


    RF

    Wednesday, January 23, 2013 11:37 AM
  • Select 'Configure the following audit events:" but nothing else.

    BTW is this supposed to be a fix, or part of the troubleshooting?

    Brian


    Brian Lalancette | MCTS, MOSS 2007 / SharePoint 2010 | Twitter: @brianlala | Blog: http://spinsiders.com/brianlala

    Thursday, January 24, 2013 4:24 PM
  • Thanks for the reply/ response.

    I would think by the Policy Text Description most people would not figure that out, that ""Configuring the following audit events" means "" No Audit""

    Strange that MS labeled it that way now....

    I am going to give it a try, for the heck of it, and see if addresses the issue of Hyper-V not recognizing the 5th eSATA port on three of my Intel MB's, that have a SATA drive connected to the 5th on-board port, but are not now usable with Hyper-V 3, but worked perfectly with Hyper-V 2, and SCVMM 2008R2, but not SCVMM 2012.

    Your positing is the third time I have seen someone propose this as a solution, but I had previously found it hard to believe, as I believe the issue is rooted much lower in the Chipset Drivers / Intel, and Microsoft, as there was issues just like this with Intel Server boards some years back and with Hyper-V not recognizing the drive.

    If this setting works for me I will make sure I post the result.

    RF   


    RF

    Thursday, January 24, 2013 6:32 PM
  • Agree re: strange labeling. However... it worked for me! Hyper-V on Windows 8 can now use my external removable USB 3.0 HDD - amazing.

    Brian


    Brian Lalancette | MCTS, MOSS 2007 / SharePoint 2010 | Twitter: @brianlala | Blog: http://spinsiders.com/brianlala

    Saturday, January 26, 2013 6:30 PM
  • I have just tried the Local Policy setting to see if it addresses the Hyper-V issues with eSATA port /drive issues. It does not.  MS/Intel still have to get around to addressing this.

    Apparently it works for external USB attached drives based upon what you have said.

    We will have to continue to wait for the fix.....


    RF

    Sunday, January 27, 2013 11:50 AM
  • Hi all,

    issue is already addressed with case id 112111410007804 from Mid Nov 2012

    it's the same issue as in

    http://social.technet.microsoft.com/Forums/sr-Latn-CS/winserver8gen/thread/9807a799-bea3-46ad-92a5-732779135f98

    it's not possible to access a remote mounted share.

    after setting the above mentioned 'Audit Removable Storage' to ' No Auditing', I'm able to

    - mount the .vhd file within hyper-V
    - access the shared USB drive from remote

    regards
    AnDi


    AD

    Monday, January 28, 2013 7:37 AM
  • Hello,

    The issue / resolution you have posted with regards to changing Local Policy does not fix the issue of Hyper-V not recognizing a directly / internally attached drive to the eSATA port.......It apparently works for USB, but not eSATA.

    Keep in mind, the resolution posted for the USB issue is a Temp Fix, until MS address that specific USB issue, but again this doesn't address eSATA and the Hyper-VF issue....Turning off a Group Policy setting, is only a Temp Fix.

    MS has experienced this issue some years back with Intel Server Boards, and this issue is listed on their Forums....

    The issue here is for eSATA ports and Hyper-V not recognizing the drive....The resolution you listed is for USB, not eSATA ( internal motherboard ports)...

    I have already tried the recommended Local Policy changes that were listed, and it had no effect, nor did it fix the issue on Win 8 nor Win 2012 Hyper-V on 3 boxes.

    This is still an open issue that needs to be addressed by MS and Intel.

    Thanks anyway....


    RF

    Monday, January 28, 2013 11:04 AM
  • Hello,

    I tested a private hotfix from Microsoft today.

    This will fix the mounting of a .vhd file on an external device.
    The fix will be available within the next months - final testing is pending.

    This fix will also address the problem accessing a shared USB drive from remote.

    a KB article number is not yet available

    AnDi


    AD

    Monday, January 28, 2013 8:50 PM
  • Hi,

    Has there been any update on the status of this? Is there a KB # or official fix yet?

    - Brad

    Monday, March 25, 2013 7:02 PM
  • Hi

    I haven't heard any updated news on this issue yet being fixed, other than what has been posted here....

    Been patiently waiting, as I have three boxes that I still cannot use 1 drive on each that is connected to the eSATA MBoard on board ports....(1 Win8 hyper-V 2 Win Serv 2012 boxes).

    I am hoping they fix it with the upcoming "Blue"this summer.....or sooner......I don't want to revert back to hyper-V and Win 2008R2 just to be able to use the missing drives.

    Fingers crossed!!!

    Regards,

    Ron


    RF

    Monday, March 25, 2013 8:06 PM
  • I ran into this problem again the other day.  The internal SATA drive partitioned into C:\ and D:\ would not create volumes for hyper-V on D:\

    Steps I used to resolve it are as follows:

    1. change the "audit removable storage" setting to 'no auditing' as per earlier post

    2. delete and recreate the D:\ drive/partition

    3. Edit Hyper-V and set the default directory to D:\Hyper-V-D (without pre-creating a folder on D:\)

    4. Create a virtual machine and check that the files are in the correct directory.

    I don't know if it was sheer luck, some steps, or all steps that contributed to the solution.....

    Regan


    http://www.oasystems.co.nz | OA Systems Ltd | CRM Solution of the Year at the Microsoft NZ 2010 Partner Awards

    Monday, March 25, 2013 8:43 PM
  • Thanks for your feedback....

    I had tried the policy setting posted some time ago, as a last ditch effort, and it had not made any difference to the 3 systems I am experiencing this issue with. Also all the three systems I have experience this with, were not boot.

    Apparently the policy change seems to work for some who are experiencing this issue, I also notice it works for those who have USB drives....

    Fingers are still crossed for MS / Intel to address this issue soon.....

    Regards,

    Ron


    RF

    Monday, March 25, 2013 10:25 PM
  • @Ron

    Did you wipe and recreate your disks/partitions after making the policy change and rebooting? i'm pretty sure the policy change did nothing on its own, but that it started working after wipe/recreate of the partition.

    Regan


    http://www.oasystems.co.nz | OA Systems Ltd | CRM Solution of the Year at the Microsoft NZ 2010 Partner Awards

    Monday, March 25, 2013 11:10 PM
  • Hi Regan,

    When I installed Win Serv2k12 I formatted the drive I had experienced the issue with, but at that time there was no public knowledge of the Policy change aspects.....I have tried the pol change after it was known, but it did not work.....

    I have to migrate all the data I have on the one specific drive ( Win 8) and will give it a try on my local system ...and see if it works....fingers crossed.....but at the same time we shouldn't have to jump through these hoops to get something that was working under SCVMM 2008r2 & Hyper-V, but does not work with Win Server 2k12.......

    I will provide any feedback after I try this on my local Win 8 PC.....

    The other thought I have that keeps sticking in my head is that this issue was experienced some years back, and MS & Intel were aware of it, it happened with I think it was an Intel 5000  series server Mboard, as I had found the information on this.....

    I am still convinced that this is a chipset driver issue MS/Intel, based upon what I had tested and the information that I have found.....

    Thanks

    Regards,

    Ron


    RF

    Tuesday, March 26, 2013 12:36 AM
  • @ReganNZ and  Everyone Else...

    I have tried the Policy Change on one of my Win Serv 2012 boxes ......AND IT WORKED........Yaaaaaaaa !!!!

    Deleted Drive

    Formatted

    Applied "Audit Removable Storage" to none, GP to the domain ( for now, until MS fixes the issue)

    Created a New Drive and formatted

    Created a New VM Folder on the drive

    And Then Tested Creating a VM under that folder......SUCCESS !!!!!

    Thank You for the process, as I can now use the 3 drives that didn't work for my 3 boxes under SCVMM 2012/ hyper-v / Win 8 & Win Serv 2012.....

    I still hope that MS fixes this issue...

    Thanks Again

    Regards,

    Ron


    RF

    Tuesday, March 26, 2013 11:14 AM
  • Glad it worked this time Ron!

    I wonder if the policy gets set on the drive and can't subsequently be 'unset' by simply turning the policy off later, thus the reason it worked after scrubbing the disk and recreating.  Whatever the issue/workaround, it would be nice for this to "just work"... especially on Win8


    http://www.oasystems.co.nz | OA Systems Ltd | CRM Solution of the Year at the Microsoft NZ 2010 Partner Awards

    Tuesday, March 26, 2013 7:39 PM
  • Hi ReganNZ

    Thanks !!! I have taken care of all three boxes, reformatted drives, set Pol, and all is now working....with VM running off the drives...

    With regards to Unsetting the Pol, that is something I was wondering also,......Now that they work on the 3 boxes, I am tempted to test turning off the GP, and see what happens..

    The last time I had tried the Pol, I didn't leave the pol setting on, reverted back to no setting.....

    Now that it does work I am very tempted to test turning it off...

    If I do, I will post the results here......

    Í have also noticed something that may help others when using SCVMM2012, and experiencing this issue.....When a drive isn't recognized under SCVMM, there seems to be the Drive Identifier showing under SCVMM2012. Not sure if this is a definite  hint of that there will be the problem we have experienced, but it does seem to point to it.

    I will post once I test Pol Disabling

    Thanks again!!

    Regards,

    Ron


    RF

    Tuesday, March 26, 2013 7:52 PM
  • This is a follow up to the information I had posted about applying the "Audit Removable Storage" Policy Update that has been recommended to get eSATA drives to play nice, with SCVMM 2012/Hyper-V.........

    -========================================================================-

    I have tried the Policy Change on one of my Win Serv 2012 boxes ......AND IT WORKED........Yaaaaaaaa !!!!

    Deleted Drive

    Formatted

    Applied "Audit Removable Storage" to none, GP to the domain ( for now, until MS fixes the issue)

    Created a New Drive and formatted

    Created a New VM Folder on the drive

    And Then Tested Creating a VM under that folder......SUCCESS !!!!!

    =================================================================

    Based upon my testing, once you are able to create a new VM, you can disable the "Audit Removable Storage" Policy Change, and drive (VHD) creation still works on the same eSATA drive that didn't before the procedures above.

    Hope this helps.....

    Regards,

    Ron


    RF

    Wednesday, March 27, 2013 11:54 AM
  • Hi all,

    is solved with the April 2013 updates from Microsoft.

    http://support.microsoft.com/kb/2822241

    http://support.microsoft.com/kb/2811670


    AD

    Friday, April 12, 2013 5:17 AM
  • Thank You !!!!!

    Yaaaaaa We waited for some time on this being released from MS.......


    RF

    Friday, April 12, 2013 12:05 PM