Macbook Pro 16 inch

Hi Tim,

First, thanks for all your efforts here, it’s much appreciated

Second, I’m afraid the documented process didn’t work for me Following the instructions to the letter, I noticed the following differences in behaviour:

1. TouchBar didn’t enable even after ten minutes waiting (confirmed driver presence in directory on Flash drive). So, I attached an external keyboard to get the CMD prompt up.
2. My Boot Camp was drive E, not D. Modified the Winclonefix.bat accordingly.
3. Ran Winclonefix.bat and got ‘drivers installed successfully’ responses
4. Restarted back into macOS, was able to set Boot Camp as the startup disk.
5. Rebooted into Windows but got the same error as before:
   
   

   IMG_7155800×600 515 KB
   
   Any suggestions? Thanks!
   (By the way, the Windows ISO I used was SW_DVD9_Win_Pro_10_1809.1_64BIT_English_Pro_Ent)

I usually do my migrations without sysprep. If I am having boot issues that are blue screen / boot related and I can’t get to the desktop is what I turn to sysprep. Haven’t had to do that in a while.

tim

OK, that is strange. if you do a

dir d:

what do you get? I am curious what gets mounted on d:. Could be a clue.

The touchbar driver is strange as is the keyboard not working. Can you post a screenshot of the contents of the thumb drive? I want to make sure it is set up correct.

You can also manually load drivers in the Windows command prompt by running drvload c:\path\to\inf\file, so to load the driver manually run:

drvload c:\AppleDrivers\AppleKeyboardInternalUSB\AppleKeyboardInternalUSB.inf

The keyboard should then start working. Also, make sure there is no WINPEDriver folder at the top level of the flash drive.

tim

What error message did you receive? When I run setup.exe, it asks me to repair and when I do that, all the drivers are then installed.

tim

Hi Tim - I will anyway have to redo it again as my macbook got screen flashing which seems to be a hardware error. Im sending it back and it will take a while before I get a new one. I will may try to redo that procedure with your new instructions and see if that works better. I also felt that the drivers havent at all installed correctly before especially because my 5k 34" Thunderbolt 3 display from LG hasnt worked in windows. I may also think about to installl bootcamp regularly and see how I transfer the programs and data manually. Did your macbook pro 16" worked properly without doubt that something could be wrong in the setup or functionality? I felt that my one really worked not so well and made a lot of fan noise for basic office tasks.

I have not used it in Windows enough to get a sense of how well it worked. I have not heard others report that, though.

tim

Hi Tim,

To clarify: the MacBook keyboard was working, but it looked like the Touch Bar wasn’t. So, I used the external keyboard to get an F10 key

OK, so I finally got some time to do some digging

Results:

• That ‘D’ drive turned out to be a fake drive added by the firmware in the USB-C hub I was using. I tried to add the output from diskpart but the forum will only allow one image to be attached.
• Turns out the Touch Bar /was/ working, it just didn’t illuminate until I hit the fn key.

The thumb drive content looks like this:

(Switching USB-C hubs to a simpler one which didn’t support MicroSD etc., got the Boot Camp partition to show up as drive D.) While still on E: I ran the operations from Winclonefix.bat and got these results (the second snapped just before the reboot kicked in). Screenshot images to be added, forum only allows one per post

Unfortunately I still get the same error (0xC000000F, A required device isn’t connected or can’t be accessed) when I try to boot from the Boot Camp partition.

Hope this helps with your diagnostic efforts!

Shot 1:

IMG_7158D800×600 127 KB

Shot 2:

IMG_7159D800×600 154 KB

Shot 3 (the output of the wmic command) can’t be added as I’m only allowed 3 new posts in the topic. Maybe another day

I think I see the issue. The EFI partition is volume 4. How did you format the drive? Disk Utility always makes EFI volume 1.

tim

I was able to clone a partition from my 16" to my Samsung X5…I get the inaccessible error trying to boot that. I notice after I dism merged everything in the PE folder you then said not to merge either the non apple stuff or the intel stuff. Do you know what drivers I can remove with DISM that will make it boot?

