I justy tried that and it stalled at 1% and wouldn’t work- (fortunately I have rollbackRX wich allowed me to roll back my system because I couldn’t even stop the converter job- there was no way to even stop it- I hit the “X” and it looked like it stopped, but it didn’t- the ‘job’ was still; running- Anyway- did a rollback to before I installed it- and back up and going again now)
I looked online for the % stall- but didn’t find anything (well anything that I could understand- they had one site with an instruction process- but my converter didn’t even have the features that they used I n their instructions-)
I’m gonna give paragon hard disk manager a try IF tey ever send me al ink to try the demo- They have never sent me a download link in my email- not sure hwat’s up with that-
That’s weird — I can’t recall ever having Converter fail.
The one problem you might have doing the virtualizing with something other than a utility from a VM company is that when you first boot the VM, it will see different hardware than it’s used to and the copy protection may kick in and make you re-authenticate. I doubt MicroShaft will still authenticate W7, given how much effort they’re expending to drag us all, kicking and screaming, to WX. If you virtualize with a utility from a VM company, they seem to handle all that in transparently. I’ve never seen it be a problem, anyway, where I have for example, trying to run virtual disks built under Virtual PC and used to Virtual PC’s virtualized hardware, under VMWare. You MIGHT get around that by running Sysprep before virtualizing, if that’s still around.