Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Win7 x64 booting natively via EFI (no BIOS emulation)

Quick questions:

1. What indexes are present in your WIM file?
2. Did you slipstream drivers on all indexes?

You have to force unsigned. Here is the process I used:


Windows 7 - x64 - Enterprise

# Setup Encironment for install
mkdir C:\Inject
cd "C:\Inject"
mkdir mount
mkdir mount\winpe
mkdir mount\setup
mkdir x64_drivers

# move install.wim and boot.wim to C:\Inject

# move all drivers to x64_drivers

# expand nvidia drivers
cd C:\Path\to\nvidia-drivers
expand *.* C:\Inject\x64_drivers

# mount images (boot and setup)
cd "C:\Inject"
dism /mount-wim /wimfile:boot.wim /index:1 /mountdir:mount\winpe
dism /mount-wim /wimfile:boot.wim /index:2 /mountdir:mount\setup

# retrieve drivers
dism /image:mount\winpe /get-drivers
dism /image:mount\setup /get-drivers

# inject drivers
dism /image:mount\winpe /add-driver /recurse /forceunsigned /driver:x64_drivers
dism /image:mount\setup /add-driver /recurse /forceunsigned /driver:x64_drivers

# verify drivers
dism /image:mount\winpe /get-drivers
dism /image:mount\setup /get-drivers

# Unmount and commit
dism /unmount-wim /mountdir:mount\winpe /commit
dism /unmount-wim /mountdir:mount\setup /commit

# Get Wiminfo
dism /get-wiminfo /wimfile:install.wim

# Make directoties
mkdir mount\enterprise

# Mount image editions (Actual windows)
dism /mount-wim /wimfile:install.wim /index:1 /mountdir:mount\enterprise

# Verify indexes
dism /get-mountedwiminfo

# Retrieve drivers
dism /image:mount\enterprise /get-drivers

# Inject drivers
dism /image:mount\enterprise /add-driver /recurse /forceunsigned /driver:x64_drivers

# Verify drivers
dism /image:mount\enterprise /get-drivers

# Unmount and commit
dism /unmount-wim /mountdir:mount\enterprise /commit
 
Last edited:
@duffman9000

I thinking about trying again... but I don't feel up to it right now. When you slipstreamed drivers was the EFI\Microsoft\Boot directory almost empty? That alone told me something was really wrong.

What system are you installing on? Mac Pro 2010

Are you also dual booting OS X? I'm using dedicated SSD for Windows only. My EFI has Grub folder u add before install & Microsoft /EFI/.../ folder from installation. I also forgot to remove USB on reboot and installation still completed.

Previous attempts before DaGr8Gatzby Guide i notice that install error ever time unless i follow these steps.

1st. Boot Windows Repair disk and format w/ Diskpart.
Code: 
C:diskpart
select disk 1
clean
convert gpt 
create partition efi size=200
create partition msr size=128
create partition primary align=1024
exit
[B]REBOOT[/B]
When i use any other tool to format it always error either before or during installation.

2nd boot ubuntu / install gpt fdisk / open gpart / format FAT32 & name efi & Format Primary NTFS / Open terminal / run : sudo gdisk /dev/sda / type in this order after each ":" x, o, n, o, w, yes / Open Disk Utiliy / mount EFI / add grub folder /

3rd reboot to osx / open terminal /{ sudo mkdir /Volumes/esp } / {sudo mount_msdos /dev/disk0s1 /Volumes/esp } / you should see grub folder / copy & paste "sudo bless --setBoot --folder" then drag & drop "grub" folder to terminal follow by " copy & paste "--file" then drag & drop "bootx64.efi" should look some thing like this.
Code: 
sudo bless --setBoot --folder /Volume/esp/grub --setfile /.../bootx64.efi

it should boot EFI SHELL. Unless you hold option to boot USB

then follow guide.
 
Last edited:
mac-hacks said:
duffman9000 said:
Hi mac-hacks,

I thinking about trying again... but I don't feel up to it right now. When you slipstreamed drivers was the EFI\Microsoft\Boot directory almost empty? That alone told me something was really wrong.

What system are you installing on? Mac Pro 2010

Are you also dual booting OS X? I'm using dedicated SSD for Windows only. My EFI has Grub folder u add before install & Microsoft /EFI/.../ folder from installation. I also forgot to remove USB on reboot and installation still completed.

