Also, since no physical discs are involved, it has become the most common medium to ship software and other information over the internet. What you imaged (and conversely what you mounted) is critical, since windows 7 at least, a large number of machines have been installed (per MS instructions) with two volumes a "system" one (containing the "boot" files) that normally is NOT attributed a drive letter, and a "boot" one (that contains the "system" files) that normally get drive letter C, if the source was setup like that you should have two volumes mounted (and accessible from the VM).Īnother possibility is that the disk is GPT (coming from a physical UEFI machine) and the (virtual) machine has been set to BIOS (as opposed to UEFI) boot.On VirtualBox, if you create a virtual machine or install an application on the guest machine, you will probably need to mount an ISO file to access the setup files.Īn ISO file is a container (also called a “disk image”) containing an exact copy of all the contents available on a physical disc. Provided that the image is valid, it is entirely possible that for *whatever* reasons it doesn't work, I would rather boot the VM from a grub4dos floppy and inspect the contents of the forensics image. cannot possibly) boot (and I doubt also the Physical ? ). The logical mount in FTK imager won't ever (i.e.
Try using the Arsenal Image Mounter instead The image file contains a installation of Windows 10 64-bit. I've also done a physical as well as a physical and logical mount in FTK Imager. the image will have some SATA drivers enabled and you will need to switch to IDE/ATA ones, using something *like* it is impossible to understand what is happening and (hopefully) solve the issue.Īs a side note, the suggestion on the referenced site about enabling LSI_SCSI or LSI_SAS drivers make no sense whatsoever as in 99.99% real cases/hard disk images those drivers won't be present at all in the disk image, rather the opposite will happen i.e. FGA/problem-report-standard-litany.htmlģ) What EXACT settings you have (or had if they changed)Īt first sight it sounds like a mis-setting in "boot priority" of the VM, but without knowing EXACTLY what (virtual) device(s) are connected to the machine, where they come from what they contain (or should contain), etc., etc. You will need to go through the "standard litany" Http// But once that is fixed, you are not providing anything meaningful in terms of data needed/useful in assisting you with your issue. For some reasons the link you posted doesn't work (most probably it has been copied/pasted incorrectly) should be
0 kommentar(er)
