Windows 10 install on bootcamp partition problem

VMWare Fusion can attach and boot my bootcamp partition of windows 10 without any problems, but I cannot get it to work with parallels. When I try to boot, it hangs at trying to boot from SATA1. I have tried the volume.inf trick and 2 other KB articles I found, but that hasn't gotten me anywhere either. Has anyone gotten Windows 10 to successfully boot from their bootcamp partition? Fusion works ok, but it's nothing like the speed of parallels...

 

Hi ErikT2, Please follow the steps suggested at http://kb.parallels.com/122808 and check if the issue still persisting.

 

Although it's a bit different (and newer) from the previous volume.inf file replacement KB article - I was able to get the volume.inf file replaced last time and it still will not boot the VM. Any other options available?

 

I stand corrected - when I do the following (Even tried the paragon route this time) it starts and gets past the SATA1 error, but now it gets stuck in an infinite loop of Preparing Automatic Repair. What can I do to get past this problem?

 

I have Windows 10 Enterprise build 10130 installed in bootcamp right now. Does the Enterprise version cause this conflict? I'm downloading the pro version now, but since I will be using this as a test work machine, I need Enterprise to work in parallels... thoughts?

 

YEP... the volume.inf must be only for pro - I installed win10-pro just the same as I've done in the past with Enterprise (7 times total with enterprise now), and first try with Pro, it saw the volume after the INF replacement and boots to it just fine. I did have to reinstall the parallel tools a second time to get file sharing working - but so far so good! Perhaps you guys can update the volume.inf to support the enterprise version of windows as well? Or maybe it's just the latest version to date of Parallels that doesn't work with Win10-Enterprise. Thanks for the feedback and tempting me to start over once more. I couldn't stand how sluggish VMWare Fusion was.

 

Hi Erik,
Please submit a Problem Report ID http://kb.parallels.com/9058 and provide us the ID number here. We'll check it for you.

 

I have the same problem and I got the same behavior when I followed the instructions above. I have a brand new macbook pro with 10.10.4 and bootcamp with windows 10 insider preview. After I installed the Paragon NTFS preview and copied the volume.inf file and deleted the old VM's it recognized the bootcamp partition and offered it as an install option. It then installed and booted to a windows fix/repair screen with a parallels dialog box that said "you must now log in to your windows machine to complete the installation", but it never gets any further than that. Please help, the reported ease of accessing the bootcamp partition is the main reason I am considering the purchase of parallels. Could it be the nature of the solid state memory on the new MBP?

 

I just submitted one ID#69074848.

 

Hi All, please try this workaround and check how it works, http://kb.parallels.com/122808 Currently Windows 10 OS is under experimental support in Parallels Desktop 10.

 

Yes I had already done that and thought it was clear in the post. It got me from "no boot device" to windows 10 blue repair screen. I got that far in Virtualbox now too. I will try again in case you updated the volume.inf file. I think it is trying to install parallels tools on the windows side but failing. I am trying to manually install tools, but can't get the iso to show up without the VM running. Is there a way to get the tools iso to the bootcamp partition directly and install it by booting to windows?

 

The 122808 instructions also refer to http://kb.parallels.com/en/113658 to install the machine, which is an instruction for importing the bootcamp machine to a virtual machine that would then be used separately. This defeats the purpose of running the bootcamp partition in a virtual machine because I was to save disk space and also keep one windows machine with all the installations and files that I can access in a window or boot to natively for speed. If the process in 113658 does something different please let me know.