crh24
Level 3 (924 points)

Q: Won't boot after Boot Camp drivers are installed.

Background:

 

I have a late-2012 i7 27" iMac with a 3 TB Fusion drive and 32GB DRAM running OS X 10.10.4.  I have been successfully running windows in Boot Camp on this iMac for a couple of years.  As it happens, my model had the bad 3TB Fusion drive and about the time Apple announced the replacement program the hard drive began to fail (good timing :-)

 

After getting all of my Mac software running successfully on the replacement drive I decided to install Windows 7 64 bit again.  I used the Boot Camp Assistant to create the Windows partition and to install the drivers (BootCamp5.1.5621) on a USB drive.

 

The Windows 7 Home Premium 64 bit install proceeded without problems all the way to the point where the Boot Camp drivers app rebooted Windows.  Upon the reboot the startup failed.  I first tried "Starting Normally" but was taken back to the same point so I said to repair.  The repair process found no problems and offered to do a system restore.  I told it to do so. The boot proceeded without problems, but of course I had no Apple drivers so no internet, etc.  I then downloaded the drivers directly from Apple and installed.  Same problem.

 

My question...It has been so long since I first installed Windows on my iMac that I have no idea what version of the drivers I used.  Would moving to version 4 of the drivers possibly work or is there something really amiss in that version?

late-2012 27; i7 iMac, 32GB, 3TB Fu, OS X Mavericks (10.9), iPad Air,miniR; ATV3; mid 2012 MBA;

Posted on Jul 16, 2015 7:06 PM

by crh24,Solvedanswer
crh24 crh24
Level 3 (924 points)
A:

I have it working now. I installed 193 windows updates and three Apple updates but the keyboard still didn't work.  I also tried your idea of unplugging the keyboard.  That didn't work, either. 

 

Further searching brought up a thread from late 2012 that held the solution--for me, at least.

 

Note #8 from this thread:

 

http://forums.macrumors.com/threads/installed-windows-7-bootcamp-drivers-now-key board-doesnt-work.1509773/

 

worked.  The text from that note is shown below:

===

The issue is the USB 3.0 extreme driver that gets installed.

 

To fix this boot into windows safe mode by holding or repeatedly hitting F8 as windows boots. Once in safe mode go to the control panel/ add remove programs and uninstall the USB 3.0 driver listing. After that you can reboot back into regular windows and your keyboard/mouse will work and you will have 1 unknown device listed in device manager.

 

Apparently this is related to a usb3 monitor utility that gets installed with the normal intel setup package. To get the drivers installed without that utility i downloaded the usb driver package from http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21129

Extract the files but do not run the setup. Instead go to device manager and update the driver and point it to the folder you extracted.

 

After you install the first unknown device a second one will pop up. Do the exact same thing with that device. Both items will install successfully and everything should be fine.

 

I haven't tested a usb3 device yet but everything should be in a position for it to work.

Posted on Jul 17, 2015 9:43 PM

Close
crh24

Q: Won't boot after Boot Camp drivers are installed.

  • All replies
  • Helpful answers

