Group: Forum Members
Typically just capturing an image of a Windows environment that was set up to run on physical hardware and trying to boot it in a VM environment will result in Windows failing to boot, because the Windows environment will be set up to expect (and load drivers for) a completely different set of hardware than will be present (virtually) from the hypervisor. Transplanting a hard drive containing a Windows installation from one PC into another will also typically result in Windows not booting for the same reason. That's why for the latter scenario, Reflect includes a ReDeploy wizard specifically designed to tweak a Windows environment to allow it to boot on dissimilar hardware, which is often used when restoring an image from one PC onto another one. viBoot does something similar because the same need exists in that scenario. In addition to allowing Hyper-V to use Reflect images as virtual disks, viBoot tweaks the image (non-destructively, by applying changes in a separate file) to basically ReDeploy it for running within a Hyper-V environment. Or at least that's what's supposed to happen.
If you encountered the same BSoD even when using a Reflect image as your source and using viBoot, I'm not sure what would account for that. There might be a "viBoot ReDeploy" log that Macrium Support can get from you to shed light on the issue, though. As for finding information about the Windows environment while it's offline, that MIGHT exist somewhere in the registry, and it is possible to mount an offline registry hive file in Registry Editor when you've got an offline Windows partition available, but I'm not sure where you'd look. That said, out of the items you mentioned, the only possible item I can see being relevant would be whether it's 32-bit or 64-bit, simply because Windows XP 64-bit wasn't very widely used or supported via drivers, so it's possible that viBoot would have trouble with ReDeploying for that OS -- but I'm not certain about that.
Still, I do find it interesting that you encountered this same issue even when using other tools that are meant to allow P2V, including making the necessary changes to achieve that.