Dear Tim

I got my new macbook pro 16" replaced back and tried to follow the new process with your video. The good thing was that I could much easier boot windows based on my old bootcamp partition without problems. No external keyboard and the drivers installed with the command function succesfully.

After login into my windows the problems started. I could not install all drivers and always got the error message error bootcampdriver.exe after several tries my screen gets black and the bootcamp partition gets useless. Somebody experienced these problems as well? Of course the windows partition didnt worked well for the short time I could use it for example wifi connection didnt worked or external monitors didnt worked (believe the thunderbolt 3 drivers are not installed) etc. etc.

Tim coudl you use in your case the bootcamp setup exe without problems?

Close to give up and reinstall e fresh bootcamp partition but would give the thing a last try.

Not to be too down on the Winclone product, although I have preferred to go the cloning route, both for macOS and Windows, from 2011 until this fall, on this new system my only viable options were:

Booting my cloned macOS from an external drive to the new Macbook failed, due to missing hardware drivers in 10.15.1 (10.15.2 probably has these).

With this 16 inch Macbook, as soon as things got really hairy, it became clear that the following software, that I rely on, wasn’t quite ready:

Winclone 8
Paragon Software’s filesystem driver suite.
VMware Fusion

So, I did migration assistant (just applications and system) of macOS.

For Windows I built up the system totally from scratch (time consuming, but straightforward).

–

I also am not terribly confident in APFS, so only my macOS system in APFS, my home folders, etc are HFS+.

–

FYI:
I went through a similar set of steps this past September, with the 2019 15 inch Macbook Pro, and Winclone/Paragon performed as advertised.

However, this was my first T2 Mac, and I really messed up big time.

I made a series of mistakes that required me to bring the system into the Apple store in order to get the system out of it’s totally ‘bricked’ state. [internet recovery spins forever, pin prompt, with no valid entries accepted].

After Apple repaired the system (I had to sign some ‘interesting’ paperwork), I got my cloned Windows and macOS booting fine.

–
My next project is to try and get Fedora Linux booting natively on the 16 inch.

Since Fedora is free, I can live with quite a bit of finicky software.

–

Once I am all done, my goal is to achieve what I had with the 2015 Macbook Pro:
Triple Native Boot (macOS, Windows, Linux).
VMWare bootcamp support, under macOS physical host, for BOTH Windows and Linux (using VMware RAW disk partitions).
Access to all partitions, from all booted O.S.s (except for APFS on T2).

–
Why do I do this? It is ‘fun’…

Hi Tim,

Sorry for the delay; the disk was formatted by the Boot Camp Assistant. Could you tell me which command relies on EFI being volume 1 so I can try to work around the problem? Thanks!

In case it helps, I can see the drivers (oem65.inf-oem72.inf) have been copied to the \WINDOWS\INF\ directory by DISM as expected, and setupapi.offline.log shows the SSD files installing correctly (and I can see them in \Windows\System32\DriverStore\FileRepository\applessd*).

Replying to my own post … after much investigation, I found the root cause of the problem in the GUID partition table (GPT). At some point in the ‘Install Boot Camp’ and ‘WinClone recovery’ journey, the original EFI system partition (ESP) at index 1 had been removed, and a new ESP created at index 3. This must have been after the first BOOTCAMP partition was created, as that was at index 2. I managed to boot into macOS and Windows using Option+startup but quite a few parts of macOS were broken. (For example, Disk Utility refused to recognise the ESP at index 3, and bless was very upset with the configuration.)

What was interesting was that the GPT also included an unallocated 105GB space following index 3, which matched the size of my original BOOTCAMP installation. So that would have been an index 4 partition, created after the new ESP. Curiouser and curiouser.

