MacBook Pro 16" unable to import Bootcamp

It's shameful that Parallels seems to be making no effort to resolve this. This didn't work in 15 and doesn't work in 16. I spent a huge amount of time experimenting and poring over logs a few weeks ago and, I think, narrowed the problem (or at least the part of it that results in the <100mb import sizes.) I believe the problem is specific to installations where their drive has only a GPT partition table i.e. it doesn't have a hybrid MBR partition table that mirrors the GPT table. I would expect this to be true of anyone who has purchased a new MacbookPro in the past few years and installed a fresh copy of Windows 10.

The logs seem to indicate that, at first pass, Parallels at least notes the existence of the bootcamp partition properly but that looks more like something primarily for logging purposes. GPT partitioned drives still have a "protective" MBR partition that basically just bookmarks the beginning and end of the drive to prevent a non-GPT aware program from erasing the disk. The first partition on the disk (before the APFS container and bootcamp partitions) is the EFI partition containing the bootloader and some rudimentary drivers. It's formatted FAT32 and on my 16" MacBook Pro is about 300MB. What parallels seems to be doing is coming across the protective MBR header followed by the FAT32 partition and decides that must be the BootCamp partition so it imports that and then when it comes to the end of the partition and there is no more MBR information, decides it's the end of the disk or gives up or something, resulting in a quite useless disk image of the MacBooks' EFI partition. One particularly obnoxious part of this is that it doesn't even generate an error and attempts to boot a VM from the useless disk it just created, which of course finally leads to an error about no operating system installed.

It's also possible there could be some path issues where the process is running as root using relatively paths and therefore pointing to files in root's folder instead of the user's but I was unable to tell if that caused any real problem and could have just been junk in the logs.

So maybe very few customers actually buy a new mac, but a fresh windows install on a bootcamp partition and then decide to import it and that's why Parallel's hasn't bothered to even look at this. It certainly seems like something the software should be capable of and I think there is enough information here to point them in a promising direction. Let's hope they read this.

 

hello Michel, I haven't tried yet due to lack of time to reinstall everything osx on the MBR / APFS partition then install Bootcamp. I think that indeed the problem as you say it comes from the fact that it is a first MBR partition that Parallèle requests. However I do not yet know if BIG sur and Catalana will agree to install on a Macbook 16. Apple has already locked and I could not even start on an external drive where El Capitan was installed even after having unlocked the protection of the T2 chip. I also think that the problem may come from this.

 

So this has not been resolved yet? Same problem here only 74mb imported

 

Parallèle desktop is starting to be a big gas factory that doesn't do what it is asked to do !!! I am extremely disappointed to see that despite the requests we still do not have a solution to be able to import this famous bootcamp partition. Moreover during the last parallel update it caused me a problem I can no longer boot on my windows 10 partition at startup !!! So I plan to go to the competition because there we collect the problems and obviously the Parallèle team does not care !!!!

 

I also have this issue. please make a solution.

 

Guys, this issue has been reported to the Parallels Engineering Team.
They are continually working on issues that are escalated from our Support Team; however do not share an ETA for a fix until one is available.

We will contact you once we get any updates from the Parallels Engineering Team.

 

I have the same problem here on a MacBook Pro (16-inch, 2019). It is an important feature and should work!

 

I have the same problem on a 2019 27" iMac. Really frustrating.

 

Running the same issue here. MacBook Pro '13 2015 OS Catalina
please, notify me when it is solved

kind regards,
Katrina Lehmann

 

Add me to the list of people that would like a fix -- or at least a workaround -- to this. It strikes that checking the volume label to import the correct partition should be one of the easier steps in this migration! I'll observe that VMware Fusion is able to accomplish the task.

 

Hi, are you running the latest build of Parallels Desktop?

 

Running the latest build of Parallels Desktop on a 2019 16" MacBook Pro on Big Sur 11.2.2, I am having the same issue. The import process claims only 90 MB need to be imported (the partition is 140GB or so), and upon completion boots to a pale blue startup error. Mounting the new vm hdd file shows it created a normal sized uefi partition and a giant system recovery partition, but no NTFS partition with the contents of the boot camp C: drive.

 

Add me to the list as well. 2018 Mac mini on Big Sur 11.2.2. Sad panda.

 

Hello, could you create a tech report once the issue reoccurs and post the report's ID here please?

 

I've created tech report 364249680.

 

Tech Report ID 364343274

 

Same issue, MacBook Pro 13 2020 with Big Sur.

 

Tech report ID: 365692441

 

I upgraded to Parallels 16.5 and was able to successfully import my bootcamp partition. However, the partition only had 140gb of data and the newly created vm file is 430gb. The configuration panel shows no space as reclaimable.

 

I am new to parallels, can someone please help me solve this issue? I have also tried to upgrade the parallels to version 16.5 but no use in that