Q: how to install windows in early 2014 mac air (bootcamp 5.1) showing error like "'Windows cannot be installed to this disk. This co ... how to install windows in early 2014 mac air (bootcamp 5.1) showing error like "'Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure the disk's controller is enabled in the computer's BIOS " more
-
All replies
-
Helpful answers
-
Jun 18, 2015 4:31 AM in response to tanvir11077by Loner T,1. Are you using Bootcamp Assistant?
2. What is the version of Windows you are trying to install?
3. The following two links should help with a "standard" Windows installation on a Mac.
-
Jun 19, 2015 9:05 PM in response to Loner Tby tanvir11077,thx for replying Loner T,
your answer:
1. Yes
2. Win 7 pro 64 bit (cause boot camp ask for only 64 bit win 7)
3. I followed those process.already.
Boot Camp ***. Version: 5.1.2 (484)
OS X Version: 10.9.5
Whenever i go for install, at first using boot camp partition completed, then windows load and show 4 partition 1. EFI 200MB 2. which is for mac, 3. recovery drive, 4 BOOTCAMP drive.
I format the drive but it says "Windows cannot be installed to this disk. The selected disk is of the GPT partition style."
Plz Plz suggest as your earliest.
-
Jun 20, 2015 6:19 AM in response to tanvir11077by Loner T,Please download GPT Fdisk from http://sourceforge.net/projects/gptfdisk/ and I can give you the steps to fix this issue.
-
Jun 20, 2015 8:48 PM in response to Loner Tby tanvir11077,Thx for replying Loner T,
I download it. So could you please share the steps to fix the issue.
-
Jun 20, 2015 9:19 PM in response to tanvir11077by Loner T,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 the sample 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.
- Sudo gdisk /dev/rdisk0
- P (Print list of parts)
- R (Recover)
- O (print current Hybrid MBR)
- H (chooses Hybrid)
- Partitions numbers to be hybridized: 2 3 4
- Y (Good for GRUB question)
- N (part 2 boot flag)
- N (part 3 boot flag)
- Y (part 4 boot flag make NTFS bootable partition)
- O (print current Hybrid MBR)
- W (Write the new MBR)
- Y (Yes! write the new MBR)
- Reboot
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 AB): Press Enter/Return
Set the bootable flag? (Y/N): N
Creating entry for GPT partition #4 (MBR partition #4)
Enter an MBR hex code (default 07): Press Enter/Return
Set the bootable flag? (Y/N): Y
Reboot and test installing Windows.
-
Dec 24, 2015 5:57 AM in response to Loner Tby dudarino,Hi there!
same problem - solution worked till point 12
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/rdisk0.
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Unable to open device '/dev/rdisk0' for writing! Errno is 1! Aborting write!
-------------
...but I'm on a Macbook Pro Mid 2012 13'' - maybe that's the problem?
many greetings from Austria
-
-
Dec 24, 2015 6:39 AM in response to dudarinoby Loner T,Can you post a new discussion and include the output of the following Terminal commands?
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.
-