I removed then re-added a native BOOTCAMP partition via the Boot Camp Assistant, but the ESP stayed where it was (of course). I even re-installed macOS but the ESP was still at index 3. Finally, I removed and recreated all the partitions in the GPT by hand, in the right ‘order’, which got everything working, but no BOOTCAMP partition showed up in System Preferences | Startup Disk, so there was still something awry.

I’ve since removed the BOOTCAMP partition using Disk Utility, whereupon it grew the APFS container to fill the disk, re-capturing both ex-BOOTCAMP partitions. Now it’s a macOS-only Mac, and the disk is fully used. Next step is to use the Boot Camp Assistant and set up a clean install of Windows.

My configuration was a Windows 10 Bootcamp installation from a 2015 Macbook Pro. I used TwoCanoes WinClone 8 to make a backup of my drive.

i got this working pretty quickly. Here’s how i fixed it.

You may have to download a trial copy of VMWare Fusion if you don’t own it.

• Copied the Windows 10 ISO to my desktop.

• Kicked off the bootcamp installer and partitioned the machine to my desired configuration. I let the machine reboot and start the install. I stopped it once it started to configure windows.

• Shut down and rebooted the machine into my Mac’s OS

• Used WInClone to restore my Bootcamp Partition and got confirmation that it was successful.

• Opened VMWare Fusion and imported my bootcamp partition. Choose the option to run directly from Bootcamp, not to import and create a new VM. Just use the actual drive.

• Booted the Bootcamp via VMWare Fusion. it rebooted a few times making sure it could boot properly. I also did all required updates to windows.

• Shut down Bootcamp gracefully through VMWare Fusion

• Opened the Bootcamp Assistant, and clicked the Action Menu --> Download Windows Support Software. I then copied the support software to a thumb drive.

• Opened VMWare Fusion. Edit the BootCamp VM and set the Windows 10 on the desktop ISO to attach to the Fusion’s CD Rom.

• Boot the VMWare Fusion Bootcamp Partition. Immediately click inside and make sure your mouse is inside the VM. Start clicking ESC right away. You’ll be prompted with a boot menu.

• Boot the EFI VMWare Virtual Sata CDROM. Make sure you configure VMWare to enable the ISO

• Once you boot from the ISO, Click next then click Repair

• Click Troubleshoot

• Click Command Prompt

Run a DIR on your drive. Your C: drive should be your bootcamp partition that you restored.

• Attached the USB Drive with the Windows Support tools to my newly imported Bootcamp partition and run a DIR on that drive to confirm the drive letter. Mine was E:

Once you know your drive letters you’ll type the following

dism /Image:C:\ /Add-Driver /Driver:e:\WindowsSupport$WinPEDrivers$ /recurse
! Make sure your C: drive is your Bootcamp and your E: drive is your thumb drive. Change the drive letters accordingly.

Dir987×519 30.8 KB

• Once i got confirmation it was successfully completed shut down my Virtual Machine and rebooted by holding down the OPTION key and went into bootcamp.

• My machine rebooted twice, but i was able to successfully get back to my restored image.

I hope this helps people that got stuck. If you get stuck, you can email me at "listeningquietly @ gmail . com "

Thanks for posting this. I’ll try and repeat the steps then put a kbase up on the site for others.

tim

Hi Tim,
I was able to do the most of the cloning process to the new Macbook 16". During startup at the command prompt, I am not able to address “c:/winclonefix.bat”. It shows me a pre-set like X:\sources> and I don’t know how to accomplish this last step from cloning my windows 10 image. I was not able to find any help for this topic online. Can you please help to get this addressed>? Thanks

you should be able to type in:

c:\winclonefix.bat

and it should run the script.

I am having problems my new Macbook pro 16 10.15.3 injecting the drivers. I have imaged and restored using Winclone 8, but I am stuck trying to get into the DOS cmd prompt using the Fn key to display f10 is not working. I have no response from the keyboard or touchpad and have redownloaded the Apple drivers.

I am using the lasted Microsoft windows 10 1909 iso and using Bootcamp 6.1.0.

What can I try?

Thanks,

Rodney