Previous attempts before DaGr8Gatzby Guide i notice that install error ever time unless i follow these steps.

1st. Boot Windows Repair disk and format w/ Diskpart.

2nd boot ubuntu / install gpt fdisk / open gpart / format FAT32 & name efi & Format Primary NTFS / Open terminal / run : sudo gdisk /dev/sda / type in this order after each ":" x, o, n, o, w, yes / Open Disk Utiliy / mount EFI / add grub folder /

3rd reboot to osx / open terminal /{ sudo mkdir /Volumes/esp } / {sudo mount_msdos /dev/disk0s1 /Volumes/esp } / you should see grub folder / copy & paste "sudo bless --setBoot --folder" then drag & drop "EFI" folder to terminal follow by " copy & paste "--file" then drag & drop "bootx64.efi"

then follow guide.
Click to expand...

I have successfully done this on a MacPro 2010. It is indeed possible. If you'd like, I can up my drivers.
Click to expand...
 
DaGr8Gatzby said:
mac-hacks said:
I have successfully done this on a MacPro 2010. It is indeed possible. If you'd like, I can up my drivers.
Click to expand...

During this step:
dism /image:mount\winpe /get-drivers

I see these message:

Obtaining list of 3rd party drivers from the driver store...

Driver packages listing:

(No drivers found in the image matching the criteria)

The operation completed successfully.

Is that correct?
Unfortunately, I'm on a MBP 15" 2011. I need cast-iron belly to try this again.
Click to expand...
 
duffman9000 said:
DaGr8Gatzby said:
During this step:
dism /image:mount\winpe /get-drivers

I see these message:

Obtaining list of 3rd party drivers from the driver store...

Driver packages listing:

(No drivers found in the image matching the criteria)

The operation completed successfully.

Is that correct?
Unfortunately, I'm on a MBP 15" 2011. I need cast-iron belly to try this again.
Click to expand...

Yea that should be correct. There are no additional drivers when you first get the wim mounted. I alwyas like to make sure I start with a clean ISO. That is why I placed that command there. Go ahead and continue. Later on, the same command will produce different output.
Click to expand...
 
still not working for me. I get past the first part of the installation just fine, with no errors. But as soon as the machine tries to load bootmgfw, i get a blinking white screen. not even caps lock works.

I think this all proves one obvious point - what's needed here is a bios like interface at startup. even if it's an efi based machine, we can go into the shell and use the mm commands to change registers and whatnot. Hitting F10, F2, delete, whatever on a bios based machine 'sort of' does the same thing. I think what we need here that apple has failed to implement is a gui, even if in the form of a simple .efi application (considering how proficient *cough* i am at c programming, not that simple) so that power users can set certain options for their os.

For instance, i'm running on a 320M mainboard. Nvidia made this board specifically for mac. It's not only your video card. Something I noticed is that when I would boot up under the CSM bios and launch the efi shell terminal under Boot Duet - my storage controller was at 00 0A 85, but when i would launch the efi shell terminal under pure efi by loading it from refind (without CSM booting via boot duet) my storage controller was actually 00 0A 88, even with a different device ID. If there were an interface where power users could set options like these, or simple vga on/off switches, and then load the os of your choice, that would be great. Any volunteers?
 
rip1999eternal said:
still not working for me. I get past the first part of the installation just fine, with no errors. But as soon as the machine tries to load bootmgfw, i get a blinking white screen. not even caps lock works.

I think this all proves one obvious point - what's needed here is a bios like interface at startup. even if it's an efi based machine, we can go into the shell and use the mm commands to change registers and whatnot. Hitting F10, F2, delete, whatever on a bios based machine 'sort of' does the same thing. I think what we need here that apple has failed to implement is a gui, even if in the form of a simple .efi application (considering how proficient *cough* i am at c programming, not that simple) so that power users can set certain options for their os.

For instance, i'm running on a 320M mainboard. Nvidia made this board specifically for mac. It's not only your video card. Something I noticed is that when I would boot up under the CSM bios and launch the efi shell terminal under Boot Duet - my storage controller was at 00 0A 85, but when i would launch the efi shell terminal under pure efi by loading it from refind (without CSM booting via boot duet) my storage controller was actually 00 0A 88, even with a different device ID. If there were an interface where power users could set options like these, or simple vga on/off switches, and then load the os of your choice, that would be great. Any volunteers?
Click to expand...

