Windows Boot Camp Partition replaced by System Reserved after installation

Hey there,


I have just created a 60GB Boot Camp partition and installed Windows 7 successfully via a method with virtualbox, someone suggested on stackexchange.


I was able to run and reboot Windows with virtualbox until I restarted my Macbook to try actually booting into Windows.

On the boot selection screen, only Macintosh HD was available.

Then, back on Mac OS, virtualbox didn't let me start up the Boot Camp disk anymore so I checked the diskutil list:


/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 439.0 GB disk0s2

3: Microsoft Basic Data System Reserved 60.9 GB disk0s3


/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +439.0 GB disk1

Physical Store disk0s2

1: APFS Volume Mac OS X SSD 185.1 GB disk1s1

2: APFS Volume Preboot 22.2 MB disk1s2

3: APFS Volume Recovery 512.1 MB disk1s3

4: APFS Volume VM 4.3 GB disk1s4

Before the reboot the Boot Camp Partition was disk0s3, 60GB.

However, during the installation process, Windows created a System Reserved partition with ~100MB space.

Now, System Reserved is disk0s3 and 60GB so I guess it kind of replaced the Boot Camp partition which completely disappeared.

I am not sure, but I guess this problem has nothing to do with the virtualbox procedure but rather with the windows installation creating the System Reserved partition.

Does anyone have an idea what could have gone wrong or how to fix this?

Would appreciate your help alot!

Ps: Im on High Sierra 10.13.6, MacBook Pro (15-inch, Early 2011)

MacBook Pro, macOS High Sierra (10.13.6), MacBook Pro (15-inch, Early 2011)

Posted on Dec 5, 2018 6:06 AM

Reply

Similar questions

20 replies

Dec 6, 2018 10:39 PM in response to Santhiphap

"We can rebuild the MBR from GPT using GDisk."


I am having a hard time to get a grasp of what that actually means. I glanced over the MBR wiki and I realize I have no idea what MBR and GPT really are.


What exactly is wrong with the MBR ?


Sorry if my curiosity makes this more complicated then it is. Maybe at this point its easier if you could just give me a rundown of how to use gdisk to accomplish this. And maybe I automatically get a better understanding of everything afterwards.

Dec 6, 2018 11:48 PM in response to Santhiphap

Alright one last try of figuring this out myself.

I found these instructions on stackexchange.


I think thats it, right?


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. 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.

  1. sudo gdisk /dev/rdisk0
  2. P (Print list of parts)
  3. R (Recover)
  4. O (print current Hybrid MBR)
  5. H (chooses Hybrid)
  6. Partitions numbers to be hybridized: 2 3 4
  7. Y (Good for GRUB question)
  8. N (part 2 boot flag), N (part 3 boot flag)
  9. Y (part 4 boot flag make NTFS bootable partition)
  10. O (print current Hybrid MBR)
  11. W (Write the new MBR)
  12. Y (Yes! write the new MBR)
  13. Reboot
To make Windows bootable again try the following:

Boot from your Windows DVD/USB-Stick

Open command prompt from Windows recovery option menu. Type “diskpart” at the command prompt.
At the DiskPart prompt, type in “list disk”. You will see the list of disk currently attached to your computer.
Now type in “select disk n”, where n is the disk number. In this example, disk 0 is selected.
Now that correct disk is selected, type in “list partition” to get a list of all the partitions on that disk.
To select the partition you want to set as active, type in “select partition n”, where n is the partition number (probably 3).
Now that you have selected the disk and partition, mark it as
active by just typing the word “active” and pressing Enter. Now the
partition is set active.
Exit from the command prompt and run startup repair.


Except, I assume in my case I have to set bootflag on partition 3.

So step 6. looks like this: Partitions numbers to be hybridized: 2 3

And at step 8. I press N only once


And I dont understand what step 7. "Y (Good for GRUB question)" is meaning/doing, I guess its setting bootflag for the EFI so I can boot into MacOS?

Dec 8, 2018 6:51 AM in response to Santhiphap

Ok so I have made some progress.


First of all, I figured out that in order to get rid of all virtualbox errors I had to execute the chown commands again and also unmount the partition, each time after I reboot my Macbook.

sudo chown $USER /dev/disk0s3
sudo chown $USER /dev/disk0s1
sudo chown $USER /dev/disk0
diskutil unmount /dev/disk0s3

There was no need to create a new .vmdk at all.


Then I tried to reinstall windows and rebuild the hybrid MBR again with gdisk.

It seemed like nothing worked until I checked the Startup Disk in my MacOS Settings.


NOW I see it!


I figured out that I had to mount it in order to show up in Startup Disks.

Anyway, I still cant chose it from the startup screen. When I hold alt/option I only see my Mac OS SSD.


My new problem is:

When I use Startup Disk to Restart into "Untitled Windows" after 10 sec of grey screen I get stuck at a black screen with blinking cursor. (I waited more than 10 min)


I tried windows repair command prompt:

Bootrec.exe /FixMBR
Bootrec.exe /FixBoot
Bootrec.exe /RebuildBcd

But nothing changed...

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Windows Boot Camp Partition replaced by System Reserved after installation

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.