Page 1 of 3 last Next

  • by Loner T,

    Loner T Loner T Jul 16, 2015 7:18 PM in response to crh24
    Level 7 (24,439 points)
    Safari
    Jul 16, 2015 7:18 PM in response to crh24

    5.1.5621 is the correct BC drivers package. Is your issue that Windows installation is not complete yet?

  • by crh24,

    crh24 crh24 Jul 16, 2015 11:53 PM in response to Loner T
    Level 3 (924 points)
    Jul 16, 2015 11:53 PM in response to Loner T

    BootCamp4.1.4586 and BootCamp5.0.5033 give me the same symptoms.

     

    Loner T wrote:

     

    5.1.5621 is the correct BC drivers package. Is your issue that Windows installation is not complete yet?

    Windows appears to be complete and works ok as windows w/o the Apple hardware, i.e. no network.

     

    As soon as I install the BC driver package, and I've tested three different versions, upon reboot after the install of the BC package completes the Windows boot process halts with the "Unable to start Windows" screen and the two standard options are try again booting normally, which takes me to the same point again, or to Repair which if chosen results in the Repair process finding nothing wrong and offering to restore the system from the last good state.  Choosing that option does give a bootable windows but w/o the BC drivers.

     

    I appear to be in an endless loop and I'm at a loss as to where to go next.

  • by Loner T,

    Loner T Loner T Jul 17, 2015 5:22 AM in response to crh24
    Level 7 (24,439 points)
    Safari
    Jul 17, 2015 5:22 AM in response to crh24

    Since this is a new installation, my suggestion is to remove Windows and re-install Windows. There is only one version which is correct as specified in System requirements to install Windows on your Mac using Boot Camp - Apple Support . Using different versions of BC drivers requires careful cleanup of the driver files before different versions are tried. If you want to try using different drivers, I suggest using System Restore points instead of installation on top of installations, which cause unpredictable behavior.

  • by crh24,

    crh24 crh24 Jul 17, 2015 12:39 PM in response to Loner T
    Level 3 (924 points)
    Jul 17, 2015 12:39 PM in response to Loner T

    As stated it is a brand new clean installation of Windows.  I'm aware of the driver issues that can arise in Windows. Each test of a different driver came after a system restore.

     

    Since I am unable to find references to my problem through internet searches I'm pretty sure it is something about my system that is causing the issue.  I'm just hoping for someone to have some other ideas than the usual re-install because I've done that...twice.

     

    I'm wondering if SMC or PRAM issues could cause this problem.  I doubt the former as the SMC was reset when the drive was replaced but it is easy to try so I'll be doing that today.

  • by Loner T,

    Loner T Loner T Jul 17, 2015 12:51 PM in response to crh24
    Level 7 (24,439 points)
    Safari
    Jul 17, 2015 12:51 PM in response to crh24

    Was Windows installed using EFI boot?

  • by crh24,

    crh24 crh24 Jul 17, 2015 1:17 PM in response to Loner T
    Level 3 (924 points)
    Jul 17, 2015 1:17 PM in response to Loner T

    Yes.

     

    Rseething SMC & PRAM didn't change things so I'm going to do a complete wipe partition using BCA and try again. This time I will remove all peripherals from my iMac before installing Windows.

     

    I'll revisit when that is completed.

  • by Loner T,

    Loner T Loner T Jul 17, 2015 1:27 PM in response to crh24
    Level 7 (24,439 points)
    Safari
    Jul 17, 2015 1:27 PM in response to crh24

    Your iMac is a PreUEFI Mac. It will not support EFI boot correctly. Please let BCA install Windows fully without the use of Alt/Option keys.

  • by crh24,

    crh24 crh24 Jul 17, 2015 1:40 PM in response to Loner T
    Level 3 (924 points)
    Jul 17, 2015 1:40 PM in response to Loner T

    Please elaborate for my education...  Also, how do I find out if my iMac is PreUEFI.  I know my EFI boot rom version is IM131.010A.B08.

  • by Loner T,

    Loner T Loner T Jul 17, 2015 1:55 PM in response to crh24
    Level 7 (24,439 points)
    Safari
    Jul 17, 2015 1:55 PM in response to crh24

    Macs prior to late 2013 run EFI version 1.1. Newer Macs run UEFI (EFI 2.0+) . There are many implications. One is that such Macs can run Windows on a GPT partition. Older Macs use a hybrid MBR to emulate BIOS via CSM-BIOS, which is slower for hardware access.

  • by crh24,

    crh24 crh24 Jul 17, 2015 2:00 PM in response to Loner T
    Level 3 (924 points)
    Jul 17, 2015 2:00 PM in response to Loner T

    Ok.  I had about gleaned that from a post of yours from May that I came across while looking for UEFI. 

     

    I'll re-install with the boot camp drivers on a SanDisk Cruzer and the Windows install disk in my smartdrive.

  • by crh24,

    crh24 crh24 Jul 17, 2015 2:25 PM in response to crh24
    Level 3 (924 points)
    Jul 17, 2015 2:25 PM in response to crh24

    One more thing.  I'm really starting from scratch, even recreating the ISO image on my 16GB SanDisk Cruzer.

  • by Loner T,

    Loner T Loner T Jul 17, 2015 2:32 PM in response to crh24
    Level 7 (24,439 points)
    Safari
    Jul 17, 2015 2:32 PM in response to crh24

    Typically, run BCA , insert USB2, point to the ISO on your Mac when prompted, partition and let BCA do its work, till the Windows partition screen appears, format the BC partition only is the sequence of steps.

     

    Are you doing anything different?

  • by crh24,

    crh24 crh24 Jul 17, 2015 2:41 PM in response to Loner T
    Level 3 (924 points)
    Jul 17, 2015 2:41 PM in response to Loner T

    That is what I did originally.  Currently the ISO is being created.

     

    One question. Is the USB drive ever removed?

     

    From what I've now read about EFI it appears that my original process caused the problem.

     

    Upon the reboot after formatting the Windows partition, a system disk wasn't found so I re-connected the windows DVD and rebooted and installed from that.  I think that is likely what caused the boot problem.

     

    I'm using a 16GB SanDisk Cruzer formatted MBR as stated in the BCA help docs.  If it fails this time I'll take a picture of the display.

     

    Up to the failure to find a system disk upon reboot everything proceeded as per the BCA docs.

  • by Loner T,

    Loner T Loner T Jul 17, 2015 3:13 PM in response to crh24
    Level 7 (24,439 points)
    Safari
    Jul 17, 2015 3:13 PM in response to crh24

    Your specific Late 2012 iMac model supports USB installer creation. Even if you use the DVD method, the USB contains the WinPE (Preboot Environment) and should not be disconnected till the Windows installer asks you to disconnect peripherals.

Page 1 of 3 last Next