I am really interested in all of these problems you guys are having. Would it be possible to film your boot up procedure the same way I did? I would like to see what is occurring.
 
rip1999eternal said:
it's buggy. i've tried to use it before for creating machine specific installs, but i ended up being better off learning how to use dism
Click to expand...

http://www.rt7lite.com/rt-se7en-lite.html

I always use this in past, never had issue with slip streaming BOOTCAMP Drivers and installing w/ .ISO. I use DSM w/ Guide and it error some where in 2nd part of installation.

Driver section will force install UN-assign drivers, if you check box. I've never experience Installer error out due to UN-assign drivers w/ RT-7 lite.

If you look in forum there another tool RT7-Booster, complement to RT7-Lite. RT7-Booster can emove more stuff that RT7-Lite could do.
 
I didn't have any success trying to install Win7 using DaGr8Gatzby's method. I went back to the previously posted method for me to install Win8.

The AMD GPU reports a resource conflict. I think that's the same place others have been stuck.
 
@rip1999eternal

Do not use rEFInd for now. Only install the EFI shell. The reason I say this is because rEFIt used to have this bug,or the mac firmware, where after running numerous EFI binaries, I was not able to get the same results from either the boot loader, or the shell. I recommend only using the EFI shell. Then using the EFI shell to chainload the required bootloader via startup.nsh, or manually.

Personally, using grub has given me the BEST results. I do have a partial bias though.

@jlpek17 and Mac-Hacks

Do not use any other tool other than dism to inject drivers. I wasted several days using RT-seven lite, or any other GUI injector because of this. I also used it to generate an autounattend.xml. Waste of time. Learn the tools created by Microsoft. It's just a lousy prerequisite. I do not know if it's the tools, or if it was just me that was messing up. However, my dism commands should provide plenty of reference. I am monitoring this thread constantly, so if you have questions, feel free to hit me up.

@duffman900

OH YEA! Sorry you didn't have any success with my method. However, it seems you want a dedicated install of Windows. If you'd like, I can make a separate tutorial for that. I will film it as well.

To everyone slipstreaming drivers, I have made the drivers that work on my machine available:

http://dl.dropbox.com/u/4308827/Inject.zip

