Mounting vmdk image using AIM (gui or cli) on a virtual machine does not work about arsenal-image-mounter HOT 4 CLOSED

Oh all right, I did not know that. I had never faced this issue before.

I will take a look at the 'fake disk signature' and I could still use another VM to mount the vmdk image. I use this particular image to make some tests but at the end, it won't be used on my own image so it would not be a problem anymore.

Thanks a lot for your help.

from arsenal-image-mounter.

Thanks for your report. I do not think we have seen any similar problem before. There should be no need to upgrade .NET or any other components on Windows 10 either. Not sure really where to start here, but if you open Disk Management in Windows in the virtual machine, does it show any messages about the mounted virtual disk? Is there anything in system event log that could give any clues?

from arsenal-image-mounter.

Thank you for your quick reply.

I have just check the diskmgmt and here is the result I get when I use provider=DiscUtils. The disk is not initialized, but I can't initialize it by myself because it is mounted in readonly.

I also tried to mount the vmdk image with provider=None to compare. Apparently, the disk is not initialized neither but in this case, even the size of the disk is not correct (40Go). In fact, the image I am trying to mount is the vmdk of the VM I am working on. So Disk1 should be similar to Disk0.

It seems that the disk is recognized (127Go) but fail to initialize. When I check the diskmgmt from my host computer, everything is fine, the vmdk is mounted and I have 2 partitions (the "System Reserved" one and the "Bitlocker" one).

from arsenal-image-mounter.

Ah, "In fact, the image I am trying to mount is the vmdk of the VM I am working on. So Disk1 should be similar to Disk0." There is the problem. You cannot have two disks with identical signatures online simultaneously in Windows. This means that you cannot mount an image of a system disk within the OS booted from that system disk. If you mount it read/write and online the disk in Disk Management, Windows will automatically create a new disk signature for it, which will invalidate any directory mount points, BCD records etc that might point to partitions within that image.

To workaround this problem, we have the "fake disk signature" option in Arsenal Image Mounter. I would recommend that you try that and see if it helps!

from arsenal-image-mounter.