Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Windows 8 EFI Install Update
- Thread starter redcolumbia
- Start date
- Sort by reaction score
Yeah I did but I'm afraid you won't be too happy.
Did some tests with two ATI cards. A Mac flashed one out of an Mac Pro and regular PC model. I connected each to my eGPU. Using die regular one it worked on the fly while the Mac flashed didn't get recognized by Windows. guess this matches your observation.
So the GPU-ROM should be the problem which seems pretty unfixable unless you want to mess with your OSX. You could try to replace your ATI MXM card with a newer Nvidia MXM card.
Yeah I am. What do you mean by:
My 650M is running fine. You might want to update your drivers. I'm currently using 314.22. You might want to disable your Intel HD in Device Manager aswell (Windows tries to start it if you don't do so but can't because of the missing file). Actually I dont even have to remove igdkmd64.sys.
After the Windows' spinning wheel it take usually a few seconds until the LCD gets recognized (maybe 5 seconds). Using your Intel HD with Basic Display Drivers you'll see your Desktop a bit faster.
Regarding the Intel HD in general we can only hope for a driver release that works. There are regular updates ... a new one just released which I haven't tested yet -> http://downloadmirror.intel.com/22627/a ... 152815.zip
My 650M is running fine. You might want to update your drivers. I'm currently using 314.22. You might want to disable your Intel HD in Device Manager aswell (Windows tries to start it if you don't do so but can't because of the missing file). Actually I dont even have to remove igdkmd64.sys.
After the Windows' spinning wheel it take usually a few seconds until the LCD gets recognized (maybe 5 seconds). Using your Intel HD with Basic Display Drivers you'll see your Desktop a bit faster.
Regarding the Intel HD in general we can only hope for a driver release that works. There are regular updates ... a new one just released which I haven't tested yet -> http://downloadmirror.intel.com/22627/a ... 152815.zip
Last edited:
What do you mean by this? That audio out via USB or HDMI works, not needing the Intel driver at all?
Ah, I see. Your GT 650M works as a pass thru device for the audio, not actually using or needing the integrated audio card on the laptop itself. I suppose your Nvidia driver works as it should.
I did ask on another forum about eGPU, which I know you visits as well. Means that if using eGPU attached via Thunderbolt port, one should be able to get sound out from the eGPU itself, via HDMI. So the non functional Intel driver for the audio on this MacBook Air becomes a non issue for such purpose. Well, at least I hope so.
Now that Bootcamp 5 drivers are out I am going to have another go at Windows 8 on my base Mac mini 2011. (bootcamp 5.0 won't run on my 2010 Mac mini server grrr...)
At the time I tried Windows 8 with Bootcamp 4 I had no sound either. This was resolved by installing windows and then before installing bootcamp go to the bootcamp installation CD / USB and find the Intel HD graphics location and install those drivers first. Afterwards reboot and then install Bootcamp as per normal. ( The Intel HD drivers do also install the audio drivers.... not something I expected but discovered it the hard way. )
On a positive note: I am on cellular so cannot download large amounts of data however I downloaded Bootcamp 5. My 2011 base Mac mini is running Lion / Windows 7. Windows 7 is running in AHCI mode because otherwise performance of the Samsung 830 SSD suffers badly. (The Intel X25M-G2 and the Toshiba HG3 have no noticeable performace differences between AHCI and "normal" mode).
With Bootcamp 4 and AHCI bootcamp control panel does not want to run - you better make sure all settings have been applied before enabling AHCI.
After removing Bootcamp 4 and installing 5 this bootcamp control panel is now working. Don't know about the Mountain Lion and system settings - under Lion the startup disk cannot be set but once I upgrade Lion to Mountain Lion (download too big for cellular data download allocation) it might turn out that setting the startup disk works there as well which means I do no longer need to use a wired keyboard for changing OS. Perhaps someone who is running Mountain Lion / Windows 7 / AHCI / Bootcamp 5 can check this.
Hopefully Apple has also fixed some other issues with AHCI - I certainly hope so.
Well this thread is about Windows 8 EFI install. I never had problems with AHCI nor had those very few ppl who actually where able to install Win7 in EFI mode. Installing Intel drivers before BootCamp won't fix the EFI problems at all. Are you sure you posted in the right thread?
Last edited:
I'm going to dump the rom of my ATI Radeon Mobility HD 4850 ; Don't you think you can "simply" tweak it.
I think we rely on a Christmas gift from Apple or Intel, in order for this to be resolved. That's unfortunately the Windows experience on a Mac, in a nutshell.
My experience so far:
I just installed Windows Server 2012 on a new MacBook Pro i7 13 inch model in EFI mode. Everything works fine except:
Light sensor
I guess this regulates the automatic dimming of the display and/or the keyboard backlight. As the display brightness buttons work fine (although with the Windows overlay on screen instead of the Mac one) I don't care that much. Strange is that the brightness tab in the Bootcamp controlpanel is missing too...
Bluetooth
This is a Microsoft issue as the MS engineers decided to ditch BT support on their server OS, much to the annoyance of many developers (like myself) that run a server OS on their development box. With some hacking I got BT to work with an outdated Toshiba BT stack... (in fact I am now typing on an Apple BT keyboard)
Audio
This is the greatest annoyance... I do not need sound during work but I also use the Mac for watching video while on holiday or listening to iTunes. So this might be the showstopper for me. On the other hand, the Mac boots up blazing fast now compared to under emulated Bootcamp BIOS... So I might opt for an external sound card until Intel/Apple get the audio working as it should.
The Intel Graphics HD4000 installed with no problem and work just fine. As well as the HD3000 on my EFI MacMini 2011 i5.
I just installed Windows Server 2012 on a new MacBook Pro i7 13 inch model in EFI mode. Everything works fine except:
Light sensor
I guess this regulates the automatic dimming of the display and/or the keyboard backlight. As the display brightness buttons work fine (although with the Windows overlay on screen instead of the Mac one) I don't care that much. Strange is that the brightness tab in the Bootcamp controlpanel is missing too...
Bluetooth
This is a Microsoft issue as the MS engineers decided to ditch BT support on their server OS, much to the annoyance of many developers (like myself) that run a server OS on their development box. With some hacking I got BT to work with an outdated Toshiba BT stack... (in fact I am now typing on an Apple BT keyboard)
Audio
This is the greatest annoyance... I do not need sound during work but I also use the Mac for watching video while on holiday or listening to iTunes. So this might be the showstopper for me. On the other hand, the Mac boots up blazing fast now compared to under emulated Bootcamp BIOS... So I might opt for an external sound card until Intel/Apple get the audio working as it should.
The Intel Graphics HD4000 installed with no problem and work just fine. As well as the HD3000 on my EFI MacMini 2011 i5.
Last edited:
I have been working with both my Macs with EFI install for quite a while now and I notice a difference between my 2012 MBP 13 i7 and my 2011 MacMini i5. Both machines run Windows Server 2012 EFI. The Mini is my study server and runs Hyper-V with 4 SQL Server virtual machines. It runs 24/7. It sits under my desk without monitor, keyboard and mouse attached. I connect to it using RDP.
Every once in a while the Mini needs to reboot due to Windows updates. And that is where the problem lies. Ever since the Mini has been installed in EFI mode the machine does restart but it cannot be taken over through RDP. The only way to get it going again is attach a physical keyboard and monitor to it and then reboot. After that it runs just fine until the next reboot. The MBP does not have this problem, most probably as it has a fixed display. And I am 100% sure the Mini did not have this issue while it was still running in BIOS mode.
It is quite annoying as attaching a monitor and keyboard is a real pain as the Mini is quite tucked away. And not having toe possibility to reboot remotely sometimes is not very handy too.
Of course I could go back to BIOS install (so far the only benifit of EFI over BIOS I am aware of are very fast boot times, which is not of the most importance on a 24/7 server...) but I would just like to know what causes this.
Any ideas? Google did not help much so far...
EDIT
I have tried the unattended logon and uninstalling the Intel HD graphics but that did not solve the issue
Every once in a while the Mini needs to reboot due to Windows updates. And that is where the problem lies. Ever since the Mini has been installed in EFI mode the machine does restart but it cannot be taken over through RDP. The only way to get it going again is attach a physical keyboard and monitor to it and then reboot. After that it runs just fine until the next reboot. The MBP does not have this problem, most probably as it has a fixed display. And I am 100% sure the Mini did not have this issue while it was still running in BIOS mode.
It is quite annoying as attaching a monitor and keyboard is a real pain as the Mini is quite tucked away. And not having toe possibility to reboot remotely sometimes is not very handy too.
Of course I could go back to BIOS install (so far the only benifit of EFI over BIOS I am aware of are very fast boot times, which is not of the most importance on a 24/7 server...) but I would just like to know what causes this.
Any ideas? Google did not help much so far...
EDIT
I have tried the unattended logon and uninstalling the Intel HD graphics but that did not solve the issue
Last edited:
For anyone who is interested, Windows 8 EFI installed fine on my 2013 MBA.
Bootcamp program installed fine
Brightness and sound controls work
Whole drive is GUID
Intel HD iGPU graphics work fine
Sound works fine
Boots quickly
Hopefully this is an indication that future apple products will be made to support Windows EFI natively.
Bootcamp program installed fine
Brightness and sound controls work
Whole drive is GUID
Intel HD iGPU graphics work fine
Sound works fine
Boots quickly
Hopefully this is an indication that future apple products will be made to support Windows EFI natively.
I also successfully installed Windows 8 using UEFI in my 2013 MBA.
Spectacular battery life I'm getting.... 11 hours of battery life.
Another success story here with EFI boot for Windows 8 on MBA Mid 2013 using the stock Bootcamp method. I didn't realize it was in EFI mode until I checked the Device Manager where I saw "Standard SATA AHCI Controller" was installed for the PCIE SSD.
The blinking cursor delay is now gone and boot time to desktop is around 5-8 seconds depends on how many apps are loaded in systray. Shutdown is almost instant.
If anyone have thunderbolt storage attached, they will find the drives scan black screen (before Windows booting logo) is now gone as well.
I guess the key is to have Bootcamp download the latest drivers for new devices like Broadcom BCM43xx for wifi onto the USB flashdrive.
The blinking cursor delay is now gone and boot time to desktop is around 5-8 seconds depends on how many apps are loaded in systray. Shutdown is almost instant.
If anyone have thunderbolt storage attached, they will find the drives scan black screen (before Windows booting logo) is now gone as well.
I guess the key is to have Bootcamp download the latest drivers for new devices like Broadcom BCM43xx for wifi onto the USB flashdrive.
Last edited:
I'm not sure it's only drivers. Perhaps Apple also did changes to their EFI firmware to be more compatible. Would be interesting to find out. What BootCamp version did you download?
Can you post a screenshot of device manager with extensive details shown for the sound device? IT would be good if you used unknown hardware identifier or a similar program to determine whether or not a Cirrus Logic chip is used for sound. Thanks.