Rick / Sharkdog

Q: Trying to install Windows 10 on Early 2013 Retina MacBook Pro

Hello!

 

As the title implies, I'm having some trouble installing Windows 10 on a 15" MacBook Pro Retina (Early 2013).

I'm at wits end right now, so I turn to you guys, hopefully someone can point me in the right direction!

 

I started with creating the USB installer from Boot Camp Assistant, this seems to go off without a hitch (having done this multiple times, sometimes it fails, but then if I try again it will do one that doesn't fail).

 

I've created partitions through the Boot Camp Assistant, and also without (I read about making an exfat partition, so I tried that), but both to no avail.

When Boot Camp Assistant finished making the partition it tries to reboot into it and gives me a "No bootable drive, press any key to restart" type error. Keys don't work, so I force shut down the laptop and restart it holding Option to select the USB installer and go from there.

 

The USB installer boots without a hitch and gets me into the Windows 10 installer. When it comes to selecting a partition, I select the Boot Camp (or self made) partition and Format it. At this point it still won't let me install on the partition because: "Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks."

 

Having read a little bit, I found the gdisk Terminal utility and ran through that. Initially it wouldn't write, so I booted into recovery to unlock it, and then it seemed to go off without a hitch.

 

When I then boot back into the Windows 10 USB installer, it seems to install the OS without issue onto the selected partition. Yay! Right? Not really..

 

As soon as Windows 10 tries to boot up (at this point, from the partition, since it installed) it immediately starts crashing. Basically getting an error like such: "System thread exception not handled igdkmd64.sys"

 

Again, reading around a bit taught me that it seems to be some sort of (graphics?) driver error. Some of the solutions I saw seemed to assume that you can already boot into Windows 10 and have a few minutes before it starts crashing. I don't seem to have that luxury.

 

That's basically the spot I'm stuck at. I've run through this loop multiple times (with the different partitions, multiple times with each method) and seem to be stuck here.

 

Hoping someone can provide some insight!

Posted on May 29, 2016 5:32 PM

Close

Q: Trying to install Windows 10 on Early 2013 Retina MacBook Pro

  • All replies
  • Helpful answers

Previous Page 2 of 4 last Next
  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 2, 2016 6:58 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jun 2, 2016 6:58 AM in response to Loner T

    Here it is, thanks again for helping with this!

    Screen Shot 2016-06-02 at 15.56.24.png

  • by Loner T,

    Loner T Loner T Jun 2, 2016 8:15 AM in response to Rick / Sharkdog
    Level 7 (23,898 points)
    Safari
    Jun 2, 2016 8:15 AM in response to Rick / Sharkdog

    Can you post the firmware and SMC versions from System Report? There have been a few EFI updates that we should check.

     

    Please see About EFI and SMC firmware updates for Intel-based Mac computers - Apple Support as a reference.

  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 2, 2016 8:26 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jun 2, 2016 8:26 AM in response to Loner T

    Just checked, here's my overview:

    Screen Shot 2016-06-02 at 17.23.41.png

     

    I've cross referenced with the page you linked, and these seem to be the correct (or latest) versions for my model.

  • by Loner T,

    Loner T Loner T Jun 2, 2016 9:28 AM in response to Rick / Sharkdog
    Level 7 (23,898 points)
    Safari
    Jun 2, 2016 9:28 AM in response to Rick / Sharkdog

    1. Do you have GPT Fdisk - https://sourceforge.net/projects/gptfdisk/ - installed?

    2. Can you post the output of

         sudo fdisk /dev/disk0

    3. We can remove the Hybrid MBR and test if EFI Boot will install correctly without any driver or Audio/GPU issues.

  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 2, 2016 12:50 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jun 2, 2016 12:50 PM in response to Loner T

    Output for 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 -     409639] <Unknown ID>

    2: AF 1023 254  63 - 1023 254  63 [    409640 -  875816464] HFS+       

    3: AB 1023 254  63 - 1023 254  63 [ 876226104 -    1269544] Darwin Boot

    4: 0B 1023 254  63 - 1023 254  63 [ 877496320 -   99608576] Win95 FAT-32


    I had BCA create a brand new partition right before I ran the command, without attempting to install anything on it. I have the GPT Fdisk utility installed as well.

  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 4, 2016 6:19 AM in response to Rick / Sharkdog
    Level 1 (4 points)
    Windows Software
    Jun 4, 2016 6:19 AM in response to Rick / Sharkdog

    I went ahead and ran the GPT Fdisk utility as per the instructions on this page: http://superuser.com/questions/508026/windows-detects-gpt-disk-as-mbr-in-efi-boo t

     

    I made sure to reboot to recovery first to use the 'csrutil disable' command first, so that GPT Fdisk could actually make changes.

     

    This got me as far as being able to run the Windows 10 installer.

    After the installer finishes and tries to boot into Windows, I immediately go into the "System thread exception not handled igdkmd64.sys" loop.

     

    This is BEFORE I am able to do anything in Windows 10, even the initial setup. It just immediately starts crashing. After a few loops it'll give me a few options (like booting into Safe Mode). I've tried booting into Safe Mode, but I then get an error that I can't boot into Safe Mode because initial setup hasn't been completed yet.

     

    I guess at this point I technically have Windows 10 installed, except it's still not actually running.

     

    Edit: I'd like to add that I at no point during the installation am connected to any network, and the only thing plugged in are my magsafe adapter and the USB flash drive with the windows installer.

    During installation the Windows 10 installer does go through an "Installing updates" step, but I never connected it to any network through either ethernet or wifi while running the installer.

  • by Loner T,

    Loner T Loner T Jun 4, 2016 8:41 AM in response to Rick / Sharkdog
    Level 7 (23,898 points)
    Safari
    Jun 4, 2016 8:41 AM in response to Rick / Sharkdog

    Remove W10 using BCA, re-create the partition, remove the MBR, disconnect from networks physically, re-run the install from the USB, install the BC drivers, create a Windows System Restore point, and then connect to a network. If it starts crashing, roll back to the restore point.

     

    This malady afflicts many Mac users. Please see Windows 10 crashing, but not sure why. as an example.

  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 4, 2016 8:49 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jun 4, 2016 8:49 AM in response to Loner T

    And therein lies my problem. I can only get up to the point where the installer runs from the USB successfully.

     

    As soon as the computer restarts to finally boot into Windows 10 after installing, the driver error starts.

    This is before any initial setup is finished, and long before I get to a point where I have access to the Desktop and Start Menu, from where I could install the drivers, make a Windows System Restore Point etc.

  • by Loner T,

    Loner T Loner T Jun 4, 2016 1:27 PM in response to Rick / Sharkdog
    Level 7 (23,898 points)
    Safari
    Jun 4, 2016 1:27 PM in response to Rick / Sharkdog

    Do you have any physical cables/hubs connecting the Mac to network?

  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 4, 2016 3:39 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jun 4, 2016 3:39 PM in response to Loner T

    Nothing connected but the Windows installer USB (also tried booting Windows without it attached, since the installer was technically done).

  • by Loner T,

    Loner T Loner T Jun 5, 2016 10:47 AM in response to Rick / Sharkdog
    Level 7 (23,898 points)
    Safari
    Jun 5, 2016 10:47 AM in response to Rick / Sharkdog

    1. What is the Product version in Bootcamp.xml on your USB?

    2. Your Mac has two GPUs as noted in MacBook Pro (Retina, 15-inch, Early 2013) - Technical Specifications and EFI Boot is exposing both to the OS. As a test, instead of using W10 Home 64-bit, can you use W10 Pro 64-bit and try to install it. The Installation media is available at https://www.microsoft.com/en-us/software-download/windows10ISO .

  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 5, 2016 3:36 PM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jun 5, 2016 3:36 PM in response to Loner T

    Again, thanks for still trying to help out. It's very much appreciated!

     

    1. The product version in Bootcamp.xml is 6.0.6136

     

    2. I downloaded a new .iso from the website you provided for prosperity (I got my original file from there as well I think). I seem to have gotten a slightly newer file (Win10_1511_2_English_x64.iso over Win10_1511_1_English_x64.iso) but it hasn't made a difference.

    I removed the existing partition with BCA and ran BCA from scratch again, making a new installer boot USB with the newly downloaded .iso file, creating a partition, then running the GPT Fdisk utility and finally installing Windows 10.

    While I only have a key for Windows 10 Home, by not entering a product key I was able to select an install for Windows 10 Pro.

     

    Unfortunately, after it finished installing and rebooting, it immediately jumped into the error loop again involving the igdkmd64.sys driver.

  • by Loner T,

    Loner T Loner T Jun 5, 2016 3:55 PM in response to Rick / Sharkdog
    Level 7 (23,898 points)
    Safari
    Jun 5, 2016 3:55 PM in response to Rick / Sharkdog

    Can you expand the $WinPEDriver$ folder on the USB to two levels and post a listing? One more test cycle using the same ISO.

     

    Using Install Windows 7 and earlier on your Mac using Boot Camp - Apple Support, can you replace the $WinPEDriver$ as shown in Step 11 with the W7 versions and test? Verify that the Intel GPU driver version files are different by looking at the Bootcamp.xml for for the .6136 and the corresponding 5.x version.

  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 6, 2016 1:22 AM in response to Loner T
    Level 1 (4 points)
    Windows Software
    Jun 6, 2016 1:22 AM in response to Loner T

    Here's a screenshot of the $WinPEDriver$ folder before I tried replacing them with the Windows 7 Drivers:

    Screen Shot 2016-06-06 at 10.04.09.png

     

    I've downloaded the Windows 7 drivers from the page you mentioned, and tossed them into the USB installer, replacing the folders.

    The $WinPEDriver$ folder that comes with the Windows 7 Drivers only contains two folders: AppleBluetoothBroadcom64 and IntelHDGraphics64.

     

    I checked the Bootcamp.xml file, and the Windows 7 Drivers do contain an older version of the driver that's giving me a bit of a headache.

     

    The Bootcamp 5 XML references it twice, both for Intel HD Graphics:

     

    <Name>Intel(R) HD Graphics

      <InfName>igdlh64.inf</InfName>

      <Class>Display</Class>

      <ClassGUID>{4D36E968-E325-11CE-BFC1-08002BE10318}</ClassGUID>

      <CatalogFile>igdlh.cat</CatalogFile>

      <Provider>Intel Corporation</Provider>

      <DriverVer>10/31/2013,10.18.10.3345</DriverVer>

      <ServiceBinary>igdkmd64.sys</ServiceBinary>

      <HardwareID></HardwareID>

      <isX64>yes</isX64>

     

    and

     

    <Name>Intel(R) HD Graphics

      <InfName>igdlh64.inf</InfName>

      <Class>Display</Class>

      <ClassGUID>{4D36E968-E325-11CE-BFC1-08002BE10318}</ClassGUID>

      <CatalogFile>igdlh.cat</CatalogFile>

      <Provider>Intel Corporation</Provider>

      <DriverVer>10/31/2013,9.17.10.3347</DriverVer>

      <ServiceBinary>igdkmd64.sys</ServiceBinary>

      <HardwareID></HardwareID>

      <isX64>yes</isX64>

     

    Whereas the newer Bootcamp 6 version contains three references:

     

    <Name>Intel(R) HD Graphics

      <InfName>igdlh64.inf</InfName>

      <Class>Display</Class>

      <ClassGUID>{4D36E968-E325-11CE-BFC1-08002BE10318}</ClassGUID>

      <CatalogFile>igdlh.cat</CatalogFile>

      <Provider>Intel Corporation</Provider>

      <DriverVer>06/19/2015,10.18.14.4243</DriverVer>

      <ServiceBinary>igdkmd64.sys</ServiceBinary>

      <HardwareID></HardwareID>

      <isX64>yes</isX64>

     

    <Name>Intel(R) HD Graphics

      <InfName>igdlh64.inf</InfName>

      <Class>Display</Class>

      <ClassGUID>{4D36E968-E325-11CE-BFC1-08002BE10318}</ClassGUID>

      <CatalogFile>igdlh.cat</CatalogFile>

      <Provider>Intel Corporation</Provider>

      <DriverVer>06/16/2015,10.18.10.4242</DriverVer>

      <ServiceBinary>igdkmd64.sys</ServiceBinary>

      <HardwareID></HardwareID>

      <isX64>yes</isX64>

      </Name>

     

    <Name>Intel(R) HD Graphics

      <InfName>igdlh64.inf</InfName>

      <Class>Display</Class>

      <ClassGUID>{4D36E968-E325-11CE-BFC1-08002BE10318}</ClassGUID>

      <CatalogFile>igdlh.cat</CatalogFile>

      <Provider>Intel Corporation</Provider>

      <DriverVer>10/31/2013,10.18.10.3345</DriverVer>

      <ServiceBinary>igdkmd64.sys</ServiceBinary>

      <HardwareID></HardwareID>

      <isX64>yes</isX64>

     

    Anyway, I replaced the files on the USB Windows installer with the ones from the Bootcamp 5 version, unfortunately, when trying to boot into the installer after doing this, I'm met with this error:

    winerror.jpg

    I re-downloaded the newer Boot Camp files through BCA (Action > Download Windows Support Software) and copied them over the Boot Camp 5 files again to see if it would work normally again, which it does.

    I guess the BC5 Windows 7 drivers are not compatible with the Windows 10 installer?

  • by Rick / Sharkdog,

    Rick / Sharkdog Rick / Sharkdog Jun 9, 2016 1:56 PM in response to Rick / Sharkdog
    Level 1 (4 points)
    Windows Software
    Jun 9, 2016 1:56 PM in response to Rick / Sharkdog

    Did a few more tests. A friend of mine had the idea to maybe install Windows 7 or 8 and then upgrade to 10 from there. He had the ISO's for Windows 7 and Windows 8.1 and passed them on to me.

     

    I tried to make a bootable USB installer from the Windows 7 iso, but that didn't pan out. It all ran through normally, but the USB installer ended up not showing up as bootable.

     

    My experiences with the Windows 8 iso are basically exactly the same as with the Windows 10 one. I can get it to install, if I change the partition to GPT with The GPT Fdisk utility, but then as soon as it installs and reboots I start getting the driver error.

     

    So unfortunately, still not any step closer.

Previous Page 2 of 4 last Next