I can no longer boot into my Windows 7 Boot Camp partition. I had created a third partition for installing Mountain Lion to test some old software so maybe that's the reason? How do I get back into Win7 Boot Camp?
MacBook Air 13", macOS 10.14
Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes). The only values that need modifications are the Boot flags and step 10. Accept all other defaults that Gdisk offers. Please see thesample Q&A as an example. These steps can be repeated if you make a mistake before you get to Step 12, otherwise start from Step 1 for these steps. Step 6 has numbers which are typed with a space between the numbers. Please see the sample Q&A before you execute these steps.
Here is sample Q&A for this section. Please notice the Press Enter/Return.
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y
Creating entry for GPT partition #2 (MBR partition #2)
Enter an MBR hex code (default AF): Press Enter/Return
Set the bootable flag? (Y/N): N
Creating entry for GPT partition #3 (MBR partition #3)
Enter an MBR hex code (default 07): Press Enter/Return
Set the bootable flag? (Y/N): Y
If you are asked about additional space, say 'N' and continue.
Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes). The only values that need modifications are the Boot flags and step 10. Accept all other defaults that Gdisk offers. Please see thesample Q&A as an example. These steps can be repeated if you make a mistake before you get to Step 12, otherwise start from Step 1 for these steps. Step 6 has numbers which are typed with a space between the numbers. Please see the sample Q&A before you execute these steps.
Here is sample Q&A for this section. Please notice the Press Enter/Return.
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y
Creating entry for GPT partition #2 (MBR partition #2)
Enter an MBR hex code (default AF): Press Enter/Return
Set the bootable flag? (Y/N): N
Creating entry for GPT partition #3 (MBR partition #3)
Enter an MBR hex code (default 07): Press Enter/Return
Set the bootable flag? (Y/N): Y
If you are asked about additional space, say 'N' and continue.
Can you download and install GPT FDisk (https://sourceforge.net/projects/gptfdisk/)? This will help us create the MBR for Windows to be bootable.
Post the output of
diskutil list
sudo gpt -vv -r show /dev/disk0
sudo fdisk /dev/disk0
Post the output of
diskutil list
Are you able to see Windows files in macOS Finder?
If you notice, you are missing the ML disk space.
diskutil apfs resizeContainer disk0s2 limits
SIP is not supported in ML, but it is on newer versions. Your Mac has two recovery paths, which are causing issues. I suggest you remove ML, and install it on an external disk. Once it is removed, we can try to address Windows issues.
The following command, if executed more than once, will lead to data loss. This must be run on the 650MB Recovery HD volume disk0s3 only once. It converts the Recovery HD to free space and disk0s3 will no longer exist.
Run
diskutil eraseVolume free free disk0s3
and post the output of
diskutil list
According to the Boot Camp support page, Mojave Boot Camp Assistant will only let you install Win10. But shouldn't a Winclone restore bypass the Mojave Boot Camp objection? Are the drivers that come with W7 enough to get it to boot into a MBP2018 and then do the upgrade to Win10 there? The Boot Camp drivers are for unique hardware features of the Mac, no? Such as brightness control, and now touchbar. So if those drivers were not present I could still use the keyboard, mouse and basic gpu functionality to get a Win10 install started. I just don't understand why the Wincloned partition didn't boot on the MBP2018. I'll restore it again and see what happens.
ckahn wrote:
According to the Boot Camp support page, Mojave Boot Camp Assistant will only let you install Win10. But shouldn't a Winclone restore bypass the Mojave Boot Camp objection?
Are you aware of this restriction - http://twocanoes.com/winclone-image-compatibility-with-512-and-4k-block/ ?
Are the drivers that come with W7 enough to get it to boot into a MBP2018 and then do the upgrade to Win10 there?
No.
The Boot Camp drivers are for unique hardware features of the Mac, no? Such as brightness control, and now touchbar.
Yes.
So if those drivers were not present I could still use the keyboard, mouse and basic gpu functionality to get a Win10 install started.
On which Mac - 2013 or 2018? W10 installation on either Mac will work, if you use BCA which downloads the appropriate drivers.
I just don't understand why the Wincloned partition didn't boot on the MBP2018. I'll restore it again and see what happens.
See the WinClone link for details. You should ask the TwoCanoes if they can specifically address the link that I posted.
It should take 5 minutes or less, if this was working properly.
Do you have a Time Machine backup? If yes, then my recommendation is - (on the 2013 MBA)
Are you trying this on the 2013 MBA or 2018 MBP?
2013 MBA should support a USB2 Flash drive formatted as MBR/FAT for W7. For W10, you can use a PC and Windows Media Creation Tool to create a bootable USB, but you will need to add BC drivers for it to work.
2018 MBP has secure boot, so you will need to look at the settings. See About Secure Boot - Apple Support for reference.
ckahn wrote:
Tim Perfitt, founder of Two Canoes Software, wrote: "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."
SysPrep generalizes Windows by removing any hardware-specific information from Windows. It uses the installed drivers' INF files to do so. Running a SysPrep on 2018 makes no sense. He is contradicting his own KB article.
Booting isn't an issue now. Boot Camp driver installation is the issue now.
Yes, and it will be because Registry entries are no longer valid on the 2018 Mac.
Not having any other ideas, I thought I'd give SysPrep a try at this late stage, hoping it would reset any driver issues, if driver issues are what is preventing Boot Camp driver installation from completing its task.
Microsoft's article clearly states that the generalized images are pushed to new devices, which do not have the same hardware as the source installation. Take a look at "Prevent Sysprep from removing installed devices" part. I use SysPrep to remove all hardware specific information on the source (Dell) to migrate to destination (HP/Asus/Lenovo) devices.
I've been following this document of instructions:
https://twocanoes.com/knowledge-base/migrating-windows-10-to-a-16-macbook-pro-2019-with-winclone-8/
Even though I have a MBP2018 13", not a MBP2019 16". The Touch Bar makes the instructions seem relevant to my situation and there is no page for MBP2018. The trouble with a lot of the Two Canoes documentation is that the details refer to interfaces that are no longer in the current OS or the current Winclone, such as the "how to partition" instructions, which has changed a lot in MacOS.
You may want to ask Tim for clarifications.
The last instruction is to run the setup.exe Boot Camp executable. The page doesn't go beyond that.
Can you post the PID/VID of the NCM entries? I will assume that you are using BC drivers package that came from BC Assistant -> Action -> Download on the 2018 MBP.
Progress indeed! Running Apple Software Update in Win10 repaired the last exclaimed device from Device Manager and made the Touch Bar brightness buttons functional. Booted back to MacOS and Parallels is able to access Boot Camp Win10 as well. I think it's fixed!
What year/model is your Mac (do not post the serial number)?
Boot Camp partition not mounting
