Boot Camp Trouble

brandonschuk wrote:

I just took a stab at it, but stopped before step 12. Here is my pastebin https://pastebin.com/PAPWq0rJ

Glad to see the GDisk warning about the technically being legal. 😂

I am not sure if I did steps 6-9 properly. I followed the steps, rather than the sample Q&A, as they differed.

The reason why I stopped before step 12 - I have two questions, please:

Inbetween steps 9 and 10 this popped up: "Unused partition space(s) found. Use one to protect more partitions?" - I said "N", but I'm not sure if that's correct.

'N' is the correct choice.

2. For step 12 it said "THIS WILL OVERWRITE EXISTING PARTITIONS!!" so I bailed. Will this delete my Mac install if I proceed?

Yes, because there is a PMBR, which is being switched to a Hybrid MBR.

brandonschuk wrote:

So I should say "Y" and let t overwrite the existing partitions?

Yes.

Won't that erase my OS that I am currently working on?

No.

I'm nervous to end up in a situation that I can't fix.

I assume you have a Time Machine backup.

I have the ultimo 2014 5k iMac with 250GB SSD and have the same problem installing win10 (april version) with USB2 Stick 32GB. No time machine snapshots left and time machine is disabled.

Greetings from germany and thank you for your help

bjoern81 wrote:

I have the ultimo 2014 5k iMac with 250GB SSD and have the same problem installing win10 (april version) with USB2 Stick 32GB. No time machine snapshots left and time machine is disabled.

Greetings from germany and thank you for your help

Since you do not have a 3Tb Fusion drive, your issue may be different. Please start a new discussion.

I have the same blue screen that says "Your PC ran into a problem and needs to restart. We'll restart for you." - Stop code: SYSTEM_SERVICE_EXCEPTION / What failed: win32kfull.sys

Maybe the 3TB is not the problem, since I have the same problem with my 250GB SSD.

Same issue. Someone earlier posted something similar to my output of diskutil using the Late 2014 5k iMac.

diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         121.1 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         1000.0 GB  disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.1 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD            271.4 GB   disk2s1
   2:                APFS Volume Preboot                 45.3 MB    disk2s2
   3:                APFS Volume Recovery                522.7 MB   disk2s3
   4:                APFS Volume VM                      2.1 GB     disk2s4

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *32.1 GB    disk3
   1:               Windows_NTFS WinInstall              32.1 GB    disk3s1

This is the first time I've noticed this because it's not a 3TB Fusion.

I've ran Bootcamp a few times on fresh Mojave installs, with different partition schemes. This issue first came up and I was on APFS so I assumed that + Fusion maybe was the issue. I de-coupled, partitioned it all again as jhfs+ and pretty sure I resetFusion as well. Used both ISOs from April and October. No dice.

Issue: After 'successfully' getting through BC partition, setup and restart, then a new and improved look alike to the classic 'blue screen of death'. Same error as most of these guys: win32ful failure.

The BIOS boot actually was really bizarre. It gets to the formatting of the 'BOOTCAMP' partition and gives the GPT format error that I've only experienced when partition is done outside BC.

This could have something to do with the strange APFS disk showing up? Under BIOS boot I noticed the size of the "BOOTCAMP" partition is 100GB greater than whatever I just set on BC. I've done 200GB partition on bootcamp and under the BIOS boot it finds a 300GB partition named ''BOOTCAMP''. Extremely extremely strange.

My iMac has never been 'touched' by Mojave. I can install W7/W8.1/W10 on a CoreStorage 1Tb Fusion drive without any issues, using either BIOS or EFI.

On the same iMac, W7/W8.1 are lost when you upgrade to Mojave, and lose the ability to successfully install W10.

This is my 2014 iMac, which will not see Mojave. Sierra is the last macOS on this iMac. I will test W7-W10 on this in the next couple of days. This iMac has a 1TB Fusion drive.