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

Totenkreuz Author

Level 1

0 points

Problem installing W10 on BCA 6 and El Capitan 10.11

Hi, I have problems installing W10 on my Mac.

Here's an overview of what happened:

OS X Yosemite, with W7 Bootcamp (everything is fine).

Updated to OSX El Capitan, Bootcamp no longer found (holding alt on boot doesn't show Bootcamp).

Used BCA to Remove Windows 7 or later version. (space allocated in HDD for Bootcamp is back to single partition).

Used BCA to Create a Windows 7 or later version install disk using Win10_English_x64.iso downloaded from Microsoft along with latest support drivers from Apple. Also checked Install Windows 7 and or later version.

After waiting a couple hours and the USB Bootcamp is finally ready, I set 70gb for the Bootcamp partition, eventually the Mac automatically reboots but never booted up to the Windows 10 bootcamp installation (The reboot is just like any normal reboot that reboots back to Mac).

Opened BCA and it now shows Remove Windows 7 and or later version.

Checked Disk Utility, and the partition for Bootcamp is there but most of it is unused.

What could be the problem here? I also noticed that my BCA is still showing Windows 7 while I've read somewhere that on El Capitan, Bootcamp no longer requires USB Drive, or atleast shows Windows 8. http://blog.twocanoes.com/post/130203487014/apple-boot-camp-no-longer-requires-u sb-flash-drive?utm_source=loopinsight.com&utm_medium=referral&utm_campaign=Feed% 3A+loopinsight%2FKqJb+(The+Loop)&utm_content=FeedBurner

Checked the Win10_English_x64.iso for MD5 and SHA1 and everything is fine.

OS X El Capitan 10.11

MBP Retina 15" Mid 2014

Thanks in advance!

Posted on Oct 6, 2015 1:44 AM

39 replies

Totenkreuz Author

Level 1

0 points

Oct 7, 2015 9:17 AM in response to Loner T

diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *251.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage Untitled 180.8 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

/dev/disk1 (internal, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Untitled +180.4 GB disk1

Logical Volume on disk0s2

5C862E07-63DE-42BC-93C9-8B34A61366FB

Unencrypted

/dev/disk2 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *8.1 GB disk2

1: DOS_FAT_32 WININSTALL 8.1 GB disk2s1

sudo fdisk /dev/disk2

Password:

Disk: /dev/disk2 geometry: 987/255/63 [15872000 sectors]

Signature: 0xAA55

Starting Ending

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

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

*1: 0B 1023 254 63 - 1023 254 63 [ 2 - 15871998] Win95 FAT-32

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

Loner T

Level 9

59,471 points

Oct 7, 2015 9:32 AM in response to Totenkreuz

Try the following command and hold the Alt/Option key when powering up your Mac.

sudo /usr/sbin/bless --device /dev/disk2s1 --setBoot --legacy --nextonly

Totenkreuz Author

Level 1

0 points

Oct 7, 2015 9:34 AM in response to Loner T

sudo /usr/sbin/bless --device /dev/disk2s1 --setBoot --legacy --nextonly

Password:

Could not set boot device property: 0xe00002bc

Loner T

Level 9

59,471 points

Oct 7, 2015 10:16 AM in response to Totenkreuz

Bless disk2 and test.

Totenkreuz Author

Level 1

0 points

Oct 7, 2015 6:25 PM in response to Loner T

sudo /usr/sbin/bless --device /dev/disk2 --setBoot --legacy --nextonly

Password:

Could not set boot device property: 0xe00002bc

Totenkreuz Author

Level 1

0 points

Oct 7, 2015 6:48 PM in response to Loner T

After doing some research, I did some csrutil disable from the recovery terminal and the bless did properly execute. After which doing a restart now boots to a windows terminal, but shows up no bootable disk found, press any key to continue.

Loner T

Level 9

59,471 points

Oct 7, 2015 7:38 PM in response to Totenkreuz

Do not use --legacy. Instead bless the bootmgr.efi. See Man bless Mount mode and the --file qualifier.

Oct 7, 2015 8:00 PM in response to Totenkreuz

Hey Totenkreuz,

I have been having the same problem but I am a MacBook Pro. Your screens help. I am determined to get it to work. The written information that Apple has is not fully helpful.

Cheels,

Applegeek17

Totenkreuz Author

Level 1

0 points

Oct 7, 2015 9:06 PM in response to Applegeek17

Likewise, I'm on a Macbook Pro also. 15" Retina Mid 2014. Please let me know how it goes for you.

Totenkreuz Author

Level 1

0 points

Oct 7, 2015 9:24 PM in response to Loner T

How do I find the path to the bootmgr.efi? Can you provide me an example for mount and file qualifier?

Checking diskutil info /dev/disk2, says it's not mounted and there's no file system. I think this could be the problem?

diskutil info /dev/disk2

Device Identifier: disk2

Device Node: /dev/disk2

Whole: Yes

Part of Whole: disk2

Device / Media Name: Generic Flash Disk Media

Volume Name: Not applicable (no file system)

Mounted: Not applicable (no file system)

File System: None

Content (IOContent): FDisk_partition_scheme

OS Can Be Installed: No

Media Type: Generic

Protocol: USB

SMART Status: Not Supported

Total Size: 8.1 GB (8126464000 Bytes) (exactly 15872000 512-Byte-Units)

Volume Free Space: Not applicable (no file system)

Device Block Size: 512 Bytes

Read-Only Media: No

Read-Only Volume: Not applicable (no file system)

Device Location: External

Removable Media: Yes

Media Removal: Software-Activated

Virtual: No

OS 9 Drivers: No

Low Level Format: Not supported

Loner T

Level 9

59,471 points

Oct 8, 2015 5:56 AM in response to Applegeek17

Applegeek17 wrote:

I have been having the same problem but I am a MacBook Pro. Your screens help. I am determined to get it to work. The written information that Apple has is not fully helpful.

Can you try and rebuild your USB installer using the first two options in BCA and test? This would allow two separate solutions to be tested.

Loner T

Level 9

59,471 points

Oct 8, 2015 5:57 AM in response to Totenkreuz

The USB file listing you posted shows bootmgr.efi in the root-level directory of the USB.

Totenkreuz Author

Level 1

0 points

Oct 8, 2015 8:48 AM in response to Loner T

Yes indeed, it is at the root of the USB drive.

I meant, how does that translate to bless --file and --mount? Sorry, was kind of new to bless.

Loner T

Level 9

59,471 points

Oct 8, 2015 8:54 AM in response to Totenkreuz

Totenkreuz wrote:

I meant, how does that translate to bless --file and --mount? Sorry, was kind of new to bless.

See the highlighted parts. Use --verbose as well and post the output. Assuming the path to the file is

/Volumes/WININSTALL/bootmgr.efi

you can use

sudo bless --folder /Volumes/WININSTALL --file /Volumes/WININSTALL/bootmgr.efi --setBoot --verbose

and test.

MOUNTMODE

Mount Mode has the following options:

--mount directory Use the volume mounted at directory to change the active boot volume, in conjunction with --setBoot . The volume must already be prop-

erly blessed.

--file file Instead of allowing the firmware to discover the booter based on the blessed directory or file, pass an explicit path to the firmware

to boot from. This can be used to run EFI applications or EFI booters for alternate OSes, but should not be normally used. This is

only supported on EFI-based systems.

--setBoot Same as for Folder Mode.

--nextonly Same as for Folder Mode.

--shortform Same as for Folder Mode.

--legacy Same as for Folder Mode.

--legacydrivehint device

Same as for Folder Mode.

--options Same as for Folder Mode.

--quiet Do not print any output

--verbose Print verbose output

Totenkreuz Author

Level 1

0 points

Oct 8, 2015 9:17 AM in response to Loner T

sudo bless --folder /Volumes/WININSTALL --file /Volumes/WININSTALL/bootmgr.efi --setBoot --verbose

Password:

EFI found at IODeviceTree:/efi

Mount point for /Volumes/WININSTALL is /Volumes/WININSTALL

Common mount point of '/Volumes/WININSTALL' and '' is /Volumes/WININSTALL

No BootX creation requested

No boot.efi creation requested

found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xE803FF37

found ioreg "FirmwareFeatures"; featureFlagsValue=0xE803F537

isPreBootEnvironmentUEFIWindowsBootCapable=1

given BSD is not a DVD disc medium

isDVDWithElToritoWithUEFIBootableOS=0

Checking if disk is complex (if it is associated with booter partitions)

Other partition scheme detected

No auxiliary booter partition required

Preferred system partition found: disk0s1

Returning booter information dictionary:

<CFBasicHash 0x7fd4d1709cb0 [0x7fff7c390890]>{type = mutable dict, count = 3,

entries =>

0 : <CFString 0x10f8e6990 [0x7fff7c390890]>{contents = "System Partitions"} = (

disk0s1

)

1 : <CFString 0x10f8e7170 [0x7fff7c390890]>{contents = "Data Partitions"} = (

disk2s1

)

2 : <CFString 0x10f8e7190 [0x7fff7c390890]>{contents = "Auxiliary Partitions"} = (

)

}

Path to mountpoint given: /Volumes/WININSTALL

IOMedia disk2s1 does not have a partition UUID

DADiskRef disk2s1 has Volume UUID 07D39EC5-BAE3-30ED-9A34-AECB16744F6A

IOMedia disk2s1 has path IODeviceTree:/PCI0@0/XHC1@14/@13:1

Setting EFI NVRAM:

efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key ><string>IOMedia</string><key>IOPathMatch</key><string>IODeviceTree:/PCI0@0/XHC1 @14/@13:1</string></dict><key>BLVolumeUUID</key><string>07D39EC5-BAE3-30ED-9A34- AECB16744F6A</string><key>BLLastBSDName</key><string>disk2s1</string></dict></ar ray>'

Setting EFI NVRAM:

IONVRAM-DELETE-PROPERTY='efi-boot-file'

Setting EFI NVRAM:

IONVRAM-DELETE-PROPERTY='efi-boot-mkext'

Setting EFI NVRAM:

IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache'

NVRAM variable "boot-args" not set.

Problem installing W10 on BCA 6 and El Capitan 10.11