Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

BootCamp Problems on mid-2014 15" Macbook Pro

Hey there guys! I was hoping someone could help me with this weird problem. You see, I've been trying to install Windows 7 x64 Professional via Bootcamp. Here's what I tried:


I tried a SanDisk cruz 3.0 usb flash drive at first and was able to get this to install. However when I booted into windows I was unable to access my flash drive. Now I wish I wouldn't have deleted the partition and moved onto using Parallels, as I could have simply dropped the BootCamp files into the NTFS partition using the paragon drivers I have now. Ah well.


So now I'm wanting to try again with BootCamp so I can boot straight into only Windows 7 when I need to. Here's what I've been trying and where it keeps going wrong:


I have been using the SanDisk Extreme 32GB 3.0 USB flash drive to install Windows and every time I get to the point of formatting the BOOTCAMP partition to NTFS, it does and then tells me that it is unable to create a new system partition or locate one when I click next having selected the newly formatted partition. I've also noticed that whenever I reboot and try the installation again, it drops me into a different Windows installer that attempts to find the drivers upon beginning setup. It can't find the 3.0 flash drive and won't load anything from it. Now I've read that this has something to do with Windows 7 not supporting USB 3.0 during installation. This is not necessarily a problem since if I could only get Windows installed on the BOOTCAMP partition, I would be able to bop the files right onto the partition from Yosemite and then boot back into Windows and go from there. So now I'm stuck in an infinite loop of deleting the partition and then repeating the entire process.


I will say this though, the last time this actually worked, I had to repeat the process maybe 3 times and each time I actually did not use the BootCamp assistant software to delete the newly made partition. I used Disk Utility instead. Now....I'm not sure if there's any correlation there, but it may be something worth trying. I feel that it may have the same result considering that BootCamp Assistant probably uses Disk Utility under the hood whenever it's partitioning and deleting partitions.


With that being said, I was wondering if anybody has solved a similar problem or has dealt with this specifically. I know that there's tons of threads/posts with similar problems but all the solutions I have found have yet to actually work in any way for me. As I said before, I'm stuck in an infinite loop and nothing seems to make this work. Anybody have any ideas? I would appreciate any help as I am so excited to be able to convert this MBP into my All-In-One productivity laptop.


EDIT: I wanted to also add that originally I had tried to install with a windows 7 ISO that I had downloaded via torrent (legally, of course) due to a purchase download link that would have taken around 2 hours. This was the one which worked successfully via the first flash drive. However when I tried it with the second flash drive, it did not work. So I did my time and downloaded the purchased ISO copy and tried that one as well, only to have the same problem. I even went so far as to go on an older windows laptop and format the flash drive, make it bootable with the purchased ISO copy, place the Bootcamp support software on it and try again that way. Again, same problem.

MacBook Pro (Retina, 15-inch, Mid 2014), OS X Yosemite (10.10.5), null

Posted on Sep 4, 2015 12:12 PM

Reply
7 replies

Sep 4, 2015 12:21 PM in response to kingdarkeyes

You have a litany of issues.


1. Do not use a USB3. Windows Installer does not have USB3 drivers. They can be added, but it requires building a custom Windows installer.

2. If you use EFI boot, the destination partition should be Free Space, not a FAT or NTFS partition. It will be split into MS Reserved (FAT) and MS Data (NTFS) parts.

3. If the Installer cannot find USB3, it is a result of 1.

4. Do not use DU to manipulate BCA-created partitions and vice-a-versa. BCA also moves Recovery HD, which DU does not.

Sep 4, 2015 12:32 PM in response to Loner T

Ah, I see. I suspected that altering the partitions with DU might have been a bad move. I will definitely keep that in mind. In regards to your first point, how might one go about putting such drivers onto the installation? Because at this point I am definitely down to try it.


To your second point, I must ask what exactly is the difference in the boot system used? I may be somewhat lost on this point, but the partition produced by BCA is in fact FAT formatted, requiring the windows installer to format it to NTFS. From what I understand, I have no control over how this procedure works as it is all dependent upon how BCA creates and formats the partition. I apologize if I have missed your point entirely.


Lastly, to your third point I remind you that this was accomplished successfully with a USB3 flash drive once before. Just as well, the installation process seems to be mainly halted by the partitioning process.


Thank you for your comments.

Sep 4, 2015 12:51 PM in response to kingdarkeyes

Can you post the output of the following OSX Terminal commands? It may be a bit easier to explain the various issues.


diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0


The "sudo" commands will prompt for your password, and it will not be echoed back. You may also see a warning about improper use of "sudo" and potential data loss due to "abuse" of the command.

Sep 4, 2015 1:06 PM in response to Loner T

Here you are good sir.


diskutil list:

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 499.4 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD *499.1 GB disk1

Logical Volume on disk0s2

37E0C60F-68B2-4753-BE6F-8FF53E110499

Unlocked Encrypted

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *31.4 GB disk2

1: Windows_NTFS 31.4 GB disk2s1


-------------------------------------------------------------------------------- -----------------------

diskutil cs list:

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group 3B4DD24E-8179-4AC5-9AFC-4F53272640BD

=========================================================

Name: Macintosh HD

Status: Online

Size: 499418034176 B (499.4 GB)

Free Space: 946176 B (946.2 KB)

|

+-< Physical Volume D016474F-4E14-4999-9A10-0F94234C1EAF

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 499418034176 B (499.4 GB)

|

+-> Logical Volume Family C6311DD2-3B28-4AFF-A481-C9B1D473AFE8

----------------------------------------------------------

Encryption Status: Unlocked

Encryption Type: AES-XTS

Conversion Status: Complete

Conversion Direction: -none-

Has Encrypted Extents: Yes

Fully Secure: Yes

Passphrase Required: Yes

|

+-> Logical Volume 37E0C60F-68B2-4753-BE6F-8FF53E110499

---------------------------------------------------

Disk: disk1

Status: Online

Size (Total): 499076300800 B (499.1 GB)

Conversion Progress: -none-

Revertible: Yes (unlock and decryption required)

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS


-------------------------------------------------------------------------------- -----------------------

sudo gpt -vv -r show /dev/disk0:

gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060

gpt show: /dev/disk0: PMBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 977105059

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 975425848 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

975835488 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

977105024 3

977105027 32 Sec GPT table

977105059 1 Sec GPT header

-------------------------------------------------------------------------------- -----------------------

sudo fdisk /dev/disk0:

Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 977105059] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

Sep 4, 2015 1:15 PM in response to kingdarkeyes

You currently do not have a Bootcamp/Windows partition.


There are two methods of installing Windows. Legacy BIOS or more modern EFI. Your Mac supports both. BIOS mode has restrictions and slower. W7 has it's own EFI challenges and is not a good choice for EFI. W8+ and W10 are better, with W10 better.


BC Assistant defaults to BIOS because it is supported across more Macs as well as older Macs.


If you do not use BCA, but use Alt/Option key to interrupt BCA during Windows installation, you can choose either, but the underlying partitioning also plays a role. BIOS requires a MBR which maps your GPT disk to a MBR to make Windows think it is using a legacy PC. BIOS has a 4-partition restriction and a 2TB (32-bit) limit. Pure GPT is much more flexible and is supported on your Mac since your Mac is UEFI compliant (UEFI is an Intel standard for OS-to-HW interface via specific Firmware APIs).

BootCamp Problems on mid-2014 15" Macbook Pro

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