Windows 8.1 install fails on new 2013 Retina MacBook

I doubt there are many people out there who can help with this yet. I was able to pick up my 2013 Haswell Retina MacBook Pro from my local Apple store this morning (yay!), and so far everything has been stellar. However, I'm unable to install Windows 8.1 via Bootcamp. I have not tried Windows 8 or 7.


I've tried installing both via USB thumb drive, and via DVD on external SuperDrive, with the same results. I know that 2013 MacBook Airs have to install via UEFI so I've tried that as well. What I've tried:


Booting into UEFI:

- After creating the partition in Bootcamp, I boot holding OPTION

- At the boot selection screen I select "EFI BOOT"

- I go through all the motions, including formatting the BOOTCAMP partition

- After all the files have been copied, I get a message that "Windows cannot update the boot partition and that my progress won't be saved" (not the exact message).


Booting via BIOS:

- After creating the partition in Bootcamp, I boot holding OPTION

- At the boot selection screen I pick "WINDOWS"

- When I get to the partition selection/formatting screen it won't let me proceed, when I expand the error message it tells me that partition can't be used because it has a GPT partition table.


So, I'm stuck =( Any ideas?

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Oct 23, 2013 8:56 PM

Reply
602 replies

Nov 16, 2013 6:02 PM in response to david0evans

EFI install was successful on my 15" MBP! Yes, with itsy bitsy hard-to-read text during the installation. I didn't do anything special, just followed the normal Boot Camp guide.


I will add one thing that may be pertinent - the Windows 8.1 Pro ISO I used was just downloaded today with the MS installer tool, so there's a small chance the ISO was updated since the retail DVD launch, but that's entirely a hypothesis on my part.

Nov 16, 2013 8:56 PM in response to david0evans

Still not working, but random tidbit of knowledge:


I was confused because bootcamp randomly started saying that the iso I was using was not 64bit / wasn't a valid windows ISO. I hadn't made any changes to the iso file.


I finally figured out that dragging the iso file into the file picker box doesn't work. You have to click choose file, and browse the the ISO, even though the UI seems to respond positively to you dragging the ISO file. Once I chose the file manually, it let me copy the iso to my usb drive as normal.

Nov 17, 2013 12:14 AM in response to david0evans

Ok, I've successfully got 8.1 installed, via the Windows 7 -> Windows 8.1 route. The "hanging" on 65% during the 7 install that I previously mentioned was, as others said, just it taking a long time. I waited it out and it continued. I'm not sure if that means I'm booting with BIOS now?


Nevertheless though, it's installed. So that's something at least. Getting drivers now, will post again if I encounter problems with this route.

Nov 17, 2013 6:17 AM in response to Shodan_Cat

EFI Installation succeded without any problems after changing the windows 8.1 version!

It works with the windows 8.1 gb-en version. It does not work with the normal english version.


steps:

(- undo all changes done by bootcamp)

- use bootcamp to create a windows usb stick (use united kingdom english iso, select only the two upper options in bootcamp tool)

- resize your osx partition using osx Disk Utility

- restart and press option key

- select efi boot

- use windows installer to create new partitions in the unallocated space (e.g. a windows and a data partition)

- install windows

- during installation the system will reboot 2 or 3 times, press the option key while restarting and select the windows hard disk symbol (not the usb stick!)

- The "getting things ready" dialog takes its time... up to 10 minutes on the top model of the rMBP 15" late 2013, so be patient!

Nov 17, 2013 11:54 AM in response to wohingenau

Hmm. I have the GB Win 8.1 ISO (full install) and it didn't work for me.


Given that some people have the problem and some don't either@

people aren't doing it exactly the same way each time

or

some people have faulty machines.


What I do know is that if you use DiskUtility to format a partition as FAT, it creates a hybrid-MBR disk, which isn't compatible with EFI booting.


But so far, when I try and do an EFI install (following the instructions above of selecting the first 2 options in BootCamp Assistant, then creating the partition manually in DiskUtility), I always get to the end of the Win 8.1 install with the error that Win8.1 can't update the boot configuration. If you look at the setup log files, you can see it's a BCD error - the Win 8.1 installer can't create BCD entries.

And when I mount the EFI partition from the installer and try myself, I also an't modify entries.


So I think it's some weird interaction between the Win 8.1 installer and the EFI partition.

One poster in anothe forum thought it might be a SecureBoot issue - I hope not, I don't want to think that Apple would go down the route of limiting what you'd be able to install on their hardware!

Nov 17, 2013 3:26 PM in response to Dourn

So, just for kicks, I followed the guide here:

http://blog.thedeltaflyer.com/2013/01/dual-booting-windows-8-and-mountain-lion-n atively-using-efi/


