Live view not seeing mounted disk image

There are a few issues that you may be having here.
Firstly what is the OS of the drive you are attempting to VM? Live view is quite old now (unless a new version has been released) and things like GPT disks are probably not going to be supported.

In terms of the mounted FTK Imager not showing up in disk management, they never do. FTK Imager doesnt mount the disk as a true physical disk, it uses a workaround. This can cause problems if you start plugging USB pen drives in after the image has been mounted as the system thinks physical drive x is free even though FTK Imager is using it.
For a true physical disk mount, try Arsenal Recon Image Mounter (Free, works in all Windows OS from 7 to 10) or Encase PDE (definitely second choice).

I would try creating a VM from the machine without using Live view. The 'Just ask Weg' website (http//justaskweg.com/) contains lots of tutorials on how to do this and we used many of these for VMing Windows 8/8.1 computers, prior to VFC working properly, or when Live view failed on any machine.

Last, but not least, you can convert the E01 to a dd file and then into a VMDK file (lots of free Linux utilities for this) an create a machine and attach the created VMDK and boot from that.

Hope this helps

For a true physical disk mount, try Arsenal Recon Image Mounter (Free, works in all Windows OS from 7 to 10) or Encase PDE (definitely second choice).

And also in XP, 2003 and Vista/2008.

http//reboot.pro/topic/18945-announcing-open-source-virtual-scsi-miniport-driver/

jaclaz

For a true physical disk mount, try Arsenal Recon Image Mounter (Free, works in all Windows OS from 7 to 10) or Encase PDE (definitely second choice).

And also in XP, 2003 and Vista/2008.

http//reboot.pro/topic/18945-announcing-open-source-virtual-scsi-miniport-driver/

jaclaz

Thanks! I wasn't sure how far back it went, very good utility though - especially as its free )

I've used Liveview quite a bit over the years to generate VM's directly from mounted E01 image files, however I'm having an issue I've not come across before.

I'm mounting an E01 format image file acquired by Xways, using FTK imager. The mount works, I can see the volumes via Windows Explorer and Xways, VMware etc can all see the drive and volumes.

Liveview on the other hand can't see it at all.

Interestingly the mounted drive doesn't appear within Windows disk manager so my assumption is that if Windows disk manager can't see it then Liveview can't see it, which I find confusing as I've never had this issue before.

Analysis machine running Win7 x64.

Does anyone have any similar experience or idea on how to fix/work around?

did u run liveview as administrator?

Run liveview as administrator

Thanks for the replies people

Running as admin didn't make any difference, and it's a Vista machine which should be supported by Liveview (at least the OS is listed within).

I ended up taking a DD image from the E01 image and going down the 'create VDMX' path as suggested, now I have the BSOD boot loop happening when I try to launch the VM.

I'm not optimistic ?

The BSOD is usually a driver issue on the machine.
VM's seem to create as SCSI disks and often cause the virtual OS to crash, usually around the windows logo loading.
The just ask weg site in my last post has some details on how to avoid this.

The BSOD is usually a driver issue on the machine.
VM's seem to create as SCSI disks and often cause the virtual OS to crash, usually around the windows logo loading.
The just ask weg site in my last post has some details on how to avoid this.

BSOD do not exist.
BSOD with a given STOP ERROR do.
Likely it is a 0x0000007b one which is not - properly - a "driver issue" (though it is a "driver issue" wink ).
Check if in the VM descriptor file the LSCSI controller is used (if it is try to enable the driver in the Registry)
http//justaskweg.com/?p=7
or "force" the VM to use the IDE interface.
Even if the VM has been set to use not the SCSI disk, but rather the IDE type, it is possible that the install was on "real hardware" on a SATA machine and this can cause the same type of error.
The 0x0000007b means inaccessible boot device, for the good ol' XP there was the Fixide
https://www.foolishit.com/free-tech-tools/fixide/

For 7 there is the nice tool by cdob
http//www.911cd.net/forums//index.php?s=&showtopic=24245

Really cannot say if something like that exists for Vista.

jaclaz