Please let me know if these help you. I wish you guys could just ship me your machines :(
 
@DaGr8Gatzby
+

Probably be good idea to start new thread with your method and leave few save Post to copy & paste useful links from this thread and any other site. Which user could PM you, if your admin "save post" to add link. to beginning thread so it doesn't get out of control and all over place.
 
When I investigated for "windows to go" I saw that "dism" and "imagex" was updated in Windows 8 and it was more powerful and easy to use.

For the bootcamp panel problem, I saw that if you don't install the driver for MagicMouse or Trackpad, the dedicated Tab for this device won't appear. So now i'm confident that we could desactivate de Start Tab of the panel and "repair" it. I think a Tab is link to a *.dll so what about rename the start tab dll with another tab dll ; we duplicate the tab but the bootcamp panel will work ?

The more difficult solutions would be to emulate the two bites of the MBR that bootcamp access to setup the bootdisk. We could also redirect this request to the bootloader (Grub, Refind ...).
 
DaGr8Gatzby said:
@rip1999eternal

Do not use rEFInd for now. Only install the EFI shell. The reason I say this is because rEFIt used to have this bug,or the mac firmware, where after running numerous EFI binaries, I was not able to get the same results from either the boot loader, or the shell. I recommend only using the EFI shell. Then using the EFI shell to chainload the required bootloader via startup.nsh, or manually.

Personally, using grub has given me the BEST results. I do have a partial bias though.

@jlpek17 and Mac-Hacks

Do not use any other tool other than dism to inject drivers. I wasted several days using RT-seven lite, or any other GUI injector because of this. I also used it to generate an autounattend.xml. Waste of time. Learn the tools created by Microsoft. It's just a lousy prerequisite. I do not know if it's the tools, or if it was just me that was messing up. However, my dism commands should provide plenty of reference. I am monitoring this thread constantly, so if you have questions, feel free to hit me up.

@duffman900

OH YEA! Sorry you didn't have any success with my method. However, it seems you want a dedicated install of Windows. If you'd like, I can make a separate tutorial for that. I will film it as well.

To everyone slipstreaming drivers, I have made the drivers that work on my machine available:

http://dl.dropbox.com/u/4308827/Inject.zip

Please let me know if these help you. I wish you guys could just ship me your machines :(
Click to expand...

Ill bless the shell directly and see what happens. As far as using dism, this is true. Ive messed up several win 7 images that were supposed to be used for company wide deployment with rt7lite. Thats what ended up forcing me to use the microsoft tool...
 
jlpek17 said:
When I investigated for "windows to go" I saw that "dism" and "imagex" was updated in Windows 8 and it was more powerful and easy to use.

For the bootcamp panel problem, I saw that if you don't install the driver for MagicMouse or Trackpad, the dedicated Tab for this device won't appear. So now i'm confident that we could desactivate de Start Tab of the panel and "repair" it. I think a Tab is link to a *.dll so what about rename the start tab dll with another tab dll ; we duplicate the tab but the bootcamp panel will work ?

The more difficult solutions would be to emulate the two bites of the MBR that bootcamp access to setup the bootdisk. We could also redirect this request to the bootloader (Grub, Refind ...).
Click to expand...

FYI - If you have Paragon NTFS for Mac OS X install and enable, bootcamp panel will not appear. If you disable, bootcamp panel will appear.
 
DaGr8Gatzby said:
@duffman900

OH YEA! Sorry you didn't have any success with my method. However, it seems you want a dedicated install of Windows. If you'd like, I can make a separate tutorial for that. I will film it as well.
(
Click to expand...

I want to dual boot. I tried a couple a days ago, over and over again, but I didn't try mac-hack's method of creating the EFI partition. I would try again, but I would need to be able to install OS X afterward on the same disk.

Even if I succeed installing Win7, I may run into the same resource problem I'm seeing right now on Win8. I thought about using Ubuntu last weekend to create the EFI partition, before mac-hack's post, because I felt Windows doesn't like how OS X creates the partition. However, booting Ubuntu proved to be a major challenge because recent versions boot into a black screen during installation.
 
duffman9000 said:
I want to dual boot. I tried a couple a days ago, over and over again, but I didn't try mac-hack's method of creating the EFI partition. I would try again, but I would need to be able to install OS X afterward on the same disk.

Even if I succeed installing Win7, I may run into the same resource problem I'm seeing right now on Win8. I thought about using Ubuntu last weekend to create the EFI partition, before mac-hack's post, because I felt Windows doesn't like how OS X creates the partition. However, booting Ubuntu proved to be a major challenge because recent versions boot into a black screen during installation.
Click to expand...

My windows disk has no problem using the EFI partition that OS X creates when you install OS X first. Did you try installing OS X first the way my method states?
 
DaGr8Gatzby said:
My windows disk has no problem using the EFI partition that OS X creates when you install OS X first. Did you try installing OS X first the way my method states?
Click to expand...


I tried your method entirely. I also tried installing Windows only. Under both instances I see a a BCD error. When I install Win8 I can at least shutdown and continue the installation. However, trying to install Win7 with your method the second part of the installation won't start.

I think I'm going to use what I have now: my Win8 installation that uses only the basic VGA driver or I may return to using Win7 via boot camp.

I've looked at the BCD file and it's always empty when the error occurs. I know it's a copy of a template, but the installer mangles it.
 
Gatsby,

You wrote an excellent manual and I will give it a try. Could you give a bit more clarification
on the following line in your manual:

"V. Trial and error phase. You will need to run the pci -i -b command using the same
column of numbers for every PCI bridge device."

In your example, does the command then become:

pci -i 05 00 00 -b

or

pci -i 00 05 00 00 -b
 
mark1234 said:
Gatsby,

You wrote an excellent manual and I will give it a try. Could you give a bit more clarification
on the following line in your manual:

"V. Trial and error phase. You will need to run the pci -i -b command using the same
column of numbers for every PCI bridge device."

In your example, does the command then become:

pci -i 05 00 00 -b

or

pci -i 00 05 00 00 -b
Click to expand...

You omit the first pair of zeros. So if the whole line for the vga device was 00 05 00 00 them the command to inspect that device would be

Code: 
pci -i 05 00 00 -b
 
Can someone please post the PCI config space of their SATA controller? The command should be:

pci -i 00 1F 02

Can you also post the Device Manager output for the IDE ATA/ATAPI Contollers?
I think I should see 2 ports and a node for the controller. Unfortunately, I see only the controller node.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back