on booting from EFI on a rMBP.

What's different, is that the guide has you remove everything on your HDD and rebuild the EFI partition using windows Diskpart tool. I wondered whether the fact that the EFI partition was created by OSX was the root cause of the problems.


But alas, no. Win 8.1 still failed with the exact same error about being unable to set boot configuration.

I managed to fix that (by manually creating the BCD file again) but then again, windows fails at the end of the install with the same old error about being unable to finish configuring.


What've discovered is that the last error (right at the end of setup) is when sysprep is running, and it's attempting to update the BCD.


So it looks like there is something with regards to the Apple EFI (or the EFI partition) that the windows installer doesn't like.


I can get Windows up and running via msoobe, but it's in Sysprep Audit mode and a number of things don't work.


So now I'm going to ry a vanilla BootCamp install - but since BootCamp only supports 1 windows partition, I'll need to use HyperV for everything else (or see if rEFInd will work).


Sigh.

Nov 17, 2013 6:08 PM in response to Dourn

OK, so I decided to try the vanilla BootCamp approach: reinstalled OSX on a blank HDD (i.e. erased the entire SSD).

I then used BootCamp Assistant and selected all 3 options.

After reboot, in the Windows Installer I selected the new windows partition, deleted it, and created a smaller one.


And then.. I get the same error again:

Windows could not update the computer's boot configuration.

Installation cannot proceed.


Currently on hold with AppleCare support (Australia).

She has basically told me that this is a Microsoft problem and I'd need to contact them for support - i.e. because BootCamp has done it's job and got me into the installer, there's nothing they can do.

She has suggested I contact Microsoft for support.

Nov 17, 2013 7:21 PM in response to Dourn

OK, so I can get it to work, if I follow instructions found earlier in this forum, and delete the BootCamp Assistant created BOOTCAMP partition and recreate it using DiskUtility (formatted as exFAT).

I can see why this works: it cerates a hybrid-MBR disk, and so Windows installs via BIOS mode.


So it looks like by default BootCamp Assistant creates a GPT partition for Windows, which causes Windows Installer to run in EFI mode.


So if you don't force Windows Installer to use BIOS mode, the install fails.


But if you can install Windows in EFI mode on a MBA 13', surely it should work on a rMBP 15.


But the problem is either that:

a) BootCamp Assistant creates a GPT partition by default when it should create a hybrid-MBR one

OR

b) There is something up with the Mac EFI that prevents Windows from writing BCD info to it.


Ah well.

BIOS loading it is.

First impressions: slow. And I hate the fact that the installer/load screens aren't at full resolution!


Still, l'll take working slow loading windows over no windows!

Nov 17, 2013 7:25 PM in response to Dourn

I don't think it's an EFI problem, because I was able to install it. A GPT partition is required for EFI installs. The hybrid MBR/GPT partition is required for the BIOS emulation method. Boot Camp creates a GPT partition so Windows will install in EFI by default.


Still, at least you got it working for now. As I mentioned earlier, I did the BIOS method first and it worked pretty well actually. The only downsides I could see were increased boot and wake-from-sleep times.


Have you considered trying to download the latest ISO with the MS installer tool? It's the only thing I can think of that I've done differently from most that allowed me to run the EFI install.

Nov 17, 2013 8:53 PM in response to Shodan_Cat

Hi Shodan_Cat - yup, I downloaded the ISO from MS using their download tool - it's a UK ISO, downloaded from my MSDN account.


Whatever the problem is, it's all centered around the fact that the Windows Installer can't write the BCD files. It can definitely write to the EFI partition (the ESR) as it writes the EFT boot loader to the /EFI/Boot folder, and it creates the /EFI/Microsoft/Boto folder and creates an empty BCD file, but the error during setup relates to the fact that it can't copy across any boot resources.


If I manually create all the BCD resources, and manually create a BCD database, then windows boot, but fails right at the end of setup (in the Sysprep Respecialize stage), with a BCD error - again it can't update the BCD files.


So who knows!


Interestingly, I'm wondering if what you've done is recreateable (I'm not asking you to try!).

There was someone else (on this thread?) who managed to get Win8.1 installed via EFI, but then found when they retried it, they got the same error as a lot of us have had.


I just wish I knew if the difference in results was because of:

1) Faulty hardware

2) Faulty firmware

3) Difference in method

4) Difference in Windows ISO files

5) A completely random event


Thans for your reply anyway!


I'm going to look back at the steps you followed I think...


I'm going to be in the states this week, so may go into an Apple store and ask them about it.

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 8.1 install fails on new 2013 Retina MacBook

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