I have Catalina 10.15.3, latest Parallels version on a 1 TB OWC Aura drive in a mid 2014 15" rMBP.
I've got Boot Camp running, having imported its clone from my previous Apple 500 GB HD, via Winclone, on a 200 GB partition.
Boot Camp itself runs in active mode perfectly. I can toggle from Legacy to EFI boot mode and back in Boot Camp, and both will boot up on my MBP in either mode. I have used Winclone clones of Boot Camp in the past with no difficulty when I had Mojave and earlier, and have always been able to create a Parallels VM or import Boot Camp into a standalone VM without difficulty.
IOW, there are two new variables: Catalina and the OWC Aura drive.
The Winclone people say that this is no problem with their Boot Camp clones, or at least nothing they can figure out with respect to the VMs. And again, the native Boot Camp itself from their clone works perfectly, just like Boot Camp installed from Apple does.
I've tried all sorts of hardware configurations in Parallels, like EFI and various options in the Windows error screens, all to no avail. All I get is one of these two screens.


So--does anyone have any idea as to the cause of this? Or how to get around it?
If Parallels says it is a Winclone problem, and Winclone says it is a Parallels problem, isn't there some way the two developers could get together and figure it out? Or maybe someone in this forum can do it.

I've got Boot Camp running, having imported its clone from my previous Apple 500 GB HD, via Winclone, on a 200 GB partition.
Boot Camp itself runs in active mode perfectly. I can toggle from Legacy to EFI boot mode and back in Boot Camp, and both will boot up on my MBP in either mode. I have used Winclone clones of Boot Camp in the past with no difficulty when I had Mojave and earlier, and have always been able to create a Parallels VM or import Boot Camp into a standalone VM without difficulty.
IOW, there are two new variables: Catalina and the OWC Aura drive.
The Winclone people say that this is no problem with their Boot Camp clones, or at least nothing they can figure out with respect to the VMs. And again, the native Boot Camp itself from their clone works perfectly, just like Boot Camp installed from Apple does.
I've tried all sorts of hardware configurations in Parallels, like EFI and various options in the Windows error screens, all to no avail. All I get is one of these two screens.


So--does anyone have any idea as to the cause of this? Or how to get around it?
If Parallels says it is a Winclone problem, and Winclone says it is a Parallels problem, isn't there some way the two developers could get together and figure it out? Or maybe someone in this forum can do it.

